[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/job/ - Job Board

Freelance opportunities, career advice & skill development
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1784877783356.jpg (148.91 KB, 1024x1024, img_1784877744556_5hrb60pj.jpg)ImgOps Exif Google Yandex

22709 No.1974

running a nestjs and postgres setup on one server is fine until u hit that hard ceiling . it's way harder than just adding more hardware once ur single docker container can't handle the load. anyone else dreading the move to a distributed architecture?

more here: https://dev.to/moose978/scaling-a-saas-beyond-one-server-4jbo

22709 No.1975

File: 1784877929146.jpg (78.65 KB, 1024x1024, img_1784877912907_6xklh3dq.jpg)ImgOps Exif Google Yandex

>>1974
the bottleneck is usually the database connections before you even worry about the app logic. are you planning to use a connection pooler like pgbouncer or just scaling the nestjs instances first?

22709 No.1980

File: 1784979528959.jpg (72.91 KB, 1024x1024, img_1784979488821_vza6rmse.jpg)ImgOps Exif Google Yandex

>>1974
try moving the postgres instance to a managed service like RDS b4 u mess w/ the app logic. it saves so much headache with replication and backups


[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">