On a Mission To Replace Kubernetes

Cycle was recently featured in a breakout article on The New Stack, highlighting our mission to replace Kubernetes. Written by industry veteran Charles Humble, the article is focused not just on Cycle, but on how the industry as a whole has started its rejection of Kubernetes as the defacto choice for container orchestraion.

Charles even mentions this quip from longtime Kubernetes evangelist Kelsey Hightower: “If you don't need Kubernetes, don't use it.” Which he tweeted in response to Pete Cheslock tweet that "Kubernetes has single handedly set back our industry a decade".

It's becoming overly clear how big the problem really is and Cycle is uniquely positioned to help those that are awake to the message.

From the Article: Where Does Cycle Fit?

One of the things that becomes apparent as you spend time with Cycle is that the people who designed and built it have spent a lot of time on infrastructure, so many of the smaller details and common problems have been thought about.

We've seen one example of this already with how the networking is managed. The platform also has built-in mechanisms for migrating instances from one cloud provider to another; when it does this, it automatically takes care of reconfiguring the network for you. In addition, if data needs to be moved it is handled via a streaming copy — dividing the data into chunks and then sending it across. If, like me, you have ever found yourself trying to move data from one machine to another when a disk is nearly full, you'll appreciate how helpful this is.

Moreover, automatic updates mean that any applications running on the platform are always on the latest stable version of Cycle with all the security patches applied, something which can be a challenge for firms running Kubernetes.

At a high level, this combination of multicloud support, well-thought-out features and ease of use is compelling. Warner told The New Stack they are seeing more and more customers migrating from Kubernetes to Cycle. Indeed, he told us, “a majority of the companies moving to Cycle today are moving away from Kubernetes. They spent time adopting it and using it over the years but realized the costs to maintain it weren't worth the value it delivered.” In terms of size, Warner told us, the average company moving to Cycle has between 15 and 25 developers.

My own view is that Cycle would make most sense for teams who see the value in containers as the way to package and deploy their applications to servers, but aren't necessarily committed to the Kubernetes way of doing things and perhaps haven't built a DevOps or platform team yet. I don't think it's a coincidence that its pricing, which is typically between US$500 and $6,000 a month, mentions discounts to early-stage start-ups.

Full Article 📰

Want to read the rest of the article ? Check it out on The New Stack.

💡 Interested in trying the Cycle platform? Create your account today! Want to drop in and have a chat with the Cycle team? We'd love to have you join our public Cycle Slack community!