Operations | Monitoring | ITSM | DevOps | Cloud

With the launch of the Cycle Partner Program, we are committing to making it easier for companies to work with Cycle by creating more transparent and predictable relationships, offering training, resources, incentives, and benefits, some of which will roll out over time as the program evolves. Interested in partnering with Cycle? Contact our partner lead to schedule a meeting.

According to recent surveys and reports on the industry, Kubernetes and containers are more popular than ever. Containers and serverless functions are being mainstream and ubiquitous – with a more than 300% increase in container production usage in the past 5 years. This trend is especially true for large organizations, which are often using managed platforms and services.

So, you’re looking for the right instance type for your public cloud workload, but how do you decide? Major cloud providers such as Amazon Web Services (AWS), Microsoft Azure Cloud and Google Cloud Platform (GCP) now offer such a large catalog of IaaS instances that it can become difficult to make sense of it all.

One of the easiest ways to see if the application running in our nodes is in an optimized state or not is by monitoring them. It is the last yet critical stage of any software development lifecycle. It opens up many possible improvements in your application, networking, IT automation, and other miscellaneous configurations. As we move towards microservice architecture, containerization and orchestration tools are rising. Containers are special processes that run in isolation from other processes.

One of the most exciting things when using Kubernetes is the ability to scale up and down the number of nodes based on application consumption. So you don’t have to manually add and remove nodes on demand and let it go on usage. Obviously what you want is to keep control on the minimum and the maximum number of nodes to avoid an unexpected bill.

When you think of TDD, you might lean towards Test-Driven-Development. Though in Tomasz Manugiewicz’s ACE 2022 talk, the ‘T’ in TDD could also mean Trust e.g Trust-Driven-Development. The talk, boils down to if there is trust, there is autonomy. If there is autonomy, creativity flourishes. Building trust is done incrementally, incremental success builds success. Software engineering is a team sport and an exercise in iteration.