Access control is an important function in our daily lives. Access control is provided in many different realms. For example, a physical door, a software program, or an API. Access control simply means that you are controlling who/what can access something. We’re going to focus this discussion around access control for an API. Businesses benefit from providing APIs to their internal (and external) developers.
We recently wrote about whether API Gateway can act as a Load Balancer. The answer is yes and, in many cases, they are substitutes for each other. But how should we choose which one to use? In this article, we will dive into more details on how these two types of HTTP networking services compare, using the AWS services as a base level: API Gateway and Application Load Balancer (ALB). Both are highly-scalable services to a point that scalability should not be a concern for most use cases.
APIs are stable, until they aren’t. We talk about that often at Bearer. If you control the APIs, it gets easier, but with third-party APIs and integrations it can be more difficult to predict when an outage or incident is about to happen.
There are few parts of business that the Covid-19 pandemic hasn’t impacted, in some cases creating pervasive and long-lasting change. While no one knows exactly how our lives will emerge from this upheaval, for businesses it’s clear that long term survival depends on agility. Entire workforces have been mobilised in a matter of weeks. Employees – even the Luddites among us – have had to adopt new ways of working and many are in no rush to return to the traditional office!
Alerting is central to your website, web application, and API monitoring. Getting the right message to the right people is essential to quickly resolving outages and error states. In this article, we walk you through seven aspects you need to consider when setting up the alerting for your monitors. If you need a general overview of how alerting works within Uptrends, we have a Knowledge Base article and an Academy course you may want to visit.
Exciting times ahead. With the Jamstack gaining momentum, the landscape around it is offering more and more tools to streamline developer workflows and free up time for actual development. A cutting edge solution in this interesting space is Vercel, formerly known as ZEIT. In this blog post we will get a taste of Vercel's capabilities by using it to deploy and preview a sample Gatsby blog - and while we're at it, we will of course take the chance to kick off some checks automatically from Checkly.
Kong for Kubernetes is a Kubernetes Ingress Controller and a full-fledged edge-router which can route traffic to any destination of your choice. In addition to Ingress management, it provides enhanced security and management capabilities. With Kong, you can use Kubernetes not just for running your workloads but also for securing and monitoring connectivity between your workloads – all managed via Kubernetes manifests and CI/CD processes.
The most common API architecture on Serverless backends is not necessarily the most scalable and resilient option. Many developers take for granted that an AWS Lambda processing external requests will require an API Gateway endpoint connected directly to it. One of the best options to decouple a Lambda function and an API Gateway endpoint is by using an SQS queue. Requests come into API Gateway, which are sent as messages to SQS.
Modern application development and IT infrastructure depend heavily on the use of APIs (Application Performance Interfaces) and API Management. APIs offer a standard set of rules for systems and applications to connect and interact. Whether you’re integrating a new application into an IT infrastructure or connecting the modular components of a microservices-based application, APIs are one of the fastest, most pluggable, and cost-effective ways to establish those connections.
