Best of Serverless — November 2024

  1. 1
    Article
    Avatar of theburningmonktheburningmonk.com·2y

    When to use Light Events vs. Rich Events in Event-Driven Architectures

    Choosing between light and rich events in event-driven architectures involves trade-offs. Light events, containing minimal information, are cost-efficient but may increase complexity for subscribers needing additional data. Rich events include more information, reducing the need for extra calls by subscribers but increasing data transfer and storage costs. Domain events, often benefitting from light events, are shared within the same domain, while integration events, suited for rich events, are shared across domains. Understanding these differences helps optimize event design and system efficiency.

  2. 2
    Video
    Avatar of joshtriedcodingJosh tried coding·2y

    I Wish I Made This SaaS Discord Bot WAY Earlier

    Discover how to set up a Discord bot to receive real-time notifications for events in your web applications. This guide walks you through creating a server, configuring a bot, and sending automated direct messages using serverless functions. Learn how to customize notifications with user data and make your web app interactions highly responsive and engaging.

  3. 3
    Article
    Avatar of theburningmonktheburningmonk.com·2y

    EventBridge best practice: why you should wrap events in event envelopes

    Learn why wrapping your event payloads in custom envelopes when using AWS EventBridge enhances structure, interoperability, filtering capabilities, versioning, idempotency, observability, and auditing. This approach provides a clear separation between metadata and business data, making it easier to manage, trace, and process events within your serverless architectures.

  4. 4
    Article
    Avatar of supabaseSupabase·2y

    Executing Dynamic JavaScript Code on Supabase with Edge Functions

    Supabase allows developers to execute dynamic JavaScript code in Edge Functions, enhancing flexibility and reducing the need for redeployments. Edge Functions execute at the edge for faster response times. Users can modify and run JavaScript code on the fly, supported by SQL scripts and helper functions like `edge.http_request`, `edge_wrapper`, and `edge.get_secret`. This setup increases the versatility of applications, enabling tasks like generating embeddings or creating users via the admin API.

  5. 5
    Article
    Avatar of communityCommunity Picks·2y

    Express.js is history? Why use Modern Frameworks in 2024?

    Elysia.js and Hono.js offer superior performance, modern JavaScript features, and optimizations for serverless and edge architectures compared to Express.js. They leverage modern development techniques, modular middleware, and WinterCG standards compliance, making them ideal for contemporary web development scenarios.

  6. 6
    Article
    Avatar of awsfundamentalsAWS Fundamentals·2y

    OpenTelemetry on AWS: Observability at Scale with Open-Source

    Learn how to implement an observability stack on AWS using OpenTelemetry, CloudWatch, and AWS X-Ray for serverless applications. This guide walks through configuring AWS Lambda for trace and log collection, and how the AWS Distro for OpenTelemetry provides a secure, production-ready solution for instrumenting applications with minimal code changes.

  7. 7
    Article
    Avatar of communityCommunity Picks·2y

    Lightweight Kubernetes and Wasm is a Perfect Combo

    Lightweight Kubernetes distributions like k3s, Microk8s, and k0s, combined with SpinKube, offer significant performance and resource efficiency benefits. Spin applications, which are WebAssembly-based, have minimal runtime overhead and can scale rapidly. This makes them ideal for both low-frequency use cases and high-traffic scenarios, as well as for edge computing where optimizing network latency is crucial.

  8. 8
    Article
    Avatar of communityCommunity Picks·2y

    Per-User Database Architecture with Xata, Clerk Webhooks, Hookdeck, and Next.js

    Learn how to implement a per-user database architecture using Xata, Clerk Webhooks, Hookdeck, and Next.js. This tutorial covers use cases that benefit from data isolation, security, and compliance, such as SaaS platforms, healthcare systems, and financial services. It guides you through setting up a Next.js application with Clerk for user management, Hookdeck for robust webhook handling, and Xata for creating per-user databases. Additionally, it demonstrates configuring webhooks and personalizing database regions based on user location.

  9. 9
    Article
    Avatar of theburningmonktheburningmonk.com·2y

    Here is one of the most misunderstood aspects of AWS Lambda

    Understanding AWS Lambda's throttling behavior is crucial. While synchronous invocations check for throttling limits, asynchronous invocations don't face immediate throttling issues as requests go through an internal queue. However, retries for failed async invocations happen up to 6 hours only. This clarification suggests you may not need SNS topics solely to prevent throttling errors, leading to fewer complexities and costs.

  10. 10
    Article
    Avatar of communityCommunity Picks·2y

    Why doesn't Cloudflare use containers in their Workers platform infrastructure?

    Cloudflare uses a V8-powered architecture instead of traditional containers in their Workers platform to deliver sub-millisecond serverless latency and serve a large number of tenants independently. This architecture leverages V8 isolates, which are lightweight, fast, and provide strict code isolation within the same OS process. While this approach offers significant performance advantages, it is limited to supporting only JavaScript and WebAssembly and may not suit compute-intensive or long-running tasks.

  11. 11
    Article
    Avatar of restateRestate·1y

    Distributed Restate - A first look

    Distributed Restate is an architecture designed for high availability, better durability, and scalability across multiple AWS regions. It features a log-first architecture, tight integration between its components, and a control plane/data plane separation. Restate ensures durability and consistency with synchronous log replication, leader/follower processor setup, and doesn’t rely on external databases. A demo showed successful order processing and consistency maintenance even during a regional failure. The system aims for a release in January, focusing on correctness and reliability.

  12. 12
    Article
    Avatar of infoworldInfoWorld·2y

    Can Wasm replace containers?

    WebAssembly (Wasm) is gaining momentum beyond web development, showing potential in areas like edge computing, serverless functions, and IoT due to its speed, portability, and security. While some see Wasm as a future replacement for Linux containers, experts believe containers will continue to dominate long-running server processes and stateful applications. The evolving landscape suggests a complementary relationship between Wasm and containers, with both technologies playing significant roles in cloud and enterprise computing.

  13. 13
    Article
    Avatar of hnHacker News·1y

    Glassdb: transactional object storage

    GlassDB is a transactional object storage solution designed as a client-side library that leverages the strong consistency of cloud object storage (e.g., AWS S3, Google Cloud Storage). It aims to bridge the gap between portability, transactional consistency, and cost-efficiency, typically challenging in cloud-based applications. The post covers the journey of designing GlassDB, touching on database design, ACID properties, optimistic locking, transaction algorithms, and the trade-offs involved. Key highlights include the use of distributed transactions, optimistic concurrency control, and local caching to optimize performance amidst the inherent latencies of object storage.

See all Serverless archives