Madoc Batters

I have always liked using AWS Lambda for serverless functions but there are other options out there like Cloudflare Workers. Seeing examples of new tools is always a good way to learn. Cloudflare Workers are a type of serverless function where the runtime is based V8 JavaScript and WebAssembly. They offer very fast performance and, from what i've seen so far, a great developer experience. There isn't as much external tooling around them yet (like support for Terraform) but i believe that is being worked on. The article below from Adnan Rahić provides some good starting info including workers interacting with a D1 Serverless SQL database and details on using OpenTelemetry for tracing.

20

Using serverless tools on AWS can allow you to achieve a very large scale of throughput for your application without being required to provision or manage much (if any) resources yourself. Of course this also means you need to keep a close eye on your bill and have proper observability to make sure you don't get hit with a huge and unexpected bill. The post from Adithya M below shows a real world example of using serverless components like the Eventbridge Scheduler, AWS Lambda, the Simple Queue Service (SQS), and the Simple Email Service (SES) to schedule and send over a million emails. https://lnkd.in/eBj6-hXu

36

In the world of Kubernetes, Node Affinity ensures your pods only run on designated nodes. Imagine a pod requiring a special GPU labeled node for processing power. Carpenter, an infrastructure management tool for AWS EKS, helps with this by automatically scaling your cluster based on these needs. This video showcases how to leverage Node Affinity with Carpenter on AWS EKS. It guides you through: 1. Setting up an EKS cluster and configuring Carpenter 2. Creating a deployment with a node affinity rule (e.g., requiring a node labeled eks:immersion-team=my-team) 3. Carpenter automatically provisioning a new node with the required label 4. Modifying the deployment to demand a different instance type. Carpenter responds by deleting the old node and creating a new one meeting the new specifications By the end, your pods are up and running on the newly created node. This video is a great resource for anyone using Kubernetes on AWS EKS, especially if you're looking to streamline pod placement and cluster scaling using Node Affinity and Carpenter.     #Kubernetes #EKS #NodeAffinity #Carpenter #CloudNative #Carpenter   https://lnkd.in/eehZh_C7

8

In this blog post, learn about SentinelOne’s Singularity Cloud Workload Security (CWS) for Serverless Containers, a real-time cloud workload protection platform (CWPP) for containerized workloads, running on AWS Fargate for Amazon ECS and Amazon EKS. Powered by AI, CWS detects runtime threats like ransomware, zero-days, and fileless exploits in real-time, and streamlines machine-speed response actions. #noble1 TOM SHAW

1

I say this as someone who enjoys and works extensively with Kubernetes: if your containers are the size of VMs, you either need to work on slimming them or you should probably just be using traditional virtualization. A lot of companies are running Docker and k8s just because that feels more modern and the devs want it on their resumes. If your boxes aren't stateless and portable, it's quite probable that containerization is just adding complexity and burning engineer time.

213

25 Comments