I’ve built event-driven systems processing 1M+ events per month at startups. One thing that always caused headaches: Validation was left to downstream consumers. In Kafka, any data can enter a topic. Every consumer has to do its own validation. Miss one rule, and you end up chasing weird side effects or broken consumers — hours lost debugging what should have been caught earlier. (This is a sponsored post, but these are my own thoughts and ideas working with EDA a lot) But what if the broker itself guaranteed that only valid data ever enters? That’s what Bufstream does: •Kafka-compatible (drop-in replacement) •Understands Protobuf schemas natively •Validates events right on the broker Bad data never even reaches your topics — it’s rejected at the producer level. And because validation is built into the broker, you can define rules once and trust the system to enforce them everywhere. Cleaner pipelines, fewer consumer bugs, and less ops overhead. If you’re working with Kafka at scale and want to simplify data quality, it’s worth a look. 👉 Learn more here: fnf.dev/4lCaq6c

What are you using for dynamic emails? 💌 I'd love to have the ability for the following: We send out a weekly newsletter with a lot of dynamic content (e.g. @hashnode posts). A process I can think of that makes sense is: 1. Having a scheduled job that pre-fills a template in a campaign (the developer is doing that) 2. Marketing can check the campaign and preview the email for every user 3. Marketing can then send the emails The main goal here is to offload developers' involvement here. Template building and all sending can be done from non-devs. ❌ - I don't want to send the emails via an API - only prefill the data - Template engine can be used - no need to build templates ourselves in HTML or abstractions - Sending is taken care of, deliverability as well Any other suggestions? Happy to hear them! 😊

Wiring up @vercel's blog starter kit with @hashnode APIs 🫂

We're currently building a new personalized feed @hashnode and considering @getstream_io 🧑🏽‍💻 Our setup would be: - One feed group per user - Collection references posts - Activities (posts) are added to feeds The issue 🚧: Adding each activity to each user's feed would result in a very large number. Has anyone done something similar with Stream or a competitor? 🤔 Not sure if we're thinking about their concepts wrong. Happy for any help 🙌🏽