Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> My app with a couple of hundred thousand users

per year? per month? per day? simultaneously? doing what?

it matters.

i ask this as someone who runs a $40/mo Linode with a debian/nginx/node/mysql stack that's definitely 20x over-provisioned for an e-commerce site with 10k daily visitors, 15 simultaneous backend users (reporting, order-entry, CRM, analytics) and 0 caching tricks. i could easily run the site on any 5 year old laptop with an SSD and 8GB RAM.

normalize/de-normalize when needed, understand and hand-write efficient SQL queries (ditch ORMs), choose small/fast libs carefully (or write your own), and you can easily serve 100k users per day on a single cheap VPS with no orchestration/replication/hz-scaling bullshit. definitely can't say the same about 200k simultaneous users - that would need proper hardware, but can still be a single server.

Monoliths Are the Future: https://news.ycombinator.com/item?id=22193383



>(ditch ORMs)

Depends on which ORM you use I think. Basic ORMs like Dapper in .NET just map your SQL query result to a object model.


Dapper's a "micro-ORM" and quite lightweight. Usually folks intend ORM to refer to Hibernate or Entity Framework, maybe ActiveRecord, etc.


hand-write efficient SQL queries (ditch ORMs)

Raw SQL strings or a query builder?


doesnt matter. query builders are negligible overhead.


What is the e-commerce site?


i'm working on a blog post about the tech choices & stack. maybe it'll make it to the front page in a month or two - that'll be a good stress test!


Are you offering a free stress test? :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: