InfoQ Homepage Microservices Content on InfoQ
-
/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.
-
/articles/infoq-2018-retrospective/en/smallimage/logo-InfoQ-1545203268727.jpg)
InfoQ’s 2018, and What We Expect to See in 2019
We take a look back at what we say on infoQ in 2018, and think about what the next year might bring.
-
/articles/golang-the-economist/en/smallimage/golang-the-economist-s-1544452613355.jpeg)
Using Golang to Build Microservices at The Economist: A Retrospective
Microservices written in Go was a key component of a new system that would enable The Economist to deliver scalable, high performing services and quickly iterate new products. Go's baked in concurrency and API support along with its design as a static, compiled language enabled a distributed eventing system. Overall, The Economist team's experience with Go has been a positive experience.
-
/articles/micronaut-tracing-security-serverless/en/smallimage/micronaut-tracing-security-serverless-s-1543948841318.jpeg)
Micronaut Tutorial: Part 2: Easy Distributed Tracing, JWT Security and AWS Lambda Deployment
In this second Micronaut tutorial article we are going to add several features to our app: distributed tracing, security via JWT and a serverless function. Moreover, we will discuss the user input validation capabilities offered by Micronaut.
-
/articles/azure-service-fabric-mesh/en/smallimage/azure-service-fabric-mesh-s-1543001784798.jpeg)
Exploring Azure Service Fabric Mesh: A Platform for Building Mission Critical Microservices
Azure has released a preview of Service Fabric Mesh, a platform targeted at microservice developers who do not want the operational responsibility of running an underlying orchestration platform. InfoQ recently sat down with Chacko Daniel, principal technical PM at Microsoft, to explore the details.
-
/articles/serverless-sea-change/en/smallimage/serverless-sea-change-s-1542815990433.jpeg)
The Serverless Sea Change
This article defines and explains how serverless is different from other application architectures and then walks through a "proof" of sorts to show that serverless application architectures, when done properly, are superior to non-serverless architectures. Finally, it concludes with a number of rules of thumb to help architects and developers realize the benefits of serverless.
-
/articles/istio-service-mesh-tutorial/en/smallimage/istio-service-mesh-tutoriaL-S-1542489920616.jpeg)
Getting Started with Istio Service Mesh Routing
In the following tutorial, we will use Istio to demonstrate one of the most powerful features of service meshes: “per request routing.” This feature allows the routing of arbitrary requests that are marked by selected HTTP headers to specific targets, which is possible only with a (OSI) layer 7 proxy. No layer 4 load balancer or proxy can achieve this functionality.
-
/articles/stateful-service-design-kubernetes/en/smallimage/akka-mountain-s-1542290375226.jpeg)
Stateful Service Design Considerations for the Kubernetes Stack
At this summer’s QCon in New York, Jonas Bonér delivered one of the most popular talks of the conference with his focus on Designing Events-First Microservices. In this InfoQ Q&A, we asked Bonér to explain how “bringing bad habits from monolithic design” is a road to nowhere for service design, and where he sees his Akka framework fitting in the cloud-native stack.