Nowadays, REST is ubiquitous across most kinds of applications. It provides an easy, simple and clear language to communicate between services, usually a frontend and a backend. Although, there are many good alternatives and I want to talk about one in particular - gRPC. From my days as a Software Engineer at Google, I have grown quite fond of gRPC. Google uses it everywhere, from communicating between frontend and backend, to communicating with database servers to all kinds of microservices.

The StatusCake API allows users of the platform to come up with custom ways of interacting and making our tools work for their specific needs. In this blog post I’m going to look at a few recent projects on GitHub that use the StatusCake API to either save you time or do something interesting with your test data.

In this tutorial, you will learn how to work with the gRPC Golang library for microservice communication by creating a simple note-taking application. APIs and service-to-service communication are what make modern microservice architecture possible. REST is generally the preferred implementation pattern, but if you only use REST, you could miss out on the significant performance gains that gRPC can offer. gRPC can provide better speed and efficiency than REST APIs.

Observability, introspection, logging, and dependency mapping are critical when building APIs. With the advent of microservice architecture, understanding what happens inside your container is vital during development. Speedscale CLI is a container-centric tool that allows you to monitor inbound and outbound traffic. With Speedscale CLI, you can monitor raw requests, latency, encoding, and detected technologies.

While new cloud native architectures are incredibly feature-rich, they can come with a high barrier to entry. Many getting started tutorials are pages long and can take forever to complete. But these always start with the first step of performing an installation. In the spirit of making the installation of Speedscale as simple as possible, we have designed a new interactive installer as part of the speedctl command line interface.

Today, I'm excited to share the release of a long-planned and requested feature - our new Check Overview Page. Until now, Checkly enabled you to troubleshoot single alerts, but a deep dive into the long-term performance trends was limited. That is not the case anymore. In the new Check Overview, we’re introducing the enhanced analytics in four distinct categories: The update is focused on two important outcomes.

We’re building incident.io as the single place you turn to when things go wrong. When an issue is disrupting your business-as-usual, the last thing you want is to start opening ten different tools to diagnose and fix it! As your central incident hub, we need to give you two powers: Workflows cover the former. Workflows are like a mini incident.io Zapier.

So you’ve just been tasked with creating a Terraform Provider (or maybe upgrading an existing one). As you do your research to prepare for the project, you slowly begin to realize, “well this looks like I’ll just be developing a Terraform specific wrapper for a client of my API.” It’s not particularly difficult, but it seems tedious. Is there a better way to build this? Maybe something that can be modular and automated? A way that’s actually stimulating to implement?

BigPanda offers a diverse set of APIs to enterprises looking to move faster and scale incident response workflows seamlessly. APIs are core to automating repeated incident response workflows that enable IT Ops to keep up with the pace of change and innovation agile teams need to thrive. In Q4 of 2021, BigPanda announced the general availability of new self-service APIs including an updated Incidents API.