This article will discuss API Monitoring, the definition of APIs and how they would affect your business if there is a failure, and how to protect APIs or your services. Everything on the web is powered by an API nowadays. APIs are an essential part of the web to connect different services that help customers complete their actions. This article will help you understand the importance of API and why API monitoring is a business necessity.
Mocking APIs is an increasingly popular trend, with more and more developers seeing the advantages of mocking dependencies rather than spinning up actual duplicates of resources. On a high-level, a mock API means that you have a service that returns static data, which in turn is based on a real API.
In this article, you will learn about some of the tools to test microservices running in a Kubernetes cluster. In particular, we will compare the Speedscale CLI tool with other tools and the main benefits of using Speedscale CLI. In the last few years, software companies have been shifting from building monolith applications to utilizing smaller microservices. In a microservices architecture, you operate with decentralized applications. This means that there's a separation in which each service is responsible for a specific component of your application.
The monitoring and testing of public applications and APIs is challenging by itself. What should you test? How often should you run your tests? And who should be alerted? A scalable monitoring setup includes many hidden details, but technically it’s straightforward. Call public APIs and see if they do what they’re supposed to.
Gin is a high-performance HTTP web framework written in Golang. It contains features and functionalities like routing and middleware out of the box. This helps to reduce boilerplate code, improves productivity, and simplifies the process of building microservices. In this tutorial, I will guide you through the process of building a RESTful API with Golang using the Gin-gonic framework. I will also lead you through building an API to manage the basic details of a company.
With over 50,000 active organizations and 250 million workflows, CircleCI is one of the most popular networked CI platforms. When getting started with CI pipelines, teams typically want to ensure that code will compile, pass unit tests, and build a container image. After catching these low hanging fruit of syntax errors, engineering teams need to dig much further to find business logic and scalability errors.
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.
