InfoQ Homepage Architecture Content on InfoQ
-
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.
-
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.
-
Book Review: Solidity Programming Essentials
Ethereum is an emerging technology that promises the ability to disintermediate many traditional approaches to business through decentralized ledger technology, built upon open-source software. In this article, we will review a recent book based upon Solidity, a programming language used to construct smart contracts on the Ethereum blockchain.
-
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.
-
Seth James Nielson on Blockchain Technology for Data Governance
Seth James Nielson recently hosted a tutorial workshop at Data Architecture Summit 2018 Conference about Blockchain technology and its impact on data architecture and data governance.
-
Q&A on the Book Bitwise - A Life in Code
In the book Bitwise - A Life in Code, David Auerbach discusses the gap between how computers picture the world and how it really is, and provides his story of attempting to close that gap. The book explores how technology has impacted society and aims to make you think about what computers do to people.
-
Apache Kafka: Ten Best Practices to Optimize Your Deployment
Author Ben Bromhead discusses the latest Kafka best practices for developers to manage the data streaming platform more effectively. Best practices include log configuration, proper hardware usage, Zookeeper configuration, replication factor, and partition count.
-
Give REST a Rest with RSocket
Representational State Transfer (REST) has become the de facto standard for communicating between microservices. The author argues that is not a good thing. We need a modern material to replace HTTP for creating modern services. Open source RSocket is designed for services. It is a connection-oriented, message-driven protocol with built-in flow control at the application level.
-
Resilient Systems in Banking
Resilience is about tolerating failure, not eliminating it. To build a resilient system, you must build a system that absorbs shocks, and continues or recovers. Following best practices for resilient architecture, including established cloud patterns, allowed Starling Bank to build a bank, from scratch, in a year, against a backdrop of highly public outages amongst incumbent banks.
-
Micronaut Tutorial: How to Build Microservices with This JVM-Based Framework
Micronaut is a modern, JVM-based, full-stack framework for building modular and easily testable microservice applications. In this tutorial you will create three microservices written in Java, Kotlin and Groovy that use the framework.
-
Agile in the Context of a Holistic Approach
In this article Jon Kern, co-author of the Agile Manifesto, describes a set of critical practices that serve to build up a holistic view of the project, from which all else proceeds. Fail to do a good job at taking the systems view, and your project will likely not go as well as it could. It might even fail.
-
Scaling Autonomy at Zalando
Autonomy isn't something you can just give to a team, it’s something that teams learn and earn over time. It has to come with accountability to amplify working towards a purpose. At Zalando, creating the right architecture and organizational structure reduced the amount of alignment needed and freed up the energy to be more thorough where alignment is needed.