is there a way to run multiple workers locally?
e.g. /posts and /comments from separate workers? I'd like to setup some kind of proxy so that the client doesn't need to deal with anything different than whats in prod.
1 Reply
@skye_31 I've done that, however it blows up due to looking for the same ports
the version I'm using is 2.13.0
using turborepo running all
dev commands at once so I don't need to have so many terminals, I guess its running them in parallel and that might be where the edge case is coming from
do you think this is something worth a report?
definitely an edge case, but if there's a way around it would be nice
yeah, makes sense, that's why I asked 🙂
anyway, thank you for your quick response.
one last thing if you don't mind
is there a way to route all of the workers to some kind of proxy easily so the client app doesn't need to be aware of all the workers it communicates with? e.g. something that a load balancer would normally be in charge of?
it looks like I could create another worker that stitches them all together through bindings, but that seems like the wrong abstraction for prod
wouldn't that mean if your entry worker some how has connection issues that all of your services would then suffer from that?
this is my first serverless project, so please excuse my naivety.
hah, I guess you have a point there, I didn't think about that. Thank you.
@skye_31 do you have a rule of thumb as to why you would use one approach over the other?
okay, thank you for the context, I really appreciate it! Especially on a Sunday! So thank you so much 🙂