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.

AWS Elastic Load Balancing (ELB) dynamically distributes incoming application traffic across multiple EC2 instances and scales resources to meet traffic requirements. Elastic Load Balancing helps optimize the performance of various web and mobile applications by identifying failing EC2 instances before they affect the end-user experience.

Microsoft Azure is a cloud computing platform for building, deploying, and managing global-scale applications. With a wide range of offerings, including dozens of different services, Azure provides tools for users to create large and sophisticated systems for hosting any type of workload. But with the huge number of configuration options and resource types, understanding the health and performance of your applications in Azure can be challenging.

This article was originally published on DevOps.com. We’ve long-since established that multi-generational, multi-cloud environments are the new norm. But how does one go about managing data in those environments? In this post, we’ll take a look at the ramifications of this hybrid cloud reality and best practices for managing your data for increased scalability and heightened availability.

At Taloflow, we are determined not to be the cobbler whose children went barefoot. We approach our own AWS costs as if we are helping one of our customers. The results are striking and worth sharing. And, with zero upfront or reserved commitments required! This post illustrates how a little bit of diligence and a clear cost objective can end up making a large impact on profitability.

In recent weeks we’ve all been disrupted by the Covid-19 pandemic, both personally and professionally. The changes have been swift and severe, bringing new meaning to the Boy Scout motto: “Be Prepared.” While certain sectors, like the restaurant industry, have been brutally affected by lockdowns, we’ve also seen encouraging signs of last-minute ingenuity. At the end of March, national chain The Cheesecake Factory warned that it would not be able to pay rent.

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.

Amazon Web Services (AWS) has a suite of tools that help application development teams enhance and streamline their work experience, from the backend to frontend services. LogicMonitor consolidates data from these services and empowers users to monitor them side by side with the rest of their infrastructure, whether it’s in the Cloud or on-premises. Keep reading for tips on monitoring some of these services to ensure business continuity.

We added out of the box alerts for irregular behaviors. Lumigo Insights will trigger an alert the second it detects an irregularity with your functions ensuring you’ll know the second things start to go sideways.

It’s 2020 and running infrastructure on the cloud has become quite standard for many companies. This is underscored by a Canalys report that shows 2019 global cloud spend at $107 billion. This spend on cloud services is spread across AWS with 32.4% of the market, Azure at 17.6%, Google Cloud at 6%, Alibaba Cloud at 5.4%, and other smaller cloud players with a combined 38.5% of market share.