What are Microservices? Code Examples, Best Practices, Tutorials and More

Microservices are increasingly used in the development world as developers work to create larger, more complex applications that are better developed and managed as a combination of smaller services that work cohesively together for more extensive, application-wide functionality. Tools such as Service Fabric are rising to meet the need to think about and build apps using a piece-by-piece methodology that is, frankly, less mind-boggling than considering the whole of the application at once.

Shrinking to Grow: What Small Can Do for Your Organization - Chad Fowler CTO & GM, Microsoft

During his talk, Chad outlined how almost everything we've seen in the evolution of software and systems points to one, fundamental truth: small things are more manageable than big things. Small iterations are better iterations. Small methods are better methods. Small teams are better teams. He discussed examples from sociology, psychology, and biology that explored how we can think small to build systems and organizations that can outlive us.

Microservices: Decomposing Applications for Testability and Deployability by Chris Richardson

In this presentation, Chris Richardson describes the essential characteristics of the microservice architecture. You will learn about the benefits and drawbacks of the microservice architecture and when it makes sense to use it. Chris also covers how the microservice architecture is not a silver bullet.

How we tracked down (what seemed like) a memory leak in one of our Go microservices

The backend developer team at Detectify has been working with Go for some years now, and it’s the language chosen by us to power our microservices. We think Go is a fantastic language and it has proven to perform very well for our operations. It comes with a great tool-set, such as the tool we’ll touch on later on called pprof. However, even though Go performs very well, we noticed one of our microservices had a behavior very similar to that of a memory leak.


Got microservices? Service mesh management might not be enough

A lot of enterprises are evolving their monolithic applications into microservices architectures. In this pattern, applications are composed of fine-grained services that communicate via APIs. Microservices promise, faster development, innovation, cloud scaling, better infrastructure optimization—and happier developers. No wonder this architecture gets so much attention.


Top 10 security traps to avoid when migrating from a monolith to microservices

Your team is thinking about migrating from a monolithic architecture to microservices. You’re intrigued. The promises of additional scalability and more predictable deployments sound nice. You’ve also been down this road before, and you know that those promises don’t always equal reality. You also know that migrations to a microservice approach don’t always go as planned.


10 Ways Microservices Create New Security Challenges

In the current microservices DevOps environment, there are tough new and evolving challenges for developers and teams to consider on top of the more traditional ones. From worsening versions of already common threats to new-generation evolving threats, new perspectives are required on securing microservices. These new perspectives may not be intuitive for many otherwise sophisticated DevOps and data teams.


Istio Security Basics: Running Microservices on Zero-Trust Networks

In our previous blog post about the Istio service mesh, we provided an overview of Istio’s features and capabilities and why you may (and sometimes may not, at least not yet) want to use it as a service mesh in your Kubernetes clusters. In this post, we’ll dive a little deeper into how Istio can help improve the runtime security of the applications in a service mesh and where it fits in the broader picture of Kubernetes security controls and practices.


Cargill Bridges Legacy and Cloud Native with Kong Enterprise

As we continue to expand across new industries and regions, we’re excited to share Cargill’s digital transformation story and how it turned to Kong Enterprise to create a unified API platform across existing legacy and newer cloud native systems. We talked to Jason Walker, senior enterprise architect at Cargill, about their journey to microservices. What was the driver for Cargill’s move to microservices?


Serverless Microservice Patterns Used In AWS

With serverless computing, our daily tasks and routines are much more comfortable than they used to be before. Serverless allows us to put our focus on the code itself without the need to worry about the configuration of the underlying compute resources or maintenance. Numerous cloud providers (AWS included) gives us a variety of previously managed services which we can combine and create a massively scalable and incredibly robust serverless microservices.