Workflows made simple (& durable). 🤝🔗☁️
Inngest, a durable workflow orchestration platform, helps developers build scalable products, like AI workflows, agents, & e-commerce stores, without the complexity of managing infrastructure. ➡️ https://do.co/4oQGVPx
A map of frameworks which provide Durable Execution workflows. Featured: Cadence, Temporal, Inngest and Cloudflare Workers.
Durable execution pattern in TypeScript and current landscape from Charly Poly at #dotJS
Tomorrow we're teaming up with our friends at Inngest!
Learn how to build a content localization engine that instantly translates all of your content into whatever languages you'd like when you hit save
👉 RSVP for the workshop: directus.is/workshop/in...
🆕 in the changelog: Prometheus metrics exports. You can now configure your external monitoring tools like Grafana or New Relic to scrape prom metrics for any Inngest environment.
www.inngest.com/changelog/20...
New in the changelog: New webhook management API endpoints are now available as part of the Inngest REST API. You can now manage webhooks and transforms in your codebase and as part of CI.
www.inngest.com/changelog/20...
🔥 new Inngest video tutorial for this weekend:
- How semantic search works under the hood ⚙️
- Automatically generate embeddings for your @neondatabase.bsky.social tables ⚡️
- Write your first vector SQL query 🔍
www.youtube.com/watch?v=priD...
Got my first taste of @inngest.com and I like it...
Start your year off with something new✨
Combine @inngest.com's workflow engine with Weaviate's vector search capabilities and create powerful agentic applications that practically run themselves! A big step up for anyone working with large-scale RAG systems.
Check out the blog! lnkd.in/gSW-xHVf
another day, another tedious task that the @inngest.com dev server made easy and safe to run 😍
Tips to quickly get your project up and running:
- Inspect your LLM calls directly from the Inngest Dev Server ⚡
- Uses the provided db/seed.sql file to setup your Neon database 🗃️
- Leverage @vercel.com's v0 to create your own UI ✨
To get started, go to the following repository and follow the instructions: github.com/inngest/inng...
You feel like coding this weekend? Here’s a coding challenge 🏆
Christmas is approaching! Build a Christmas dinner AI generator from scratch using @nextjs.org, @inngest.com, and @neondatabase.bsky.social 🌲
The most creative projects will be featured in the Inngest documentation!
this is the first time i've used @egghead.io this way for a quick technical video i wanted to share
it's unlisted so wont show up in our site search etc since it is rough
having easy to use video infra you own/control is fuckin rad
thanks @inngest.com
@inngest.com thanks for your software, one of my vendors had an issue with their API for two days.
After they got it fixed I could re-run the last two days of failed events with just a few clicks and everything got fixed 🙏
Starter packs make Bluesky immediately enjoyable - such a great idea. Here's another one I found: go.bsky.app/8udaK5Y
here's a podcast i was on talking about event-driven workflows podrocket.logrocket.com/mastering-du...
👋 hello world!
can't wait to show you what we've been working on over at @inngest.com this week. some great stuff about to be unleashed in the next couple of weeks.
it feels like we're only getting started!
All the code is open source for you to explore the flow end-to-end: github.com/inngest/mult...
We'd love to hear how you've addressed similar challenges with RAG pipelines in multi-tenant systems!
A system diagram of a RAG pipeline for ingesting and embedding user information. The diagram splits into two separate workflows per tenant.
With that in place, we use events to create an embedding workflow which uses Inngest's event batching keys ensure that each tenant's embeddings are processed & inserted in separate jobs creating a clean pipeline where only one user database is accessed in a single ingestion job:
An architecture diagram showing a multi-tenant RAG system with per-tenant databases and vector databases
The first step is using Neon's API to create a separate database and vector database for each tenant or user in your system:
How do you rely on user-provided information for RAG pipelines while ensuring there is proper data isolation?
We wrote an article on how to build multi-tenant RAG that leverages @neondatabase.bsky.social's db-per-user design and the multi-tenancy features of @inngest.com
neon.tech/blog/multi-t...
Here's your Friday reminder that local development for background jobs and async workflows doesn't have to be terrible. The Inngest Dev Server runs on your laptop and provides visual debugging and logs and one-click retries and invocations.
Excited to be part of the conversation!
We used the new
@inngest.com test helper library together with @vitest.dev, works smoothly so far! ✨
github.com/inngest/inng...
(clerkDeletedAt is our own tombstone flag using event timestamp as proxy—doesn't actually exist on Clerk because the whole record gets deleted there)
#buildinpublic
