Remove Fashion Remove Microservices Remove Scalability Remove System Design
article thumbnail

Journey to Event Driven ā€“ Part 4: Four Pillars of Event Streaming Microservices

Confluent

Iā€™m going to explore four pillars for enabling scalable development that works across the event-driven enterprise. These pillars minimize complexity and provide foundational rules for building systems using composition. How do I upgrade or evolve microservices? Which teams are going to run my system? What is the latency?

article thumbnail

Journey to Event Driven ā€“ Part 2: Programming Models for the Event-Driven Architecture

Confluent

Rather, we apply different event planes to provide orthogonal aspects of system design such as core functionality, operations and instrumentation. Do I need to use a microservices framework? Systems built as Reactive Systems are more flexible, loosely-coupled and scalable. Event-driven architecture.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Journey to Event Driven ā€“ Part 3: The Affinity Between Events, Streams and Serverless

Confluent

In part 1 of this series, we developed an understanding of event-driven architectures and determined that the event-first approach allows us to model the domain in addition to building decoupled, scalable and enterprise-wide systems that can evolve. The first call is where database connections (and the like) should be initialized.

article thumbnail

Distributed systems: A quick and simple definition

O'Reilly Media - Ideas

Virtually all modern software and applications built today are distributed systems of some sort, says Sam Newman , director at Sam Newman & Associates and author of Building Microservices. Even a monolithic application talking to a database is a distributed system, he says, ā€œjust a very simple one.ā€. Horizontal Scalability.