A few months ago I signed up to be an advisor to Kelda, and I thought I’d do a quick post to talk about the company and why I decided to sign up.
What is Kelda?
Kelda provides developer sandboxes in a customer’s cloud within their Kubernetes cluster. Why does this matter?
- The world is moving to cloud computing at a rapid place.
- Cloud computing is moving away from virtual machines as the unit of abstraction and towards containers, microservices, and serverless architectures.
- The exact technologies that make microservices powerful in production environments have made the development experience worse.
In short, nobody was thinking much about developers when they started migrating to these new architectures.
Think for a minute about being a developer building a microservices-based application. Then think about testing it. Your code has dependencies on scores or hundreds of microservices which in turn have dependencies on other microservices. Any or all of these microservices are themselves changing over time. How you are you supposed to find a stable test-bed on which to test your code?
Unlike production environments, run by DevOps teams with a sophisticated CI/CD platform, development environments are often primitive by comparison. Tools for collecting dependencies are not robust. Developers often have to test on their own laptops, running all the required microservices locally, which elongates test cycles because of slow performance. Moreover, debugging is potentially complicated by non-deterministic interactions among microservices.
Kelda solves all that by effectively spinning up a private, stable, server-based Kubernetes cluster where developers can test their code. If that sounds pretty practical, well it is. If that sounds pedestrian, remember that one of VMware’s top early use-case was … stable test environments for QA teams across different version of operating systems, middleware, and databases. Pragmatic solutions often generalize way beyond their initial landing point.
For more technical information on Kelda, here’s a link where you can download their white paper. And here’s an excerpt that sums things up quite nicely:
Why Did I Sign Up to Advise Kelda?
There are always many reasons behind such a decision, so in no particular order:
- The awesome founder, Ethan Jackson, who put his Berkeley computer science PhD on the back burner in order create the company. I like that this isn’t his first corporate rodeo (he worked at Nicira –> VMware) for 5 years. I also like the burn-the-ships level of commitment.
- The practical logic behind the product idea. Remember the famous William Gibson quote: “the future is already here — it’s just not very evenly distributed.” When you’re working at the cutting edge, the next step looks kind of obvious. So while this looks very high-tech to me, it looks pretty obvious to Ethan and, in my humble opinion, a lot of people have been very successful doing the next pretty-obvious thing (e.g., from PeopleSoft building apps atop Oracle to NetSuite taking financials to the cloud to Palo Alto Networks doing application-based firewalls).
- The trends driving the company. Kelda is dead center of the movement to containers and microservices-based architectures in the cloud. The technology elite can use all these technologies today. Kelda makes them more accessible to the typical corporate development shop.