At Cycle, we understand the paramount importance of security and the challenges that come with maintaining it. That's why we're proud to share how our proactive approach has not only addressed the recent “Leaky Vessels” container exploit, but has done so in a manner entirely transparent to our customers, and in under 4 hours of the vulnerability being made public.

We're thrilled to announce the launch of our latest feature: Deployments! This game-changing addition is set to redefine how our users deploy and manage their applications, ensuring zero downtime and enhancing productivity.

A new year has started and some of the major IaaS providers are making major changes early on. AWS and GCP have both announced major changes that might be a signal for what's to come this year.

With such an eventful year of releases and development, we wanted to take a moment to reflect on all thats been accomplished this trip around the sun. Before we do that, a quick message to the users who've made this year so special. Thank you so much for joining us on this amazing journey. It is your trust and unwavering support which has helped us grow this vision into a reality.

Over the last few months, you may have noticed that many of our changelog releases mentioned the release of, and improvements to, Cycle’s native load balancer. While this load balancer still officially remains in beta status, we wanted to begin diving into the details around it a bit more thoroughly: What is it? Why did we build it? How can you use it?

In part 1 of this 2 part blog we looked at some common engineering tradeoffs. But how might someone navigate these tradeoffs and build a model that works for their product? Here are some core concepts that can help along the way.

Tradeoff: a balance achieved between two desirable but incompatible features; a compromise. Schooling often promotes the idea that there is a right and wrong answer to questions… It does little to prepare us for how many times that there are multiple right answers and no definitive best path forward. In a time where we have unlimited information at our fingertips, you can throw a stone and hit a thousand people with an opinion.

Containers are nearly ubiquitous in software these days. Outside of abstractions like fully managed services (RDS, Dynamo, Cloud SQL), everything engineering teams are responsible for, mostly, land in containers. For many, deciding what platform to run those containers on is a burning question. Choosing the wrong container management solution can be a real headache.

The software engineering world has become a place where compute, storage, and availability have become the cornerstones of scale. As an industry and as individuals, we should stop to take a closer look at scaling the most important of all resources… our people. In this post I’ve modeled a team with 6 engineers, 2 Sr, 3 Mid, and 1 Jr. This team is getting 450 “units” of work done ( where a unit is just some measure of throughput ) per interval (2 months).

I'm Konner, a Strategic Sales Executive here at Cycle.io. With a background rooted in DevOps and CI/CD, I've dedicated over three years to engaging with developers and the DevOps community, consistently learning and gaining insights from each conversation.