Operations | Monitoring | ITSM | DevOps | Cloud

When people hear ‘microservices’ they often think about Kubernetes, which is a declarative container orchestrator. Because of its declarative nature, Kubernetes treats microservices as entities, which presents some challenges when it comes to troubleshooting. Let’s take a look at why troubleshooting microservices in a Kubernetes environment can be challenging, and some best practices for getting it right.

Github’s, “Github Actions” CI/CD tooling is becoming an increasingly popular option for developers. I've personally worked with several Cycle users who are adopting Github Actions as part of their deployment solution and we've found that when pairing GH actions with Cycle it makes for a simple, yet powerful combination. Today we’ll stroll through a basic example of using Github Actions alongside the Cycle platform.

Modern digital businesses have adopted cloud technology and distributed architectures to enable on-demand scaling of resources. Containerization technologies like Kubernetes and Docker have made it possible to handle customer demands at scale. However, orchestrating a complex microservices architecture with Kubernetes is challenging. Monitoring your Kubernetes cluster can give you insights to better manage your cluster.

Picking the right AWS instance is challenging because you have to match the ever-changing resource usage patterns of your apps with the 500+ AWS instance types, and the result is over-provisioning and waste. Nearly one-third of businesses exceed their cloud budgets by as much as 40%, in part due to poorly sized instances.