Remove Architecture Remove Events Remove System Design
article thumbnail

Agile Book Club: System Architecture

James Shore

But what about the components that make up a deployed system? Those components and interactions form your system architecture. Evolutionary System Architecture. ?? Discussion prompts: How have you seen teams approach designing system architecture? Reading: ?? About the Book Club.

article thumbnail

Journey to Event Driven – Part 2: Programming Models for the Event-Driven Architecture

Confluent

Part 1 of this series discussed why you need to embrace event-first thinking, while this article builds a rationale for different styles of event-driven architectures and compares and contrasts scaling, persistence and runtime models. In this way, we don’t think about solution architecture in just one dimension.

article thumbnail

Enabling privacy and choice for customers in data system design

Lacework

This article addresses privacy in the context of hosting data and considers how privacy by design can be incorporated into the data architecture. This is how Lacework puts customers first — by ensuring protection and control of customer data is at the core of our technology and data architecture design.

article thumbnail

GSAS Talk: Pragmatic Approach to Architecture Metrics – Part 1

Apiumhub

In their thought-provoking presentation titled “Pragmatic Approach to Architecture Metrics” at GSAS’22 organized by Apiumhub , Sonya Natanzon, and Vlad Khononov delivered valuable insights. The success of software architecture hinges upon its adaptability to meet evolving business requirements. Whatever that is.”

Metrics 68
article thumbnail

Journey to Event Driven – Part 3: The Affinity Between Events, Streams and Serverless

Confluent

What is more, as the world adopts the event-driven streaming architecture, how does it fit with serverless? Serverless functions provide a synergistic relationship with event streaming applications; they behave differently with respect to streaming workloads but are both event driven. Event-first FaaS? Next Steps.

article thumbnail

Self-documenting Architecture

Strategic Tech

I’ve heard the opinion from many technical leaders that it is reasonable to expect a new hire to take upto 6 months to learn about the code, the domain, and the architecture before they become fully productive. I believe that self-documenting architecture would dramatically reduce one of the big costs in software development.

article thumbnail

Journey to Event Driven – Part 4: Four Pillars of Event Streaming Microservices

Confluent

Event-first thinking enables us to build a new atomic unit: the event. Four pillars of event streaming. Building the KPay payment system. Pillar 4 – Operational plane: Event logging, DLQs and automation. Journey to Event Driven – Part 2: Programming Models for the Event-Driven Architecture.