InfoQ Homepage Architecture Content on InfoQ
-
Book Review: Attack of the 50 Foot Blockchain
David Gerard's 2017 book, "Attack of the 50ft Blockchain" is an in-depth look at the cryptocurrency space. The book takes a straightforwardly skeptical angle, and is explicitly intended as a non-technical overview that frames Bitcoin in purely political and economic terms.
-
Holacracy for Humans
Snapper, a New Zealand based transport ticketing service provider, wanted to be more like a city, and less like a bureaucratic corporation. In 2016 they introduced Holacracy, which enables people to act more like entrepreneurs and self-direct their work instead of waiting to be told what to do. They use Holacracy across all areas of the business and this way of working applies to everyone.
-
Designing, Implementing, and Using Reactive APIs
Reactive programming is a hot topic in the Java world. Whether you want to leverage non-blocking APIs, manage the latency introduced by the explosion of microservices, or simply utilize computing resources more efficiently, it's time to look at reactive as a viable programming model. In this article, we offer some opinions on how you should design, implement and use reactive APIs.
-
Virtual Panel: Succeeding with Event Sourcing
Why should you use event sourcing as a data storage and retrieval technique? What are the architectural implications? When should you use platforms versus frameworks to satisfy requirements? InfoQ interviewed two experts to learn more.
-
Migrating Batch ETL to Stream Processing: A Netflix Case Study with Kafka and Flink
At QCon New York, Shriya Arora presented “Personalising Netflix with Streaming Datasets” and discussed the trials and tribulations of a recent migration of a Netflix data processing job from the traditional approach of batch-style ETL to stream processing using Apache Flink.
-
The Kubernetes Effect
To successfully design for, implement, and run applications on Kubernetes requires knowledge of primitives, and awareness of design principles and practices. This article provides an overview of Kubernetes and guidance for how to best use it.
-
DevOps and Cloud InfoQ Trends Report - January 2018
This article, following on from the Culture and Methods piece we published last week, provides a summary of how we currently see the operations space, which for us is mainly DevOps and cloud.
-
Exploring the Fundamentals of Stream Processing with the Dataflow Model and Apache Beam
At QCon San Francisco 2016, Frances Perry and Tyler Akidau presented “Fundamentals of Stream Processing with Apache Beam”, and discussed Google's Dataflow model and associated implementation of Apache Beam.
-
Is Batch ETL Dead, and is Apache Kafka the Future of Data Processing?
At QCon San Francisco 2016, Neha Narkhede presented “ETL is Dead; Long Live Streams”, and discussed the changing landscape of enterprise data processing. A core premise of the talk was that the open source Apache Kafka streaming platform can provide a flexible and uniform framework that supports modern requirements for data transformation and processing.
-
Five Things Every Developer Should Know about Software Architecture
Given the distributed nature of the software systems we’re now building, and the distributed nature of the teams building them, it's more important than ever to understand the basics of software architecture. As a short introduction to the topic and to debunk some myths, here are five things that every software developer should know about software architecture.
-
Q&A with Dan Szuc and Jo Wong on Make Meaningful Work
Raf Gemmail speaks with UX leaders Dan Szuc and Josephine Wong about Make Meaningful Work, a humanistic framework and set of practices born from applying human-centered design to the workplace. Sitting beneath existing methodologies, it enables teams to share and understand character perspectives, in working towards producing impacts which are meaningful to them.
-
Events, Flows and Long-Running Services: A Modern Approach to Workflow Automation
Recent discussions around the microservice architectural style has promoted the idea that “to effectively decouple your services you have to create an event-driven-architecture”. Although events can decrease coupling, we must avoid the mistakes of traditional SOA: centralised control should to be avoided, and workflow engines must be less painful to use and operate.