After a span of 5 long years, we've bid farewell to Cycle's old portal. Our engineering team has been working tirelessly over the last 10 months to bring a fresh, new interface to the platform for our users. This new design encapsulates the wealth of insights we've gained during this period. Just last week, we took the decisive step of launching it into production, and the initial feedback has been overwhelmingly positive.
The dev world was on fire this weekend, as news of yet another major open-source project was revealed to be in the midst of an identity crisis. The unsettling trend is clear: hit a certain adoption threshold, and then swap the licensing in an attempt to turn dedicated fans into revenue streams. With more companies searching for a sustainable business model and attempting to appease shareholders, the only certainty we have is, what was free yesterday, might be paid tomorrow.
In the dynamic landscape of software development, the terms DevOps and Platform Engineering have garnered attention. Both concepts, although distinct, aim at a shared goal: to build efficient, streamlined systems that simplify code deployment within organizations.
If you’re in DevOps, you know the word ‘Kubernetes’. While saying that mouthful of a word (generally shortened to k8s in text) would have gotten you a weird look and someone asking if you need to lie down before 2017, it’s been sacrilegious to even consider starting a project without architecting your solution on top of it in the last few years.
In recent discussions about cloud-based GPU workloads, I was struck by these two recurring challenges: As the Head of Customer Success for a platform that confronts both of these problems, I wanted to take a moment to talk about their origin, what teams can do to mitigate, and finish up with a brief look at how Cycle might help.
Redis is a powerful in-memory data store thats blazing fast. It's performant, scalable, supports a wide range of data structures, has built in caching mechanisms, and is simple to set up for Cycle users. This post will take you from deploying your first Redis instance on Cycle, through deploying highly available, stateful Redis instances that are monitored by Redis Sentinel. The companion repo for this article with configuration files and settings can be found here.
Today, we are thrilled to announce a major upgrade to the security of your networks and infrastructure on the Cycle platform. With the most recent update, our team has added IPSec support to Cycle’s Compute layer. If you’re not familiar with IPSec, it’s a suite of different encryption and authentication protocols which enables secure communication between servers.
Life at a startup often feels like a 100-meter sprint, head down, and focused until you cross the finish line. Only then do you really know what you have achieved. While a startup's work is never finished, every year we take a pause to reflect on what we have achieved over the past twelve months. And boy, was 2022 a good one!
If you're involved in deploying and managing applications and servers, you know that it is a complex and resource-intensive process. Container orchestration platforms help automate the deployment, scaling, and management of your applications, but the challenges don’t stop there. Everything from the way applications communicate, down to the underlying infrastructure they run on, exposes vulnerabilities, complexities, and builds up technical debt.
Before I dive into the launch of Cycle’s latest feature (and it’s a big one!) I want to share some context about how we got here. Let’s rewind back to 2015: containers, at least in their modern form, had just begun to take the developer ecosystem by storm. At the same time, we at Cycle were watching everything unfold: from Docker’s meteoric rise to the first few releases of tools like Kubernetes, Rancher, and so on.
