Questions on Using `@effect/workflow` in a Monorepo with Next.js and Node.js APIs
Hi, I am looking at using
We have a monorepo, which contains both a Next.js application with a tRPC API, and a regular Node.js API with Effect's
Here are my questions:
1. Is it possible to create a shared package for my workflows, so I can trigger them from the Next.js application, but run them on the API? The API is less mission critical, so I prefer to offload any long running stuff to it
2. Our main database is a MySQL database, which both applications connect to. Is this enough for the workflow engine, or do we require more parts of Cluster to make this work properly? The
@effect/workflow for some our stuff, but have some questions and hoping someone can validate my thinking.We have a monorepo, which contains both a Next.js application with a tRPC API, and a regular Node.js API with Effect's
HttpApiHere are my questions:
1. Is it possible to create a shared package for my workflows, so I can trigger them from the Next.js application, but run them on the API? The API is less mission critical, so I prefer to offload any long running stuff to it
2. Our main database is a MySQL database, which both applications connect to. Is this enough for the workflow engine, or do we require more parts of Cluster to make this work properly? The
@effect/workflow readme makes me think it is, but I may be missing something
