It’s been a long time in the making but after months of pushing it on the back burner, we are finally ready to release our news project. Serverless technology has evolved at a thrilling pace. As a result of the rapid growth and expansion of this whole new space, many developers felt overwhelmed.
Ever since FaaS platforms inception, blogs, and benchmarks measuring and analyzing "cold start" emerged. No wonder that the most searched term in the topic of serverless on Google is "cold start". However, using the term "cold start" distracts us from what we really care about - "Invocation Overheads". Although cold starts are a part of "invocation overheads", focusing solely on them is misleading.
Whether 10 years ago or just last week, companies continue to ponder, “is cloud computing secure?” The truth is cloud computing is just as secure, if not more secure, than a traditional server if configured properly. In fact, most security breaches in the cloud are the fault of the customer, not the cloud network. Gartner Research estimates that between now and 2025, 99 percent of cloud security breaches will be the customer’s fault.
Since AWS Lambda’s introduction in 2014, which marked the beginning of the of serverless evolution, the development world has benefited from unprecedented levels of velocity and agility. As a result, developers have been able to focus on development of new features and innovation, without having to maintain or provision complex infrastructure.
AWS recently launched the Serverless Event Bus, AWS EventBridge. Some have described it as an extension of CloudWatch Events, while others say it is provides the same features as AWS SNS. So, what exactly is EventBridge? And how does it fit into the existing AWS serverless ecosystem?
You’ve no doubt heard that IOpipe has been acquired by New Relic (congratulations to both). As part of the acquisition, New Relic has said it intends to retire the IOpipe platform in the next 30 days. If you’re currently relying on the IOpipe platform to monitor and debug your serverless application you have an important decision to make. One option is to try out New Relic’s serverless monitoring functionality.
It’s been a great couple of months at Stackery. Since coming on as CEO earlier this year, I’ve been impressed with how much our team gets done and their contributions to making the serverless development experience easier and more reliable. I want to take a moment to recognize two of our amazing Stackerinos who were recognized by AWS recently with the AWS Serverless Hero distinction.
Back in 2017, Our CTO Serkan and other Opsgenie engineers were having a hard time monitoring their Lambda functions. They were used to dive deep inside Java applications with existing tools back at that time, and they were not able to achieve the same level for AWS Lambda functions. They made research on the possible options and came across a tool specialized for serverless monitoring: IOpipe.
Companies choose to transition to serverless computing for various reasons, mainly being faster time-to-market and reduced infrastructure costs. However, the root cause of their serverless security needs differ based on a myriad of factors. In this use case we will highlight a team struggling with traditional AppSec in serverless and finding security at serverless speed, their security driver and challenges, solution & ultimate results.
A Bit of History Not so long ago, the development, deployment, and maintenance of applications was much more complicated and time-consuming than it is today. In the very beginning, maintenance required fixes not only to the applications code, but also to supporting physical machines. Keeping servers, hardware, and software up-to-date were also critical tasks. In the 2000s, a new model called “Infrastructure as a Service (IaaS)” quickly became popular.
