InfoQ Homepage Microservices Content on InfoQ
-
/articles/java-jvm-trends-2021/en/smallimage/InfoQ-Trend-Report-logo-1641794256028.jpeg)
Java InfoQ Trends Report—December 2021
This article provides a summary of how the InfoQ Java editorial team and various Java Champions currently see the adoption of technology and emerging trends within the Java and JVM space in 2021.
-
/articles/introducing-kivakit/en/smallimage/logo-1637780334611.jpg)
Introducing the KivaKit Framework
In this article, we take a brief tour of the KivaKit open source Java microservices application framework. KivaKit is a collection of mini-frameworks designed to work together. Each mini-framework is described in more detail at https://www.kivakit.org as well as on Jonathan Locke’s blog State of the Art.
-
/articles/microservices-concepts-patterns/en/smallimage/Microservices-the-letter-and-the-spirit-small-image-1637327649178.jpg)
Microservices — the Letter and the Spirit
Microservices to be a pattern of ‘decoupled services’ managed to get the best out of it (the underlying understanding of the pattern (‘small’ vs ‘decoupled’) forces developers to take certain design decisions that are consistent with these objectives. In this article discuss we will discuss well and poor implementations: ‘small-services’ vs ‘decoupled-services’ or ‘Letter’ vs the ‘Spirit’.
-
/articles/tech-presidential-campaign/en/smallimage/building-tech-at-presidential-scale-small-image-1634558562576.jpg)
Building Tech at Presidential Scale
Dan Woods discusses the unique challenges of building and running tech for a presidential cycle. Woods also describes how ML was applied at foundational points to reduce operating costs and some of the architectural choices made.
-
/articles/service-mesh-unnecessary-complexity/en/smallimage/logo-1632479954476.jpg)
How Unnecessary Complexity Gave the Service Mesh a Bad Name
There is immense value in adopting a service mesh, but it must be done in a lightweight manner to avoid unnecessary complexity. Take a pragmatic approach when implementing a service mesh by aligning with the core features of the technology, such as standardized monitoring and smart routing, and watching out for distractions.
-
/articles/ballerina-cloud-native-programming/en/smallimage/-C2PlY3M-1631543404121.jpg)
Ballerina Swan Lake: 10 Compelling Language Characteristics for Cloud Native Programming
The Ballerina language has come a long way with significant improvements since the 1.0 release in 2019. The latest Swan Lake release further simplifies building and deploying cloud native apps.
-
/articles/service-mesh-ultimate-guide-2021/en/smallimage/logo-1630968100375.jpg)
Service Mesh Ultimate Guide 2021 - Second Edition: Next Generation Microservices Development
Get up to speed on the adoption of service mesh. Learn how to deploy service mesh solutions in heterogeneous infrastructures and application/service connectivity.
-
/articles/cloud-native-architecture-adoption-part3/en/smallimage/adoption-cloud-native-architecture-part-3-logo-small-1630316844867.jpg)
Adoption of Cloud Native Architecture, Part 3: Service Orchestration and Service Mesh
This part 3 article in Cloud Native Architecture Adoption series, explores service interaction in a microservices based architecture, typical challenges we experience in distributed systems without proper governance, and how patterns like service orchestration and service mesh can help address those challenges.
-
/articles/pitfalls-patterns-microservice-dependency-management/en/smallimage/pitfalls-and-patterns-in-microservice-dependency-management-small-image-1630081386094.jpg)
Pitfalls and Patterns in Microservice Dependency Management
Silvia Esparrachiari shares stories on how a small change can impact a system, discussing the importance of having a broad view of a system to better understand how a change can impact a system. She presents three different scenarios that changed related to dependency management in an environment of microservices, all based on situations that she encountered while working at Google.
-
/articles/consistency-coupling-complexity/en/smallimage/consistency-coupling-complexity-s-1628577348640.jpg)
Consistency, Coupling, and Complexity at the Edge
Successful use of a microservices architecture requires maintaining a clear separation of concerns in the various layers and by employing design principles best suited to each layer. While RESTful API design has become the standard for microservices, it can cause problems at the UI layer. Alternatives such as the Backend-for-Frontend pattern using GraphQL can provide better separation of concerns.
-
/articles/microservices-inside-out/en/smallimage/turning-microservices-inside-out-small-image-1627634447180.jpg)
Turning Microservices Inside-Out
Turning microservices inside-out means moving past a single, request/response API to designing microservices with an inbound API for queries and commands, an outbound APIs to emit events, and a meta API to describe them both. A database can be supplemented with Apache Kafka via a connecting tissue such as Debezium.
-
/articles/github-monolith-microservices/en/smallimage/gitHub-journey-from-monolith-to-microservices-small-image-1627307383403.jpg)
GitHub’s Journey from Monolith to Microservices
This article explores GitHub's recent journey towards a microservices architecture. It takes a deeper look at GitHub’s historical and current state, goes over some internal and external factors, and discusses practical consideration points in how Github tackled their migration, including key concepts and best practices of implementing microservices architecture.