Explore >> Select a destination
|
You are here 
|
codesimple.blog | ||
| | | | |
jack-vanlightly.com
|
|
| | | | | At some point, we've all sat in an architecture meeting where someone asks, "Should this be an event? An RPC? A queue?", or "How do we tie this process together across our microservices? Should it be event-driven? Maybe a workflow orchestration?" Cue a flurry of opinions, whiteboard arrows, and vague references to sagas. Now that I work for a streaming data infra vendor, I get asked: "How do event-driven architecture, stream processing, orchestration, and the new durable execution category relate to one another?" These are deceptively broad questions, touching everything from architectural principles to practical trade-offs. To be honest, I had an instinctual understanding of how they fit together but I'd never written it down, so this series is how I see it, my mental framework, and hopefully it will be useful and understandable to you. | |
| | | | |
www.decodable.co
|
|
| | | | | How does the current state of data movement within a typical data platform compare to a stream processing environment? Sharon explores the scaling and management challenges of a traditional approach and looks at the benefits of unified data movement to support ELT, ETL, and data replication. | |
| | | | |
martinfowler.com
|
|
| | | | | Four principles that drive a logical architecture for a data mesh. | |
| | | | |
www.kevinrchant.com
|
|
| | | In this post I want to cover my first impressions of the Microsoft Fabric security white paper. For a couple of reasons. | ||
