Motia Work with Nestjs #360
blackrabbit944
started this conversation in
General
Replies: 1 comment
-
|
Or can we replace our entire NestJS backend from Motia? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Yesterday, I built a workflow using Motia—and honestly, it was a breeze.
The pub/sub-based model makes it super intuitive to visualize and build workflows. It’s clean, easy to understand, and quick to get started with.
But here’s my challenge:
My entire API system is built with NestJS.
And I’m not sure how to properly integrate Motia into that stack.
Right now, the only solution I can think of is treating Motia as a standalone service—have NestJS trigger it via HTTP calls. But this creates complexity when the result from Motia needs to be sent back to NestJS. It gets messy, fast.
Truth is, most people won’t rebuild their whole system just to adopt Motia.
They’ll want to plug it into existing infrastructures.
So my question is:
Are there examples of how to integrate Motia into an existing backend (like NestJS)?
And more broadly—should one of Motia’s goals be making integration into existing systems seamless?
Would love to hear how others are handling this.
Beta Was this translation helpful? Give feedback.
All reactions