Today’s modern applications contain a broad set of microservices, with containers and serverless becoming the architectures of choice for many cloud applications. Both architectures facilitate highly scalable systems, and while which approach to take is routinely debated, containers and serverless technologies are being used in tandem more and more.
Since our founding, Lumigo has worked hard to build innovative technology that meets the real-world needs of our customers in a cloud-first world. Today, we’re excited to be recognized for our work in serverless operations and the AI market by the experts at Frost & Sullivan, who have awarded Lumigo with the prestigious Best Practices Technology Award in Europe and Israel.
Lumigo uses IntelliJ IDEs everywhere. The back-end developers love their PyCharm and us frontend developers use WebStorm all the time. No doubt that it’s one of the most popular IDE’s out there. One of the perks at Lumigo is that as employees, we can use 10% of our working time to invest in personal projects or do cool things for self-development and innovation.
AWS Lambda execution lifecycle has main phases: initialization, invocation, and shutdown. In the initialization phase, Lambda creates the runtime environment, downloads the code, imports everything needed, and runs the functions initialization code. In the invocation phase, the Lambda will get an input, process it, and produce an output. After the invocation phase, Lambda will go to an ideal state and wait for the next input.
When a startup is in its very early stages, rapid iteration and dynamism are at the top of its priorities. The ability to do so, while maintaining a stable and high-quality product, is a big challenge facing the R&D group. We want to release features as quickly as possible, but this rapid velocity cane cause conflicts when writing in-depth, comprehensive tests.
AWS announced the release of the Lambda Function URLs feature today. In this post, I describe what it is, how it works, and how you can benefit from it. API Gateway and AWS Lambda is a potent combination and lets you build REST APIs without having to worry about the underlying infrastructure. API Gateway offers many powerful features out-of-the-box, including: Understandably you pay a premium for these features.
Nowadays, microservice architecture is a pattern that helps to innovate quicker by enabling easier scalability, giving language flexibility, improving fault isolation, etc. Systems built this way also bring some downsides. Moving parts, concurrent invocations, and different retries policies can make operating and troubleshooting such systems challenging. Without proper tools, correlating logs with metrics may be difficult. To overcome these challenges, you need observability.
Every Lambda function comes with 512MB of ephemeral storage in the shape of a /tmp directory. This storage space can be reused across multiple invocations for the same instance of a Lambda function. Each instance of a function has its own /tmp directory and data is not shared amongst different instances of a function.
Observability is a measure of how well the internal state of a system can be inferred from its external outputs. It helps us understand what is happening in our application and troubleshoot problems when they arise. It’s an essential part of running production workloads and providing a reliable service that attracts and retains satisfied customers.
At Lumigo. we believe in serverless technology, and our mission is to make serverless development easy and fast. For the past few months, we’ve been extending our observability and debugging capabilities, making it a breeze for developers to understand the end-to-end story of every request that goes through the system, find the root causes of issues and be able to easily address them.
