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.
- Microsoft SQL Server Blog. If you follow what happens in the database world, you probably know that Microsoft SQL Server 2022 is now in Public Preview. This version of SQL Server promises to be a pretty impressive release, so I suggest two things: download the preview and test it out, and bookmark the SQL Server 2022 Blogging Series page in the linked post to follow along and see future blog posts.
Azure Data Explorer
- Take advantage of Azure Data Explorer with Playfab data connections. PlayFab is a complete backend platform for live games with managed game services, real-time analytics, and LiveOps, and you can read more about it here. This post announces how there is now an Azure Data Explorer connector for PlayFab. Based on what we are doing in Derivco, PlayFab sounds like something we really should look into, and having Azure Data Explorer connectors makes it even more so.
- Databricks strikes back. Databricks held its Data+AI Summit 2022 last week (June 27 - 30). The post linked to was published the same day as the Summit started, and it looks at the full range of announcements during the conference (yes, the author of the post was pre-briefed by Databricks). Some very cool “stuff” there!
- Prescriptive Guidance for Implementing a Data Vault Model on the Databricks Lakehouse Platform. Another Databricks-related post, this one by Databricks themselves. The post discusses Data Vault’s and how to implement them within the Bronze/Silver/Gold layer. It also looks at how to get the best performance of Data Vault with Databricks Lakehouse Platform.
- Kafka Streams: State Store. Kafka Streams stateful processing enables grouping related events that arrive at different times. Operations such as joins, reduce, counts, and aggregations can then be performed on them. That is all well and good, but the previously mentioned functionality would require state to be stored. This post dives into how state is stored in KStreams, and I found it very informative!
That’s all for this week. I hope you enjoy what I did put together. Please comment on this post or ping me if you have ideas for what to cover.