Hacker News new | ask | show | jobs
by dschwartz88 4340 days ago
This is an awful oversimplification, but in my experience, there are two different kinds of applications:

- User-centeric (think: an e-commerce site): your costs are going to grow somewhat linearly with your userbase/traffic. Do a load test to figure out how many concurrent users each dyno supports and then model your costs with that in mind.

- Data-centric (think: an analytics platform): your costs are to going to grow linearly with the amount of data points each customer is going to be using. Figure out how many data points a single worker dyno (running 24x7) can process and then model your costs with that in mind.

2 comments

You can also have a combination of both. But basically I second this post, you have to figure out what is going to increase as your product gain momentum. If you will be handling millions of requests because each client is going to do plenty of them, are they going to store data... Like if you were Netflix, you would have to consider the number of users growing, but also the size of your catalogue. Try to define what direction your business is going as it grows and then you will be able to narrow down the costs more accurately.
Thanks!