Week 50, year 2024

  • Designing Data Products: next steps - Once we've designed our initial data products, Kiran Prakash finishes his article by leading us through the next steps: identifying common patterns, improving the developer experience, and handling governance. [Martin Fowler]
  • Design Token-Based UI Architecture - Design tokens are fundamental design decisions represented as data. Andreas Kutschmann explains how they work and how to organize them to balance scalability, maintainability and developer experience. [Martin Fowler]
Permalink | From 09 December 2024 to 15 December 2024 | Last updated on: Thu, 12 Dec 2024 15:19:30 GMT

Week 49, year 2024

  • Designing data products: Working backwards from use cases - Increasingly the industry is seeing the value of creating data products as a core organizing principle for analytic data. Kiran Prakash has helped many clients design their data products, and shares what he's learned. In particular his methodical approach doesn't begin by thinking about some data that might be handy to share, but instead works from what consumers of a data product need. [Martin Fowler]
  • Generalizing the design of data products - Having got an initial data product, Kiran Prakash leads us through the next steps: covering similar uses cases to generalize the data product, determining which domains the products fit into, and considering service level objectives. [Martin Fowler]
Permalink | From 02 December 2024 to 08 December 2024 | Last updated on: Wed, 4 Dec 2024 23:19:26 GMT

Week 47, year 2024

  • Exploring Gen AI: Copilot's new multi-file editing - A very powerful new coding assistance feature made its way into GitHub Copilot at the end of October. This new “multi-file editing” capability expands the scope of AI assistance from small, localized suggestions to larger implementations across multiple files. Birgitta Böckeler tries out this new capability and finds out how useful its changes tend to be, and wonders about what feedback loops are needed with them. [Martin Fowler]
  • Event Store is evolving to Kurrent - “There’s a better way to do it — find it.” – Thomas Edison [Event Store blog]
  • Event Store to Kurrent Rebrand FAQ - 1. What is Kurrent? Event Store – the company and the product – are rebranding as Kurrent. The flagship product will be referred to as “the Kurrent event-native data platform” or “the Kurrent platform” or simply “Kurrent" EventStoreDB will be referred to as KurrentDB Event Store Cloud will now be called Kurrent Cloud The Kurrent event-native data platform feeds real-time, business-critical data with historical context in fine-grained streams from origination to destination, enhancing application development, data analytics and AI outcomes. Kurrent was developed to allow companies to originate data and/or aggregate data from other sources, and curate it, while also maintaining its integrity in an immutable log and persistent data store. Kurrent delivers fine-grained streams of event data to the exact point of need, so businesses can serve their downstream use cases in real-time with unmatched precision. [Event Store blog]
  • Event Store to Kurrent Rebrand FAQ - 1. What is Kurrent? Event Store – the company and the product – are rebranding as Kurrent. The flagship product will be referred to as “the Kurrent event-native data platform” or “the Kurrent platform” or simply “Kurrent" EventStoreDB will be referred to as KurrentDB Event Store Cloud will now be called Kurrent Cloud The Kurrent event-native data platform feeds real-time, business-critical data with historical context in fine-grained streams from origination to destination, enhancing application development, data analytics and AI outcomes. Kurrent was developed to allow companies to originate data and/or aggregate data from other sources, and curate it, while also maintaining its integrity in an immutable log and persistent data store. Kurrent delivers fine-grained streams of event data to the exact point of need, so businesses can serve their downstream use cases in real-time with unmatched precision. [Event Store blog]
  • Event Store is evolving to Kurrent - “There’s a better way to do it — find it.” – Thomas Edison [Event Store blog]
  • Event Store to Kurrent Rebrand FAQ - 1. What is Kurrent? Event Store – the company and the product – are rebranding as Kurrent. The flagship product will be referred to as “the Kurrent event-native data platform” or “the Kurrent platform” or simply “Kurrent" EventStoreDB will be referred to as KurrentDB Event Store Cloud will now be called Kurrent Cloud The Kurrent event-native data platform feeds real-time, business-critical data with historical context in fine-grained streams from origination to destination, enhancing application development, data analytics and AI outcomes. Kurrent was developed to allow companies to originate data and/or aggregate data from other sources, and curate it, while also maintaining its integrity in an immutable log and persistent data store. Kurrent delivers fine-grained streams of event data to the exact point of need, so businesses can serve their downstream use cases in real-time with unmatched precision. [Event Store blog]
  • Event Store is evolving to Kurrent - “There’s a better way to do it — find it.” – Thomas Edison [Event Store blog]
Permalink | From 18 November 2024 to 24 November 2024 | Last updated on: Tue, 25 Feb 2025 23:19:35 GMT

Week 46, year 2024

Permalink | From 11 November 2024 to 17 November 2024 | Last updated on: Fri, 15 Nov 2024 23:19:28 GMT

Week 45, year 2024

  • Assessing the results of using the Strangler Fig on a Mobile App - Matthew Foster and John Mikel Amiel Regida finish their account of how they incrementally modernized a mobile application by looking at the results of their work. They achieved a significant shortening of time to new value, and found that changes in the new application could be prepared in about half the time it took on the old codebase. [Martin Fowler]
Permalink | From 04 November 2024 to 10 November 2024 | Last updated on: Tue, 5 Nov 2024 15:19:30 GMT

Week 44, year 2024

  • Using the Strangler Fig with Mobile Apps - My colleagues are often involved in modernizing legacy systems, and our approach is to do this in an incremental fashion. Doing this with a mobile application raises some specific challenges. Matthew Foster and John Mikel Amiel Regida share their experiences of a recent engagement to do this, shifting from a monolithic legacy application to one using a modular micro-app architecture. [Martin Fowler]
  • Diving deeper into using the Strangler Fig with Mobile Apps - Matthew Foster and John Mikel Amiel Regida dive into the details of incrementally modernizing a legacy mobile application. They look at how to implant the strangler fig into the existing app, setting up bi-directional communication between the new app and the legacy, and ensuring effective regression testing on the overall system. [Martin Fowler]
Permalink | From 28 October 2024 to 03 November 2024 | Last updated on: Wed, 30 Oct 2024 15:19:28 GMT