How to Secure Serverless Applications - Part One

This article is part of a two-part series: First off before we dive into “how” to secure your serverless applications. Let’s first talk about “why” you need to secure serverless applications. As you can imagine, just because serverless is abstracting the compute resources doesn’t mean it’s abstracting all of the security considerations. Why do I need to secure a serverless application?


Google Cloud Platform Serverless Ingestion into Splunk

If you have or plan to collect data from Google Cloud Platform (GCP), you will have noticed that your option of ingesting data has been by using Splunk’s Google Cloud Platform Add-On. However, many customers are adopting “serverless” cloud services to deliver their cloud solutions. There are many reasons for this, but mainly it provides solutions that do not require any overheads of server or container management, that scale and is delivered as a part of their cloud platform.

Lowering the TCO of your Serverless solution with Serverless360

Total Cost of Ownership for enterprise software is the sum of all direct and indirect costs incurred by the software and is a critical part of the ROI calculation. The reality of the cloud support process is that the user will end up paying more money depending upon the severity of the problem. For Instance, the support ticket resolved by 1st or 2nd line support teams would cost less than being resolved by the Architecture team.

Why Is End-to-End Tracing Important For Serverless

Serverless has become extremely popular with software companies, and has become one of the fastest-growing cloud service models. According to forecasts, its market will reach $22 billion by 2025. While serverless has ushered in a new era of technological advancement, it has also brought new challenges. Application debugging and monitoring, for example, have become much more complicated.


How to optimize AWS Lambda performance

AWS Lambda has become the most widely used deployment pattern for serverless applications. It allows developers to set aside worrying about server provisioning, maintenance, idle capacity management and scaling, and instead to focus solely on writing business logic. But that’s not entirely true. Because while Lambda is a self-managed AWS service, it still requires careful design to get the best performance out of the computation capabilities it provides.