InfoQ Homepage Microservices Content on InfoQ
-
/articles/microservicilities-tekton/en/smallimage/implementing-microservicilities-with-tekton-small-1620664010598-1626177498036.jpg)
Implementing Pipeline Microservicilities with Tekton
Microservicilities is a list of cross-cutting concerns that a service must implement apart from the business logic. These concerns include invocation, elasticity and resiliency, among others. This article describes how a service mesh such as Istio may be used to implement these concerns.
-
/articles/microservicilities-istio/en/smallimage/implementing-microservicilities-with-quarkus-and-microProfile-small-1620664010598-1623756271578.jpg)
Implementing Microservicilites with Istio
Microservicilities is a list of cross-cutting concerns that a service must implement apart from the business logic. These concerns include invocation, elasticity and resiliency, among others. This article describes how a service mesh such as Istio may be used to implement these concerns.
-
/articles/Microservices-Case-Study/en/smallimage/a-decade-of-microservices-financial-firm-small-1621258139055.jpg)
Case Study: a Decade of Microservices at a Financial Firm
Microservices are the hot new architectural pattern, but the problem with “hot” and “new” is that it can take years for the real costs of an architectural pattern to be revealed. Fortunately, the pattern isn’t new, just the name is. So, we can learn from companies that have been doing this for a decade or more.
-
/articles/Running-Axon-Server-VM/en/smallimage/cqrs-s-1618608230290.jpg)
Running Axon Server in a Virtual Machine
In this series, we’ve been looking at running Axon Server locally, in Docker, and Kubernetes. What happens if we use a VM as a platform? Naturally, we need to do more work to get everything set up correctly, because instead of sharing a part of the Operating System, we now have to consider everything from the machine and upwards.
-
/articles/building-microservices-in-java/en/smallimage/building-microservices-in-java-small-1617799532305.jpg)
Article Series: Building Microservices in Java
This article series will explore the state-of-the-art in building microservice-based architectures using the Java language. Alongside popular stalwarts, such as Spring Boot and Dropwizard, newer frameworks, such as Quarkus, Micronaut and Helidon, have been gaining momentum. These frameworks emerged after MicroProfile was introduced to the Java community in 2016.
-
/articles/testing-quarkus-reactive/en/smallimage/testing-quarkus-part-3-small-1615282646449.jpg)
Testing Quarkus Web Applications: Reactive Messaging, Kafka, and Testcontainers
Quarkus is a full-stack, Kubernetes-native Java framework that supports many coding styles, including reactive programming. Writing clean unit/component/integration tests for Quarkus applications when a reactive approach is used is vitally important. Here we demonstrate testing reactive code, reactive messaging, and full integration testing.
-
/articles/serverless-microservices-flexibility/en/smallimage/logo-1614703384662.jpg)
Serverless Functions for Microservices? Probably Yes, But Stay Flexible to Change
When designing cloud-native systems, it is important to accommodate freedom to change deployment strategy, from FaaS to containers or VMs, for potentially significant savings on cloud bills.
-
/articles/saga-orchestration-outbox/en/smallimage/logo-1614119945335.jpg)
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.
-
/articles/microservices-from-trenches-lessons-challenges/en/smallimage/ivj9ss0o-1613044026543.jpeg)
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.
-
/articles/testing-quarkus-integration/en/smallimage/github-logo-1612966105089.jpg)
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.
-
/articles/migrating-monoliths-to-microservices-with-decomposition/en/smallimage/micreoservices-logo-1612542776368.jpeg)
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.
-
/articles/microprofile-microservices/en/smallimage/microprofile-logo-small-1612176632505.jpg)
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.