InfoQ Homepage Microservices Content on InfoQ
-
Saga Orchestration for Microservices Using the Outbox Pattern
The outbox pattern, implemented via change data capture, is a proven approach for addressing the concern of data exchange between microservices. The saga pattern, as demonstrated in this article, is useful for data updates that span multiple microservices.
-
Microservices from the Trenches: Lessons, Benefits, Challenges, and Mistakes
Nicky Wrightson, from Skyscanner, hosted a panel at QCon London with participants who have moved from the monolith to microservices and in some cases back again. They share their experience with microservices on production, and also strong opinions on monorepos, on operating distributed systems, and on the best way to structure an organization to make a success of this architecture.
-
Testing Quarkus Web Applications: Component & Integration Tests
Quarkus is a full-stack, Kubernetes-native Java framework made for Java virtual machines (JVMs) and native compilation. Instead of reinventing the wheel, Quarkus uses well-known enterprise-grade frameworks backed by standards/specifications and makes them compilable to a binary using Graal VM. This article focuses on using some of the Quarkus testing facilities.
-
Migrating Monoliths to Microservices with Decomposition and Incremental Changes
Microservices migrations are not a trivial change. You have to think carefully about whether or they're right for you. Maybe a monolith would be enough for your context and business needs. In this article, Sam Newman shares some decomposition and incremental changes patterns that can help you to evaluate and migrate to a microservices architecture.
-
Virtual Panel: the MicroProfile Influence on Microservices Frameworks
In mid-2016, the MicroProfile initiative was created as a collaboration of vendors to deliver microservices for enterprise Java. InfoQ recently asked the opinion of expert practitioners on how MicroProfile has influenced how developers today are building microservices-based applications, the emergence of new microservices frameworks and reverting back to monolith-based applications development.
-
InfoQ 2020 Recap, Editor Recommendations, and Best Content of the Year
As 2020 is coming to an end, we created this article listing some of the best posts published this year. This collection was hand-picked by nine InfoQ Editors recommending the greatest posts in their domain. It's a great piece to make sure you don't miss out on some of the InfoQ's best content.
-
Reviewing the Microservices Architecture: Impacts, Operational Complexity, and Alternatives
Wes Reisz moderated a roundtable with Leif Beaton (NGINX senior solutions architect), Yan Cui (independent AWS and serverless consultant), and Nicky Wrightson (Skyscanner principal engineer), discussing topics around the microservices approach. The panelists shared their experience on it, analyzing the impact of microservices, challenges in dealing with operational complexity, and alternatives.
-
Monitoring Microservices the Right Way
Modern systems are more complex to monitor as they tend to emit large amounts of high cardinality data. Recent innovations in open-source time series databases have improved the scalability of newer monitoring tools such as Prometheus. These solutions are able to handle the high scale of data while providing metric scraping, querying, and visualization based on Prometheus and Grafana.
-
Seven Hard-Earned Lessons Learned Migrating a Monolith to Microservices
Based on experience gained from several microservices migrations, these seven lessons can help you be successful and overcome or avoid common challenges.
-
Azure + Spring Boot = Serverless - Q&A with Julien Dubois
Microsoft seems to prove over and over again its focus on cloud and the Java ecosystem is the new normal. Even though Java has been amongst the supported languages for Azure functions for some time now, Julien Dubois experimented with Spring Boot and Azure to see what this combination means for Azure serverless computing. InfoQ reached out to him to explore further his experience on this topic.
-
From Monolith to Event-Driven: Finding Seams in Your Future Architecture
One of the challenges of migrating your system’s architecture is excluding non-desirable attributes and leaving the target state uncorrupted. An event-driven architecture and its related patterns, CQRS and Event Sourcing, are positioned well to introduce seams into the architecture that allow you to separate legacy and modern elements.
-
Principles for Microservice Design: Think IDEALS, Rather than SOLID
For object-oriented design we follow the SOLID principles. For microservice design we propose developers follow the “IDEALS”: interface segregation, deployability (is on you), event-driven, availability over consistency, loose-coupling, and single responsibility.