Information security (infosec) is a broad field. Its practitioners behave more like artists than engineers. After all, the mandate for security is not “do X”, but instead “ensure no one can do X, Y, Z, ɑ, β, ɣ, etc.”. The array of possibilities leading to infosec failure are vast. It’s like trying to prove a negative, thus making the task near impossible. On one hand we have an impossible task, on the other we have the affordance of time.

Applications have traditionally been run on servers, which have to be closely monitored to ensure there are no hindrances in production. In the case of serverless computing, you no longer have to manage servers, as the onus falls on cloud service providers. Read along to discover more about serverless computing, including some of its advantages and disadvantages. So what actually is serverless computing?

Ten years ago, Amazon found that every 100ms of latency would cost them roughly 1% in sales. This is a pretty clear statement on the importance of user experience! It’s especially true in today’s ultra-competitive market where the cost of switching (to another provider) for consumers is lower than ever. And one of the most common performance issues in serverless architectures is related to elevated latencies from services we depend on.

AWS API Gateway is a great service but can be quite expensive, and even cost-prohibitive in some cases. An Application Load Balancer is a viable alternative since it integrates seamlessly with Lambda functions and is also highly scalable and reliable. For very small traffic, API Gateway will probably be the winner, but in high-throughput cases, ALB is capable of providing up to 90% savings.

AWS Lambda enables you to run serverless functions in the AWS cloud, by manually triggering functions or by creating trigger events. To ensure your Lambda functions are running smoothly, you can monitor metrics that measure performance, invocations, and concurrencies. However, even if you continuously monitor, once in a while you are going to run into what’s termed a Lamba cold start. There are various ways to prevent AWS Lambda cold starts.

When thinking about serverless applications, one thing that comes to mind immediately is efficiency. Running code that gets the job done as swiftly and efficiently as possible means you spend less money, which means good coding practices suddenly directly impact your bottom line. How does logging play into this, though? Every logging action your application takes is within the scope of that same performance evaluation.

I’m a bit of a data nerd. And like many fortunate people, I’m still working from and generally staying home and have a lot spare time on my hands. So what does that combination result in? Graphs!

The Azure Functions team has yet again joined us for another monthly live webcast by staying remote and safe. In this live webcast, along with Jeff Hollan, Anthony and Matthew joined us to give a picture of the latest happenings in Azure Functions space. Without any further delay, let us jump in as there are tons of update are awaiting.

It’s no secret that AWS Lambda adoption has grown steadily since AWS first released it in 2015—and for good reason. The benefits of adopting Lambda are many: leveraging Lambda eliminates the need to provision and manage servers, enabling teams to just focus on their code without the mental and operational overhead of worrying about the underlying infrastructure.

We’re thrilled to announce that Gartner has named Lumigo a cool vendor in its recent Cool Vendors in Performance Analysis for Cloud-Native Architectures report by Padraig Byrne, Josh Chessman, Federico De Silva, Pankaj Prasad, Charley Rich, published May 18, 2020. The report explains something we at Lumigo heartily agree with: in a cloud-first world, the lines between development and operations are blurring.