We have read and selected a few articles and other resources about the latest developments around cloud technology so you don’t have to. Read further and keep yourself up-to-date in five minutes!
Why is there no June 2021 edition?
You probably noticed that we skipped the June 2021 edition. We have been quite busy working on other awesome stuff, for example the Google Cloud Platform User Group Benelux and the “Designing Serverless Applications on AWS” talk for the End2End Live Conference. Watch the recording below!
Where should I run my stuff? Choosing a Google Cloud compute option
Where should you run your workload? It depends…Choosing the right infrastructure options to run your application is critical, both for the success of your application and for the team that is managing and developing it. This post breaks down some of the most important factors that you need to consider when deciding where you should run your stuff!
The execution environment of a Lambda gets reused when it is executed multiple times. Usually code ignores this fact but a very common optimization is to load settings only the first time your code runs in the execution environment. The extension API, that is available for extension writers, now gives standardized access to life-cycle information of the execution environment. There are many ready-to-use extensions from AWS partners and open source projects, but you can even write your own extensions. An extension is usually just a code “layer” you can add to your Lambda.
The ultimate App Engine cheat sheet
App Engine is a fully managed serverless compute option in Google Cloud that you can use to build and deploy low-latency, highly scalable applications. App Engine makes it easy to host and run your applications. It scales them from zero to planet scale without you having to manage infrastructure. App Engine is recommended for a wide variety of applications including web traffic that requires low-latency responses, web frameworks that support routes, HTTP methods, and APIs.
StepFunctions now supports EventBridge
Before you had to go through something like Lambda to generate EventBridge events from a StepFunction. Now support has been added to the StepFunctions implementation to do this more efficiently without the need of extra code or infrastructure. This simplifies this kind of serverless solutions greatly!
Maximize your Cloud Run investments with new committed use discounts
One of the key benefits of Cloud Run is that it lets you pay only for what you use, down to 100 millisecond granularity. This is ideal for elastic workloads, notably workloads that can scale to zero or that need instant scaling. However, the traffic on your website or API doesn’t always need this kind of elasticity. Often, customers have a steady stream of requests, or the same daily traffic pattern, resulting in a predictable spend for your Cloud Run resources. Google Cloud is now introducing self-service spend-based committed use discounts for Cloud Run, which let you commit for a year to spending a certain amount on Cloud Run and benefiting from a 17% discount on the amount you committed.
EventBridge supports sharing events between event buses
Using EventBridge is a good way to create a decoupled event-driven architecture. Using routing rules you can now route events to other buses in the same account and region. Using this feature you can either fan out events to different event buses or aggregate events to a single bus.