InfoQ Homepage Architecture & Design Content on InfoQ
-
/articles/hyperledger-experience-report/en/smallimage/hyperledger-experience-report-s-1551274078411.jpeg)
Exploring HyperLedger: Experience in Being a Framework Early Adopter
Some time ago OpenGift explored deploying a HyperLedger-based blockchain within a production environment. This article presents a story of our attempts to integrate it and the problems we encountered.
-
/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/serverless-performance-cost/en/smallimage/4-Techniques-Serverless-Platforms-Balance-Performance-Cost-small-1-1550007155719.jpg)
Four Techniques Serverless Platforms Use to Balance Performance and Cost
There are two aspects that have been key to the rapid adoption of serverless computing: the performance and the cost model. This article looks at those aspects, the tradeoffs, and opportunity ahead.
-
/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/overcoming-restlessness/en/smallimage/overcoming-restlessness-s-1548835990305.jpeg)
Overcoming RESTlessness
New API protocols like GraphQL, gRPC, and Apache Kafka have risen in popularity as alternatives to REST-inspired HTTP APIs. Instead of seeking to replace REST, the software engineering industry should seek to evolve by building on the maturity of the REST ecosystem while exploiting the technological strengths of the new protocols.
-
/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/Kubernetes-multi-cloud/en/smallimage/Kubernetes-multi-s-1548317086297.jpeg)
Virtual Panel: Kubernetes and the Challenges of Multi-Cloud
Kubernetes is eliminating vendor lock-in and enabling cloud portability. In this panel, the panelists talk about what multi-cloud means as more than a common platform on multiple clouds.
-
/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/why-architectural-diagrams/en/smallimage/why-architectural-diagrams-s-1547639074677.jpeg)
Why Do We Need Architectural Diagrams?
Software architecture diagrams, when created well, and sparingly, can greatly improve communication within the development team and with external stakeholders. They require an understanding of the intended audience, and thoughtful restraint on what to include. Resist the temptation to think that diagrams are unnecessary or unhelpful, simply because there have been plenty of cases of bad diagrams.
-
/articles/patient-care-stream-processing/en/smallimage/patient-care-stream-processing-s-1547626914062.jpeg)
Increasing the Quality of Patient Care through Stream Processing
Today’s healthcare technology landscape is disaggregated and siloed. Physicians analyse patient data streams from different systems without much correlation. Even though health-tech domain is mature and rich with data, the value of it is not directed towards increasing the quality of patient care. This article presents a stream processing solution in which streams are co-related.