Need suggestions on production usage #1561
saurabh-git-dev
started this conversation in
General
Replies: 1 comment
-
|
Absolutely no prob in production environment. Rock solid. Even for mission critical systems. |
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.
-
I want to use Loco in production. Would you recommend? How likely is it that the loco API will change in the near future? I am almost going to utilize 70-80% of the features provided by the loco. All basic functionality to write API and some part of HTMX, additionally Static files embedding, Worker, Scheduler, Mailing, Websocket(may be use SocketIO), Caching, OAuth. Some of the things I don't like, but I believe I can customize easily.
Coming from a NestJS TypeScript background. Everything is ok with NestJs, except for a few things(Database migration, the way deps are managed, and large Docker images). Loco database migration with SeaORM is amazing. In NestJS, we have many options. but I don't like the way they are doing it. I was using TypeORM earlier, but those are not maintained anymore and also lack a few features.
Beta Was this translation helpful? Give feedback.
All reactions