3 ms·
Setting up a single postgresql is not that difficult indeed. But in a production scenario with decent uptime guarantees you are going to at least need master-sl
by vbsteven 9y ago
Setting up a single postgresql is not that difficult indeed. But in a production scenario with decent uptime guarantees you are going to at least need master-slave replication, make sure they fail over when the master goes down, have backups so you can do point-in-time recovery, rotate and ship the logs somewhere, apply security patches, and more.
Sure, I can do all that by myself but that takes time, time that is better spent serving my clients instead of setting up yet another replicated db. It takes me a few minutes to setup an Amazon RDS instance with all that enabled out of the box.
- always_good 9y agoAlso, "just run your own X" starts to fall flat once you grow beyond having a single project in your life.
- notyourday 9y agos/single project/single successful money making project/g Oh to have those problems
- notyourday 9y agoCould you possibly provide the chapter and verse of this dogma? The harsh reality is that the vast majority of the companies *do not have traffic or need to have 99.9% available infrastructure because they: a) do not have service that operates 24x7 b) do not have peopleware needed for 24x7 operations c) service customers that do not have 24x7 operations A metric boat load of now shuttered "startups" would have been going concerns providing very nice long term living (and retirement) to their owners had they been optimized for "not spending 109% of revenue for Yet Another Thing We Should Use As a Service".