⚠️ Please note, this is a very early draft. Revisions and diagrams coming soon! 🔗 In part 1 of this series we discussed why and when a domain-specific PaaS can be useful. Part 2 continued with the example use case and presented the platform at a high level. In this post, we’ll get into the technical details of how we might implement a domain-specific PaaS using Kubernetes, Istio and Auth0.

In part 1 of this series we discussed why and when a domain-specific PaaS can be useful. This post will present a specific use case. Part 3 will show how we can build our platform by customizing Kubernetes through its native extension points. But first, dancing Bill Gates. 🔗Real time data is not the first thing that comes to mind when you think of Microsoft Excel, but in fact Excel has some impressive capabilities in this area.

Languages are amazing things. For all the beauty of music and dance, neither has the ability to convey information as precisely as human language. Sure, there’s few better expressions of romantic love than Percy Sledge’s When a Man Loves a Woman, or more convincing statements of intergalactic dominance than an enthusiastic performance of the Hammer dance. But if you need to give someone directions to the railway station, or explain the poor numbers of the sales unit in the quarterly report, you’re probably better off using a human language rather than humming or interpretive dance.