Throughout the week, I read a lot of blog-posts, articles, and so forth that has to do with things that interest me:
- AI/data science
- data in general
- data architecture
- distributed computing
- SQL Server
- transactions (both db as well as non db)
- and other “stuff”
This blog-post is the “roundup” of the things that have been most interesting to me for the week just ending.
- 5 Reasons Why You Should Use Microsoft Dapr to Build Event-driven Microservices. Dapr is a portable, event-driven runtime, and it helps developers build event-driven, resilient distributed applications. As the name implies, the post linked to looks at some of the reasons to use Dapr.
- Alibaba Cloud Uses Dapr to Support Its Business Growth. I doubt that the Alibaba crowd read the post above, but they use Dapr extensively. This InfoQ post looks at some of the reasons why Alibaba chose Dapr. Quite interesting read!
- Sundial: Fault-tolerant Clock Synchronization for Datacenters. The post linked to here gives an excellent explanation of time synchronization challenges and fundamental techniques to achieve precise time synchronization in data centers.
- Configure SQL Server AG (Read-Scale) for SQL Containers deployed on Kubernetes using Helm. This post looks at how to setup Always On Availability Group (AG) between SQL instances deployed as SQL containers on Kubernetes. As a SQL old-timer, I still can’t believe we can run SQL on Linux and in Kubernetes!
- Catching Data In a Data Mesh: Principles (Part I). This post is part of a series intending to give an in-depth view of how the Data Mesh architectural paradigm helps to build a data platform. This is part one, explaining the thinking about the mesh and the guiding principles for the implementation. After reading this post, be sure to read part two as well.
- Making Data Lakehouse real yet effective. In previous roundups, I have linked to posts about data warehouses, data lakes, data lakehouses, etc. The post I link to here tries to explore and explain how all this hangs together.
- Feature Store: Data Platform for Machine Learning. Feature stores are a relatively recent “innovation” in the Machine Learning world. A feature store is a data system that runs data pipelines that transform raw data into feature values, stores and manages the feature data, and serves feature data consistently for training and inference purposes. The post I link to here surveys the leading feature stores. As a side note: if you want to read more about feature stores, browse over to Feature Store for ML.
- Integrating Azure and Confluent: Real-Time Search Powered by Azure Cache for Redis, Spring Cloud. This article looks at an architecture pattern that transforms an existing traditional transaction system into a real-time data processing system. Don’t get hung up on the components used (Redis Cache, Spring Cloud), as what the article covers is applicable for different tech-stacks as well.
- Event-Driven Architecture Demo. As the title says, this post looks at a completely event-driven system, incorporating Kafka and GraphQL. Very cool!
That’s all for this week. I hope you enjoy what I did put together. If you have ideas for what to cover, please comment on this post or ping me.