Archive for October 2022

Week 44, year 2022

  • Exploring Mastodon - I've been a heavy user of Twitter over the last decade, and while Musk's purchase of Twitter hasn't got me running for the exit, it has prompted me to take a look at possible alternatives should Twitter change into something no longer worthwhile for me. The obvious alternative is for me to explore the fediverse with a Mastodon account. As I explore using Mastodon, I'll make some notes here so that others can learn from my explorations. [Martin Fowler]
  • Twitter feed now cross-posts to Mastodon - One of the main things I wanted to do with Mastodon was to replicate my twitter feed there, so that folks who would rather follow me on Mastodon could get everything. To do this, I used moa. party. You have to give it credentials to access both your Twitter and Mastodon feeds, which is a little worrisome, but my Mastodon-aware colleagues have used it without problems. It allows cross-posting in either or both directions, but I've set it up to just go from Twitter to Mastodon. It's pretty simple and seems to be working. [Martin Fowler]
  • An appeal to Americans who aren't inclined to vote in the midterm elections - In the United States, we have midterm elections coming up. Many people aren't interested in politics, or feel there is nobody worthwhile to vote for. If you're an American inclined to skip voting in these midterms, I'd appreciate it if you read my appeal. [Martin Fowler]
  • Never Lose Data Again - Event Sourcing to the Rescue! - Relational databases are not losing data. They’re robust, consistent and secure! Are they? Too often, we mix technical and logical concepts… [Event-Driven by Oskar Dudycz]
Permalink | From 31 October 2022 to 06 November 2022 | Last updated on: Sun, 6 Nov 2022 22:08:23 GMT

Week 43, year 2022

Permalink | From 24 October 2022 to 30 October 2022 | Last updated on: Fri, 28 Oct 2022 23:19:25 GMT

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

Week 41, year 2022

Permalink | From 10 October 2022 to 16 October 2022 | Last updated on: Tue, 25 Oct 2022 17:09:04 GMT

Week 40, year 2022

Permalink | From 03 October 2022 to 09 October 2022 | Last updated on: Fri, 4 Nov 2022 18:36:45 GMT