Exploring AWS Aurora Serverless v2 for cheap WordPress usage
Summary: I wanted to know if the new Aurora Serverless V2 could be used for a cheap wordpress instance, I was disappointed.
Summary: I wanted to know if the new Aurora Serverless V2 could be used for a cheap wordpress instance, I was disappointed.
Summary: This article goes over AWS HTTP API Gateway (which is still in beta) for AWS Lambda targets. There’s currently few examples, and a bug in a basic configuration that prevents the chain of services from working
Summary: Is API Gateway merely a front end to your Lambda, with no additional configurations? Do you run multiple APIs? Do you see >5 million requests/month in traffic? Perhaps you should switch to an Application Load Balancer Proxy. Here are some considerations.
Summary: AWS Lambda through API Gateway binds requests to lambdas in 1:1, which means cold starts are likely if you receive more parallel requests than you have lambdas available to de-thaw. For more information, read below…
In short: This article will help you take an existing snapshot and reduce the initialization time of dirty snapshots (snapshots that contain large amounts of deleted data) by removing the dirty blocks from your snapshot. Combined with a tool like fio
or dd
to read over the disk, your initialization times should be reduced.
Summary: This article will hook up GitLab group (or project) runners to AWS Spot Instances through docker-machine, which in my professional experience gave us ~3-4 extra concurrent workers while reducing our cost by ~60%. This is mostly achieved by only spawning CI/CD instances only as they were needed and getting lower Spot instance rates.