Every day that I commute home, I check Google Maps for the next Trimet bus arrival at the usual stop. There’s nothing wrong with this ritual but it always distracts or leaves me stalled for a few empty minutes. Ever the proponent of laziness automation, I decided to build a stack that will do this for me by texting incoming arrival times for my bus home.
Ben Kehoe wrote a post about AWS API Gateway to Lambda integration: How you should — and should not — use API Gateway proxy integration with Lambda. In his post, Ben gave a few reasons why he believes using API Gateway Proxy Integration is an anti-pattern. Ben does a great job summarizing how the integration works. He writes: The pattern that I am recommending against is the “API Gateway proxy integration” as shown in the API Gateway documentation here.
As a company providing tooling to enable developers and operations teams to adopt a productive serverless workflow, Stackery is closely integrated with Amazon Web Services (AWS). Our customers are development teams who want to confidently build on AWS serverless and then manage the pipeline to production with confidence that what gets built and changed is done efficiently and well.
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.
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.
I was recently called upon to secure an Nginx web server with HTTPS, and my goal was to set this up with a certificate obtained from AWS Certificate Manager. It took me a while to figure out how to get everything configured and working. Hopefully someone else who is attempting to do the same thing will read this and I can save you some time!
Back in Part I of Deploying a Serverless Data Processing Workflow with AWS Step Functions, Nuatu mentioned one key benefit of using step functions is their visibility into business critical workflows. Outside stakeholders, support staff, and other engineers can look at a state machine execution in AWS or Stackery, and can easily understand the process.
Serverless has the potential to bring massive ops advantages to projects of all sizes, but while it presents great business benefits, we need to spare a thought for how teams develop on serverless. I recently published ‘Serverless Development is Broken’ a list of concerns about how developers can work with long deploy times inherent in a cloud-only code environment.
Many people writing about AWS Lambda view Node as the code-default. I’ve been guilty of this in my own articles, but it’s important to remember that Python is a ‘first-class citizen’ within AWS and is a great option for writing readable Lambda code. Take a look at these two starter examples of writing functionality in Python.
