I'll conclude this thread tomorrow with the last #ComposableCodex chapter.
While you wait, you can read the full chapter on data sprawl here: https://voltrondata.com/codex/data-sprawl
or explore the other chapters that have already been published.
Please share and ask questions!
🧵 31/...
Today, we continue our exploration of the #ComposableCodex with Chapter 03, "Data Sprawl" (🔗 https://voltrondata.com/codex/data-sprawl).
Most likely, you have data in more than one system. Each requires a special incantation (and/or a new support ticket) to access its contents.
With composable data systems, standards help you access data where they are.
🧵 25/...
Let's continue our deep dive into the #ComposableCodex with Chapter 02: "Bridging Language Divides" (🔗 https://voltrondata.com/codex/bridging-language-divides)
What if teams could use the language of their choice, all thanks to standards?
🧵 18/...
Finally, well-designed modules will let you extend them beyond their initial use case to fit your specific workflows or data formats. For instance, the Arrow format has already been extended to represent PyTorch data frame (with #TorchArrow) and geospatial data with #GeoArrow.
That's it for today! To read the full chapter of the #ComposableCodex "Standards over Silos", it's at https://voltrondata.com/codex/standards-over-silos
I will continue soon with the next chapter on UIs for data systems.
🧵 17/...
Today, we continue this thread with Chapter 01 of the #ComposableCodex: "Standards over Silos" (🔗 https://voltrondata.com/codex/standards-over-silos).
We will explore how to recognize good standards and use them to build a composable data system.
🧵 7/...
0️⃣0️⃣ - Chapter 00 - A New Frontier
🔗 https://voltrondata.com/codex/a-new-frontier
There are 100s of database systems available, and yet, companies with lots of data don't find one for their niche, and instead develop their own. It is a very expensive endeavor 💸 and all these systems are not that different. 🧵 2/...
François Michonneau