Kelda advisor Dave Kellogg featured us in his blogpost “Why I’m Advising Kelda” on Kellblog. Dave Kellogg is an expert on technology and startups, the former CEO of Host Analytics, SVP/GM of Salesforce Service Cloud, and before that the CEO of MarkLogic. His deep insight in business, management, and the technology industry have proven invaluable to us at Kelda, and we're so grateful to have him on our team.
With his permission, we've reprinted the full article below.
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?
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:
In production, that complexity is dealt with by a dizzying array of tools (containers, orchestrators, service meshes, and monitoring services). However, in local development, the developers are on their own, left to set up complex development environments with tools that are slow and difficult to understand. These challenges lead to wasted time and inefficienty that, as an industry, we've just accepted as normal.
Why Did I Sign Up to Advise Kelda?
There are always many reasons behind such a decision, so in no particular order:
Kelda gives each developer a personal development sandbox that's lightweight, fast, and easy to use. Kelda development environments run on Kubernetes in your cloud while allowing developers to continue using their favorite local development tools. Kelda combines a fantastic developer experience with the performance, stability, sophisticated features possible when running in the cloud.