Operations | Monitoring | ITSM | DevOps | Cloud

With Infrastructure as Code and service-oriented development, a modern web app can consist of countless moving parts developed by multiple development and DevOps teams. When establishing a high-velocity development environment, the main question is, "How can you guarantee a stellar end-user experience when lots of engineers are constantly pushing and deploying code?" Solid, easy-to-write, and clearly defined monitoring practices are the only answer to this question.

Let us consider a scenario where a Logic App is used to communicate with SharePoint through API connections, known as connectors. When configuring the connector, it communicates with Azure AD, retrieving a username and password and continuously refreshing the authentication token. When the Logic App calls the connector, it performs operations like uploading files to SharePoint.

Learn the biggest obstacles with load test automation, and how existing user traffic holds the key to scaling eCommerce software safely, and fast.

gRPC (Google Remote Procedure Call) is a high-performance, open-source universal RPC framework that Google developed to achieve high-speed communication between microservices. gRPC has Protobuf (protocol buffers) by default which would format or serialize the messages to a specific format that will be highly packed, highly efficient data. By its virtue of being a lightweight RPC, gRPC is suited for many use-cases. gRPC can be considered a successor to RPC, which is light in weight.

In the previous blog in this series, we delved into the redesigned architecture of Amazon Prime Video and how they integrated different architectural styles for optimal performance and cost efficiency. We also discussed the impact of Amazon’s decision on the concept of a “serverless-first” mindset, highlighting the importance of considering alternative architectural approaches based on specific use cases and requirements.

Earlier this week we shared some exciting news. Checkly has made its mark in not one, but two Gartner Hype Cycles reports. We're being recognized for something we're super passionate about - Monitoring as Code (MaC). This recognition comes in the Hype Cycle for Monitoring and Observability and the first ever Hype Cycle for Site Reliability Engineering. It's a big deal for us, and here's why it should matter to you, too.

The Kubernetes networking landscape is shifting. The traditional Kubernetes Ingress approach is being complemented and, in some cases, replaced by a more powerful, flexible, and extensible standard: the Kubernetes Gateway API. Kubernetes has become the go-to platform for orchestrating and managing containerized applications. A key aspect of Kubernetes that's crucial for the functionality of these applications? Networking.

I’m thrilled to announce that Gartner added Monitoring as Code (MaC) as an emerging practice into their Hype Cycles for Monitoring and Observability and Site Reliability Engineering. We are extremely hyped about this recognition and being listed as a vendor innovating in that space. Since we founded Checkly, our vision has been that monitoring should be set up as code and live in your repository; it must be open-source based and feel natural for developers.