Operations | Monitoring | ITSM | DevOps | Cloud

It is incumbent on cloud operations teams to choose the correct type of AWS EC2 instance relative to the underlying application. The wrong choice could adversely impact business and user experience. This article walks through a customer case study where the EC2 instance choice impacted their business.

Serverless computing is on the rise, having already earned the mantle of “The Next Big Thing”. For developers, serverless computing means less concern regarding infrastructure when deploying code, as all computing resources are dynamically provisioned by the cloud provider. Pricing is generally on a pay-as-you-use model and is based on resources consumed – which is in line with modern business principles of “on-demand”, flexibility and rapid scaling.

Both AWS X-Ray and Jaeger are distributed tracing tools used for performance monitoring in a microservices architecture. Jaeger was originally built by teams at Uber and then open-sourced in 2015. On the other hand, AWS X-Ray is a distributed tracing tool provided by AWS specifically focused on distributed tracing for applications using Amazon Cloud Services. Jaeger is a popular open-source tool that graduated as a project from Cloud Native Computing Foundation.

Not too long ago, you would have needed development experience to oversee the delivery of scalable and reliable software. But with the rise of low-code and no-code tools, that requirement is now obsolete. What used to be hours of coding has turned into a few minutes of dragging and dropping.

If the cloud is a destination you have planned for any of your enterprise workloads, then you need to be prepared to navigate the journey that is the cloud migration process. It’s not unlike planning for a physical trip to a fabulous destination (or maybe we’re just really really ready to start traveling again). Either way, we’ve got some travel tips to ensure that your cloud-bound workloads have a great trip.