3 ms·
Did you guys consider Heroku PostgreSQL? It's inside of AWS. If so, can you shed some light on why you opted against it? I don't want to sound like a fanboy of
by whalesalad 14y ago
Did you guys consider Heroku PostgreSQL? It's inside of AWS. If so, can you shed some light on why you opted against it? I don't want to sound like a fanboy of Heroku (I am not) but I am just interested in whether or not you guys considered it.
- simonw 14y agoWe didn't - it's a fantastic product (I'm really impressed with how easy they've made it to set up followers and forks) but we were ready to move to dedicated hardware. It's also a pretty expensive option.
- whalesalad 14y agoThanks for the response. I used to agree with you on the price until I realized that with Heroku you're essentially paying for a dedicated server with that much RAM for each plan. Reason being, every single database is "hot" and the entire thing lives in memory to avoid I/O. On second glance ... you're right. It is kind of pricey. Speaking of moving to dedicated.. I'd love to hear some of your general feedback on how AWS has been at some point. Essentially where you'd use it again or where you'd go directly to dedicated (or a diet option like a VPS) if you were starting on a new project.
- gsibble 14y agoI've worked in similar environments and Heroku is crazy expensive and slow compared to dedicated hardware.
- jaequery 14y agosad thing is, most people don't realize how slow they are. once they move off to dedicated w/ SSD, their site starts to run blazing fast (plus at a fraction of the cost) and say to themselves why they haven't done this sooner.
- gsibble 14y agoIndeed. Most companies don't have the operational experience to optimize for speed until they are later stage. Also, they will develop on something like Heroku and get addicted to the ease of use.
- joevandyk 14y agoDo SSDs improve performance with PostgreSQL if most of your data fits in ram? I guess it depends on the type of workload (reads vs writes).
- X-Istence 14y agoYes, it improves performance because PostgreSQL wants to write data out to disk before returning.