• Uncovering the seams in Mainframes for Incremental Modernisation - Mainframe systems continue to run much of the world's computing workload, but it's often difficult to add new features to support growing business needs. Furthermore the architectural challenges that make them slow to enhance also make them hard to replace. To reduce the risk involved, we use an incremental approach to legacy displacement, gradually replacing legacy capabilities with implementations in modern technology. This strategy requires us to introduce seams into the mainframe system: points in which we could divert logic flow into newer services. In a recent project Alessio Ferri and Tom Coggrave investigated several approaches to introduce these seams into a long-lived mainframe system. [Martin Fowler]
• Event Store At Explore DDD Conference - Last week, the Event Store team had the pleasure of attending Explore DDD 2024, a triumphant return for the conference in the US. [Event Store blog]
• Farewell, John Kordyback - John Kordyback, a treasured colleague and friend, died last week, aged 64. [Martin Fowler]
• Uncovering Seams in a Mainframe's external interfaces - Alessio Ferri and Tom Coggrave start detailing the seams they explored with two areas of external interfaces. Batch input of files are copied to new implementations while comparing the output of the processing pipelines. API access points can be covered with a proxy and traffic gradually directed to the new implementation. [Martin Fowler]
• Joining LinkedIn - As the enmuskification of Twitter continues, I’ve increasingly heard that more people are using LinkedIn to keep up with new professional material. So, a couple of weeks ago, I set up my LinkedIn account, so people can follow me on that platform. I’ve always avoided LinkedIn - I’ve found the whole vibe of connections rather off-putting. I get too much spam from people wanting to connect as it is. But LinkedIn has added a “creator mode”, which encourages people to follow someone for posts rather than the bi-directional connection. It seems to be working reasonably well so far, so I’ve decided that I shall post all updates here to that account too. [Martin Fowler]
• I'm no longer Marten maintainer - Folks, I’d like to inform you that I’m no longer a Marten maintainer. As you know, sometimes in the project’s lifetime, there’s a moment… [Event-Driven by Oskar Dudycz]
• How to work around Apache Kafka’s limitations - Introduction To gain new insights, consider changing your perspective. For instance, think about how your API might look using GraphQL instead of REST, or compare a microservices setup that uses Apache Kafka for messaging to one that uses Axon Server to store AND route messages. [AxonIQ Blog]

Permalink | From 25 March 2024 to 31 March 2024 | Last updated on: Thu, 2 May 2024 22:06:34 GMT

• How to capture qualitative metrics - Abi Noda and Tim Cochran complete their article on qualitative metrics by outlining how to capture them effectively. They discuss the mental steps that people go through as they respond to a survey and provide a template to get started when assessing developer experience. A final section looks at how qualitative and quantitative work together: often by starting with qualitative metrics to establish baselines and determine where to focus, followed with quantitative metrics to drill deeper into specific areas. [Martin Fowler]
• Why the world’s top banks choose AxonIQ - In today's rapidly evolving business landscape, the banking and fintech industries, among others, face numerous challenges that necessitate agile, scalable, and customer-centric solutions. Enter AxonIQ's cutting-edge platforms, Axon Framework and Axon Server, which are trusted and used by some of the world's top banks, including Standard Chartered, Barclays, MoneyLion, Société Générale‏, and more. These banks rely on Axon technology to achieve their objectives and propel industries into a new era of efficiency and innovation. [AxonIQ Blog]
• Testing Event Sourcing, Emmett edition - I’ve been going pretty down the rabbit hole in the last few years. What am I searching for? A way to deliver better software. And that’s, of… [Event-Driven by Oskar Dudycz]

Permalink | From 18 March 2024 to 24 March 2024 | Last updated on: Thu, 2 May 2024 22:06:34 GMT

• Measuring Developer Productivity via Humans - Measuring developer productivity is a difficult challenge. Conventional metrics focused on development cycle time and throughput are limited, and there aren't obvious answers for where else to turn. Qualitative metrics offer a powerful way to measure and understand developer productivity using data derived from developers themselves. Abi Noda and Tim Cochran begin their discussion by explaining what a qualitative metric is and why we shouldn't reject them for being subjective or unreliable. [Martin Fowler]
• The Benefits of Qualitative Metrics - Abi Noda and Tim Cochran continue their discussion on using qualitative metrics to assess the productivity of development teams. In this installment they classify qualitative metrics into attitudinal and behavioral metrics. We also see that qualitative metrics allow you to measure things that are otherwise unmeasurable, provide missing visibility, and supply necessary context for quantitative data. [Martin Fowler]
• Code samples for the opening chapter of Refactoring - From time to time people ask me for a copy of the code I used in the opening chapter of Refactoring, so they can follow along themselves. I had Reasons for not providing this code, specifically laziness. Fortunately Emily Bache is more dedicated, and she has set up a github repository - the Theatrical Players Refactoring Kata - with the code, and enough tests to make it reasonable to do the refactoring. The repository goes further than this, however, in that it includes similar sample code in a dozen languages, including C, Java, Rust, and Python. She has recently posted a video to her YouTube channel, which outlines why she encourages folks to use this code while they are reading that chapter. Her channel includes a lot of videos on good code technique, and she has a Patreon for readers to support her work. [Martin Fowler]
• Join my Event Sourcing workshops at Techorama and DDD Europe and speed up your journey! - Event Sourcing is a pattern that is quickly gaining popularity. Many companies see the advantages it brings, e.g. business focus and keeping… [Event-Driven by Oskar Dudycz]

Permalink | From 11 March 2024 to 17 March 2024 | Last updated on: Sun, 17 Mar 2024 22:06:34 GMT

• Patterns of Legacy Displacement: Event Interception - When we gradually replace a legacy system, we have plenty of cases where the legacy system and its replacement need to interact. Since these legacy systems are often difficult, and costly, to change, we need a mechanism that can integrate elements of the replacement while minimizing the impact to the legacy system. Ian Cartwright, Rob Horn, and James Lewis explain how we can use Event Interception on state-changing events, allowing us to forward them to the replacement. [Martin Fowler]
• Expert Talk, Swag, Meet-Up | Event Store at QCon London - Event Store is excited to be joining this year's QCon London as a gold sponsor, taking place from 8th - 10th April. [Event Store blog]
• Event Store's Explore DDD Meetup | Friday March 15th, 7pm - Excitement is in the air as we gear up for Explore DDD next week! This event brings together a diverse international community of industry experts, developers, software architects, and business leaders. Don't miss the opportunity to catch Event Store's very own Erik Shafer speaking on 'Ecommerce with DDD and Event Sourcing'. And be sure to join us for a special meet-up where you can enjoy free drinks, nibbles, and even a friendly game of pool! [Event Store blog]
• What if we rotate pairs every day? - When pair programming, it's important to rotate the pairs frequently, but many organizations that do pair programming are reluctant to do that. Gabriel Robaina and Kieran Murphy ask the question: “What if we rotate pairs every day?” and worked with three teams through an exercise of daily pair rotation. They developed a lightweight methodology to help teams reflect on the benefits and challenges of pairing and how to solve them. Initial fears were overcome and teams discovered the benefits of frequently rotating pairs. They learned that pair swapping frequently greatly enhances the benefits of pairing. Their article shares the methodology they developed, their observations, and some common fears and insights shared by the participating team members. [Martin Fowler]
• EventStoreDB 24.2 released - Today, we are excited to announce that the EventStoreDB 24.2 Release is here. This release is a significant update that introduces a suite of innovative features and enhancements designed to elevate the performance, security, and scalability of your event-native applications. The highlights below represent just the beginning of what EventStoreDB 24.2 offers. Read on to uncover the details of these features and more. [Event Store blog]
• How to tackle compatibility issues in ECMA Script modules (and in general) - Do you recall moments when you’re sitting and closing dozens or more browser tabs? Most of them are Google, GitHub, Blogs, and others. You… [Event-Driven by Oskar Dudycz]
• How to Fix a Bug: Tests, Hypotheses, Timeboxes - Here’s roughly how I fixed bugs early on in my career: Browse around in the code. Try stuff. See if it works. Below is my preferred way of doing it since about 2012: Step 1. Pair / Ensemble Find one or more people to collaborate with. Linus’ Law “Given enough eyeballs, all bugs are shallow” was formulated at least 25 years ago, and yet we do so much work in isolation. [Mathias Verraes]

Permalink | From 04 March 2024 to 10 March 2024 | Last updated on: Sun, 10 Mar 2024 14:06:31 GMT