You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For me personally there is one thing missing for Nitro to be a "complete package" for all my web projects:
Use Nitro not as a HTTP API, but as a microservice that listens to incoming requests from other sources like NATS, AWS SNS/SQS, Redis Pub/Sub, or similar. Also a hybrid solution is thinkable: One Nitro app that provides a public HTTP api but also listen for microservice events.
Probably this is not what Nitro wants to be, but what I like about Nitro (and Nuxt) is that it takes everything off my hands:
Create a new project with the CLI that just works
Dev environment with file watching
Bundling, HMR, Tree Shaking
Bundling for basically every environment (Node, Bun, Deno, Cloudflare, Vercel, ...)
Best practices
Integration of UnJS ecosystem as well as no restrictions in using other frameworks (e.g. Zod, Drizzle)
It would be amazing to have all this for a microservice as well!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
For me personally there is one thing missing for Nitro to be a "complete package" for all my web projects:
Use Nitro not as a HTTP API, but as a microservice that listens to incoming requests from other sources like NATS, AWS SNS/SQS, Redis Pub/Sub, or similar. Also a hybrid solution is thinkable: One Nitro app that provides a public HTTP api but also listen for microservice events.
Probably this is not what Nitro wants to be, but what I like about Nitro (and Nuxt) is that it takes everything off my hands:
It would be amazing to have all this for a microservice as well!
Beta Was this translation helpful? Give feedback.
All reactions