InfoQ Homepage Microservices Content on InfoQ
-
/articles/service-mesh-event-driven-messaging/en/smallimage/using-service-mesh-for-event-driven-messaging-logo-small-1557145841741.jpg)
The Potential for Using a Service Mesh for Event-Driven Messaging
In this article, we discuss one of the most challenging and unexplored areas in service mesh architecture; supporting event-driven messaging. There are two main architectural patterns that we discuss here: the protocol proxy sidecar, and the HTTP bridge sidecar. Regardless of the pattern that is used, the sidecar can facilitate features such as observability, throttling, tracing etc.
-
/articles/api-gateway-service-mesh-app-modernisation/en/smallimage/api-gateway-service-mesh-app-modernisation-s-1556793369643.jpeg)
API Gateways and Service Meshes: Opening the Door to Application Modernisation
Modernising applications by decoupling them from the underlying infrastructure on which they are running can enable innovation, reduce costs, and improve security. An API Gateway can decouple applications from external consumers, and a service mesh decouples applications from internal consumers.
-
/articles/kubernetes-multicluster-comms/en/smallimage/kubernetes-multicluster-comms-s-1555590645353.jpeg)
To Multicluster, or Not to Multicluster: Inter-Cluster Communication Using a Service Mesh
Communication within Kubernetes clusters is a solved issue, but communication across clusters requires more design and operational overhead. Before deciding on whether to implement multicluster support, you should understand your communication use case.
-
/articles/linkerd-v2-production-adoption/en/smallimage/linkerd-v2-production-adoption-s-1554326459659.jpeg)
Linkerd v2: How Lessons from Production Adoption Resulted in a Rewrite of the Service Mesh
Linkerd 2.0 introduced a substantial rewrite of the widely adopted service mesh, using a split between Go and Rust. In this article, we discuss the lessons learned in the "cauldron of production adoption", and how those lessons became the basis of Linkerd 2.x’s philosophy, design, and implementation.
-
/articles/monitor-workflow-collaborating-microservices/en/smallimage/secure-scalable-web-ecosystem-linkedin-s-1551190398162.jpeg)
Monitoring and Managing Workflows across Collaborating Microservices
This article argues that you need to balance orchestration and choreography in a microservices architecture in order to be able to understand, manage and change the system.
-
/articles/devops-cloud-trends-2019/en/smallimage/devops-cloud-trends-2019-s-1550778123254.jpeg)
DevOps and Cloud InfoQ Trends Report - February 2019
An overview of how the “cloud computing” and DevOps space is evolving in 2019 including updates on Kubernetes, Chaos Engineering, Service meshes and more.
-
/articles/tap-compare-diferencia/en/smallimage/tap-compare-diferencia-s-1550262871940.jpeg)
Tap Compare Testing with Diferencia and Java Microservices
“Tap compare” is a testing technique that allows you to test the behavior and performance of the new service by comparing its results against the old service. This article provides an example of using a new open source tool, Diferencia, and mirroring production traffic across both old and new services to compare the difference in result.
-
/articles/ambassador-api-gateway-kubernetes/en/smallimage/ambassador-api-gateway-kubernetes-s-1549375314797.jpeg)
Ambassador: Building a Control Plane for an Envoy-Powered API Gateway on Kubernetes
This article provides an insight into the creation of the Ambassador open source API gateway for Kubernetes, and discusses the technical challenges and lessons learned from building a developer-focused control plane for managing ingress or "edge" traffic within microservice-based applications.
-
/articles/service-catalog-kubernetes/en/smallimage/service-catalog-kubernetes-s-1549091867205.jpeg)
Service Catalog and Kubernetes
Cloud-native applications do not just live inside Kubernetes—they also benefit from using the available cloud managed services. Similar to Kubernetes' declarative object configuration model, the Open Service Broker API with the Service Catalog provides a declarative way to describe cross-platform/cross-cloud managed service dependencies.
-
/articles/api-gateway-clojure-golang/en/smallimage/api-gateway-clojure-golang-s-1548715717206.jpg)
Rewriting an API Gateway Service from Clojure to Golang: AppsFlyer Experience Report
AppsFlyer processes nearly 70+ billion HTTP requests a day, and is built using a microservices architecture style. The entry point to the system that wraps all of the frontend services is a mission-critical (non-micro) service called the API Gateway. This article is an experience reporting of migrating from a Clojure-based gateway to a newly designed Go-based implementation.
-
/articles/microservices-bdd-interface-oriented/en/smallimage/microservices-bdd-interface-oriented-S-1548449537959.jpeg)
Developing Microservices with Behavior Driven Development and Interface Oriented Design
These dependencies require well-defined and well-tested services. Behavior Driven Development (BDD) and Interface Oriented Design (IOD) help achieve this. BDD concentrates on the functionality of the services, which are specified with tests. IOD identifies contractual obligations (e.g. failure reporting) of the services.
-
/articles/architecture-trends-2019/en/smallimage/InfoQ-logo-1548231844124.jpg)
Architecture and Design InfoQ Trends Report - January 2019
An overview of how the InfoQ editorial team sees the “architecture and design” (A&D) topic evolving in 2019, which focuses on fundamental architectural patterns, framework usage, and design skills.