Shipped

🎉🔗 Tech Enthusiasts, Assemble! 🔗🎉

Calling all DevOps heroes, Kubernetes sailors, Golang wizards, and Cloud-natives! 🚀
FAUN has Subreddits just waiting for you. Join the community, where sharing is caring, and knowledge is limitless! 🌟

• 💻 Live and breathe DevOps? Join DevOpsLinks!

• ⚓ Mastering the K8s? Set sail on KubernetesLinks!

• 🐹 Go-ing crazy for Go? Get in on GolangLinks!

• 🔐 Got security woven into your code? Secure your spot at DevSecOpsLinks!

• 🐍 Pythonista at heart? Slither into PythonLinks!

• 🤖 Curious about AI’s endless possibilities? Get smart with AILinks!

• ☁️ Navigating the Cloud-native space? Soar through CloudNativeLinks!

• 💡 Got code in your veins? Share your snippets at ProgrammingLinks!

• 🌩️ Mastering the Azure skies? Fly high at AzureLinks!

• 🌍 Exploring Google's cloud horizon? Discover wonders at GoogleCloudLinks!

• 🌦️ Sailing through Amazon's vast cloud? Embark on AWSLinks!

• ⚡ Harnessing the power of Serverless? Energize at ServerlessLinks!

Engage in thought-provoking discussions, share your mighty projects, soak in wisdom from industry gurus, and forge bonds with tech aficionados around the globe! 🌍🔗💬

The realms of knowledge are infinite – let's explore them together! 🚀🔥

AWS Amplify introduces the UI Builder Figma plugin, allowing design and development teams to collaborate seamlessly in Figma. This plugin enables users to generate React code from designs within Figma, providing a live preview and easy integration into applications.

AWS Lambda now supports starting from a specific timestamp when using Amazon Managed Streaming for Apache Kafka (MSK) or Self-Managed Kafka as an event source. This allows for precise processing of messages at a desired point in time, beneficial for scenarios like Disaster Recovery. The feature incurs no additional charge, and more information can be found in the Lambda Developer Guide for Amazon MSK and Apache Kafka.

Serverless application developers can now simplify the process of building AppSync powered applications in AWS Serverless Application Model (AWS SAM) by using the new AWS::Serverless::GraphQLApi resource abstraction. This resource type allows users to define an AppSync GraphQL API in a single resource, including the API schema, resolver pipeline functions, and data sources, while also providing SAM CLI support for automatic packaging and uploading of code files. This resource is available in all AWS commercial regions, except China and GovCloud, and documentation is provided to help users get started.

AWS Step Functions now offers Versions and Aliases, enhancing deployment resiliency for serverless workflows. This update allows users to set up continuous deployment, maintain multiple workflow versions, track execution versions, and create aliases for traffic routing, enabling safer and faster iteration and release into production.

The AWS Serverless Application Model (SAM) CLI introduces the remote invoke command, allowing developers to quickly test their AWS Lambda functions deployed in the AWS cloud. This feature, available in SAM CLI version 1.88.0+, enables users to invoke Lambda functions with various options and eliminates the need for using AWS Console or AWS CLI for testing, improving the build-deploy-test iteration loop.

Deno's latest release brings us closer to its vision of making programming simple by offering a stable and high-performance web server API, Deno.serve(). It also improves npm support and adds highly anticipated packages, along with other improvements and bug fixes. Additionally, this release includes changes to the Deno API, Web API, standard library, and updates to V8 and TypeScript versions.

Moonpig, a heavy user of AWS Lambda, shares their recent findings on Lambda performance and cost tuning. They emphasize the importance of right-sizing functions by considering memory allocation, CPU profiles, and asynchronous versus synchronous workloads. They also highlight the benefits of using AWS's Graviton CPUs and the challenges of adopting Lambda Layers for managing parameter wrangling.

Solaris performs massive amounts of processes, including asynchronous tasks that require notification upon completion. They employ a publisher-subscriber model to deliver millions of messages per day to partners, but their legacy solution faced limitations in scalability. To address this, they redesigned their architecture to prioritize robustness, fast delivery, and containment of retries, utilizing serverless components like SNS, SQS, Lambda, and DynamoDB. They also conducted performance tests and learned important lessons about error handling, batch processing, and parallelization. As a result, their system now successfully handles millions of messages per day with impressive latency metrics.

The rise of third-party database providers, known as Database as a Service (DBaaS), offers developers the option to use external database hosts instead of hosting databases on the same server as their primary application. These "serverless" databases relieve developers of the responsibility of maintaining a database appliance and often provide useful features like dashboards, data browsing, and schema versioning. When selecting a database, the choice between relational tables (SQL) and document storage (NoSQL) is crucial, but access speed, particularly for simple queries, is the second most important consideration. In tests conducted with various third-party database vendors, AWS's DynamoDB emerged as the fastest option for querying data from a Lambda-based application, boasting a repeatable query latency of 10ms, which is 2.5 times better than its closest competitor. While all tested providers delivered query times under half a second, MongoDB was the only exception, but their paid tiers do offer better performance. It is important not to be paralyzed by the database selection process but to choose one and begin building the initial implementation.

Technology being discussed too early in the process can lead to underoptimized decisions and a focus on the end-state technology solution rather than requirements and business value. Containers and serverless technologies are well-suited for certain applications, but they do not apply to everything new, and complexity, increased costs, and vendor lock-in are potential downsides that need to be considered when adopting these technologies.

DynamoDB cross-region migration involves replicating or moving data from one AWS region to another, providing benefits such as disaster recovery, data locality, compliance, and global data distribution. Manual migration of a large number of tables can be challenging, time-consuming, and prone to errors. To address this, AWS Lambda functions and Step Functions can be used to automate and orchestrate the backup and restore operations, simplifying the migration process.

Azure, AWS, and Google Cloud offer various resources and services for building event-driven architectures. Each platform has its own messaging services, such as Azure Service Bus, AWS Simple Queue Service (SQS), and Google Cloud Pub/Sub, which allow for reliable message delivery and support different message patterns. Additionally, AWS provides AWS EventBridge, a serverless event bus, while Google Cloud offers EventArc for managing event ingestion and delivery. These platforms also have services like AWS Kinesis, Azure Event Hub, and Amazon MSK, which enable streaming and processing of real-time data.

We are thrilled to announce a special offer for our widely acclaimed book, "Cloud Native Microservices With Kubernetes - A Comprehensive Guide to Building, Scaling, Deploying, Observing, and Managing Highly-Available Microservices in Kubernetes".

Starting today and running until July 31st, we're offering an exclusive 20% discount off the regular price!

To take advantage of this offer, simply use this coupon link .

Don't miss this opportunity. Remember, the offer is only valid until July 31st. Grab your copy now and unlock the full potential of cloud-native microservices with Kubernetes!

We look forward to empowering your journey in the world of cloud computing!

Happy learning!
FAUN Team

libSQL is a fork of SQLite that is both Open Source, and Open Contributions.

Achievements that did not make the cut.

Starter template for a serverless website using Astro, WebAuthn, and Cloudflare D1.

The Apollo 11 guidance computer, which helped land humans on the moon, had less processing power than a modern-day smartphone.