Week 3, year 2022
- Designing Tinder - This is a guest post by Ankit Sirmorya. Ankit is working as a Machine Learning Lead/Sr. Machine Learning Engineer at Amazon and has led several machine-learning initiatives across the Amazon ecosystem. Ankit has been working on applying machine learning to solve ambiguous business problems and improve customer experience. For instance, he created a platform for experimenting with different hypotheses on Amazon product pages using reinforcement learning techniques. Currently, he is in the Alexa Shopping organization where he is developing machine-learning-based solutions to send personalized reorder hints to customers for improving their experience. [High Scalability]
- Two Phase Commit - Continuing his exploration of important patterns to maintain consistency across a cluster, Unmesh Joshi now looks at Two Phase Commit. It's broadly the most familiar approach, but comes with lots of complexities to make it work in practice over unreliable networks. [Martin Fowler]
- Critical Aggregator - Business Leaders often need to make decisions that are influenced by a wide range of activity throughout the whole enterprise. To support this systems often have a what Ian Cartwright, Rob Horn, and James Lewis call a Critical Aggregator: a component whose job is to visit various other systems and pull this information together. A critical aggregator is important, but often metastasizes into an Invasive Critical Aggregator [Martin Fowler]
- Using strongly-typed identifiers with Marten - Let’s say that you have the following class definition: Now you can create instance using: So far, so good. What if we accidentally mixed… [Event-Driven by Oskar Dudycz]
- Improving data quality with Event Sourcing - In this article we'll take a look at a few different characteristics of data quality and how Event Sourcing can help companies improve the data quality in their software. [Serialized development blog]
- Divert the Flow - Yesterday Ian Cartwright, Rob Horn, and James Lewis described the Critical Aggregator and how it can metastasize into an invasive form. When a legacy system has such an Invasive Critical Aggregator it's often best, if a little counter-intuitive, to Divert the Flow of data by building a new critical aggregator first. Once this is done, we have far more freedom to change or relocate the various upstream data sources. [Martin Fowler]
- The Quest for Low-Code: 9 paths, some of which actually work - No-code, low-code has become a popular quest. Architects are called in to separate fact from fiction. No French were harmed. [The Architect Elevator]
Permalink |
From 17 January 2022 to 23 January 2022 |
Last updated on: Tue, 25 Oct 2022 17:09:04 GMT