The latest News and Information on Serverless Monitoring, Management, Development and related cloud technologies.
If you’ve dealt with lambda functions you may have run across the RequestEntityTooLargeException - * byte payload is too large for the Event invocation type (limit 131072 bytes) AWS Lambda exception that occurs when a function is invoked with too large of a payload. Current AWS Lambda limits are set at 6 MB for synchronous/RequestResponse invocations, and 128 K for asynchronous/Event invocations.
In the unlikely event that you might not already hear this, AWS Lambda is Amazon’s answer to the serverless computing. The theory behind serverless computer services is, as it sounds, to create a network for a variety of purposes while bypassing the need to have and maintain expensive servers. With AWS Lambda, you are at top of the class in serverless computing. The setup and management is a breeze.
Yesterday our founder and CEO Nate Taggart announced his decision to step down from his post. While his presence will be missed by all of us, he made this choice in order for Stackery to bring in a new CEO with the experience and pedigree to steer the business to the next level.
When I browse Stackery’s documentation and blog, I see some great writing that I know not everyone has read. Check out these great articles essential to growth as a developer.
API Gateway is a powerful tool for creating a coherent API out of a set of multiple disconnected remote function providers, and API Gateway with AWS Lambda, when used properly, can give you the capacity to create truly powerful serverless APIs. However, given that API Gateway is a layer between your requests and the code itself, there are latency concerns that API Gateway Lambdas may face that may not be present when working with other architectures.
