There is rarely a trace of memory when it comes to frame selection. If we were so worried, we would use a manual assembly of assembler code with everything that is aggressively compressed into memory, like some demoscene . This is obviously not the case.
Even Rails, which tends to be quite heavy, will only use ~ 100 MB per instance. When using 512 MB instances of approximately $ 20 per month, the net cost of each instance ends at $ 5. When accounting for OS overhead.
How many hours does a programmer need to end up costing you more than just buying a system with more bandwidth? Probably a lot if your time is not free.
Remember that you can always rent your own equipment for a small fraction of the cost of using a managed provider, where systems with 64 GB of memory can have less than $ 500 / month. As a result, it barely pays even a small share of a programmer per month.
I would pay attention to how a particular developer can work with your chosen structure. Some frameworks will work better for you, allowing you to work better. Sometimes paying for additional memory is a way to compensate for the increased development and optimization time, which is usually premature until you deal with tens of thousands of server accounts per month.
source share