Week 42, year 2022

• How to implement Event-Driven Architecture - You’ve heard about Event-Driven Architecture (EDA) on your journey to event sourcing, read the blog posts, and watched the videos. You’re positive it would help your business achieve more. So, how do you go about implementing it? This page gives you some useful advice on how to implement EDA and affect real change in your business, maximizing your investment in your technical architecture. [Event Store blog]
• Creating multidisciplinary stream-aligned teams to escape the product-vs-engineering bottleneck - Rick and Kennedy continue explaining how to deal with the lack of collaboration between product and engineering. This installment advises creating multidisciplinary stream-aligned teams and establishing team working agreements. [Martin Fowler]
• Developers' tips for Event Sourcing & EDA - If you’ve made it through our Beginner’s Guide to Event-Driven Architecture (EDA) and Beginner’s Guide to Event Sourcing, you’re probably ready to start building your first event-driven application. The Event Store team put their heads together to come up with a list of tips that can give you the best start. [Event Store blog]
• Negotiate a balanced product investment mix - Rick and Kennedy conclude their article on the bottleneck caused by tension between product and engineering. This final section addresses balancing between under and over-engineering in the product's technical infrastructure. [Martin Fowler]
• Bliki: ConwaysLaw - Pretty much all the practitioners I favor in Software Architecture are deeply suspicious of any kind of general law in the field. Good software architecture is very context-specific, analyzing trade-offs that resolve differently across a wide range of environments. But if there is one thing they all agree on, it's the importance and power of Conway's Law. Important enough to affect every system I've come across, and powerful enough that you're doomed to defeat if you try to fight it. The law is probably best stated, by its author, as: [1] Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure. -- Melvin Conway Conway's Law is essentially the observation that the architectures of software systems look remarkably similar to the organization of the development team that built it. [Martin Fowler]
• Writing and testing business logic in F# - My road to functional programming was pretty long. I started with structural programming in C++ and then rebranded into an Object-Oriented… [Event-Driven by Oskar Dudycz]
• Transformation Agents: An Engagement Model - No one can transform an organization from the outside. But on the inside you're bound by legacy rules. Catch-22? [The Architect Elevator]

Permalink | From 17 October 2022 to 23 October 2022 | Last updated on: Sun, 30 Oct 2022 17:07:50 GMT