Switching over to microservices and DevOps might be costly. But not doing so might be even worse. Jerome Louvel explains why API-first is catching on and why we all should embrace the microservice revolution.
In this post, Asim Aslam, the founder of Micro, discusses the non-technical aspects of adopting microservices within a company. He also covers motivations, the migration path, what success may actually look like and the tradeoffs which are made in such a transition.
The microservice architecture has become the defacto best style for implementing web-based applications. However, with the “great power” provided by microservices comes great responsibilities and challenges. In this article, Daniel Bryant, Chief Scientist at OpenCredo and JAX DevOps speaker talks about the challenges of testing Java-based microservices.
Surprise, surprise! There’s a new Java framework which promises to allow developers to easily develop microservices in Java.
Microservices became a design style to define system architectures, purify core business concepts, evolve solutions in parallel, make things look uniform, and implement stable and consistent interfaces across systems. In this post, Zalando’s Dmitry Kolesnikov discusses the company’s principles for microservice development of stateful solutions such as fashion search and discovery.
As projects got bigger and the number of teams and modules involved increased, it became obvious that the monolith approach wasn’t scalable anymore for a number of reasons. In this post, Mete Atamel, Developer Advocate at Google and speaker at JAX DevOps 2017, identifies four reasons why the shift from monolith to microservices has become necessary.
A lot of companies and organizations have adopted Prometheus and the project quickly gained an active developer and user community. It is currently a standalone open source project maintained independently of any company. In 2016, Prometheus joined the Cloud Native Computing Foundation as the second hosted project after Kubernetes. We talked to Björn Rabenstein, engineer at SoundCloud and Prometheus core developer, about how Prometheus can help companies adopt DevOps.
Netflix has open sourced its “orchestration engine” Conductor, which helped orchestrate over 2.6 million process flows ranging from simple linear workflows to very complex dynamic workflows which run over multiple days. Let’s see what is under its hood.
In this post, Alex Zhitnitsky takes a down-to-earth view at the frameworks we have at our disposal, focusing on the Java ecosystem, to actually implement microservices and see what they’re all about.
Microservices are the current hype in the software architecture community. However, microservices can be used in many different scenarios to reach different goals. Self-contained Systems (SCS) represent one approach to achieving some of those goals while avoiding many common pitfalls.
In this article, Vaughn Vernon, author of “Implementing Domain- Driven Design”, “Reactive Messaging Patterns with the Actor Model”, and “Domain-Driven Design Distilled”, will teach you a first approach method to designing microservices, giving you a workable foundation to build on. He will introduce you to reactive software development and summarize how you can use Scala and Akka as a go-to toolkit for developing reactive microservices.
Moving to microservices? Great but the first question before you write a single line of code is: How do you organize your codebase — do you create a repository for each service or do you create a single ‘mono repo’ for all services?
In this article, Clement Escoffier, Principal Software Engineer at Red Hat, gives an overview of Vert.x and goes through an example of reactive microservice application while focusing on the different key parts of such a system.
In this article, we shortly summarize the common characteristics of Microservices, talk about the main challenges of building Microservices, and describe how product teams can leverage AWS to overcome those challenges.