InfoQ Homepage Architecture & Design Content on InfoQ
-
7 Steps for Improving Cloud Security With Business Integration
For business owners and information technology professionals, cloud computing has represented a significant advancement in terms of efficiency and supportability. But like with any major shift in the IT industry, the cloud brings a host of new security risks. Let’s take a look at the most common risks associated with integrating cloud-based business systems and how to manage them appropriately.
-
Transforming the Healthcare Industry Through API Marketplaces
A key problem in the healthcare industry is that valuable data points are hidden and siloed. Through an API marketplace, we can expose these data points securely and make them accessible by healthcare industry stakeholders and citizens alike, improving efficiency in the industry and enabling innovation in population health technologies.
-
A Great Engineer Needs the Liberal Arts
Much of what helps you become a great software engineer, and create outstanding software that people want to use, comes from outside the world of STEM. The ability to effectively analyze a problem, evaluate different options, and engineer a solution requires skills taught in the liberal arts.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
CONTENT IN THIS BOX PROVIDED BY OUR SPONSOR
Free ebooks to design,
deploy, and manage modern
applications:
Cloud Native DevOps With Kubernetes
This full, complete O’Reilly book shows developers and operations staff how to apply industry-standard DevOps practices to Kubernetes in a cloud-native context.
Service Mesh for Microservices
Learn how a service mesh provides a configurable infrastructure layer that makes service-to-service communication flexible, reliable, and fast.
Microservices: From Design to Deployment
Learn benefits and drawbacks of microservices, whether it makes sense for your project, and how to apply it.
SOA vs Microservices
Get more out of your service-oriented architecture investment.
Follow NGINX on: 
