#How!
6 messages · Page 1 of 1 (latest)
Nest is built on top of Express (or Fastify). The question about switching can only be answered by you and your team (if you have one). The reasons you might have to switch are, your current code base is getting unwieldy, due to its size. You want a (better) path to moving to microservices from logical and architectural standpoints. You want to be able to better abstract sections of code to their own libraries. You want to test your code easier and better.
Those were off the top of my head.
There were a couple other discussions about using Nest in parallel to Express here and I'm not sure if the possibility exists. I can't remember the outcomes because, IMHO, if you have an Express app and have the situation where one or more of the reasons I mentioned above are valid, then I'd highly suggest to just do a rewrite, even if it seems more painful at first.
darn beat me to it
huh?
You can also connect an existing app to Nest (via the ExpressAdapter) and rewrite piece by piece