Setting up a database server along with a couple of read-only
replications is harder. Adding a writeable failover secondary is harder >still. Making sure that everything works /perfectly/ when the primary
goes down for maintenance, and that everything is consistent afterwards,
is even harder. Being sure it still all works even while the different >parts have different versions during updates typically means you have to >duplicate the whole thing so you can do test runs. And if the database >server is not open source, your license costs will be absurd, compared
to what you actually need to provide the service - usually just one
server instance.
Clouds do nothing to help any of that.
According to David Brown <david.brown@hesbynett.no>:
Setting up a database server along with a couple of read-only
replications is harder. Adding a writeable failover secondary is harder
still. Making sure that everything works /perfectly/ when the primary
goes down for maintenance, and that everything is consistent afterwards,
is even harder. Being sure it still all works even while the different
parts have different versions during updates typically means you have to
duplicate the whole thing so you can do test runs. And if the database
server is not open source, your license costs will be absurd, compared
to what you actually need to provide the service - usually just one
server instance.
Clouds do nothing to help any of that.
AWS provides a database service that does most of that. You can spin
up databases, read-only mirrors, failover from one region to another,
staging environments to test upgrades. They offer MySQL and
PostgreSQL, as well as Oracle and DB2.
It's still a fair amount of work, but way less than doing it all yourself.
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 991 |
Nodes: | 10 (0 / 10) |
Uptime: | 120:18:30 |
Calls: | 12,958 |
Files: | 186,574 |
Messages: | 3,265,651 |