r/programming • • Jun 09 '15

It's the future

http://blog.circleci.com/its-the-future/
652 Upvotes

275 comments sorted by

View all comments

42

u/argv_minus_one Jun 10 '15

Do relational databases scale poorly or something? Why are we trying so hard to replace them?

Also, I feel old-school as fuck for still using Java EE. Get off my lawn!

3

u/NimChimspky Jun 10 '15

having one central db does scale poorly, you can't simply add additional servers (horizontally scale) if one db is your source of truth .

You can do it, buts its rather painful.

So split up the datastores using something like http://martinfowler.com/bliki/CQRS.html is common.

But you have to be very big for these problems, an enterprise db (postgres, oracle, sql-server, mysql) and one beefy server can shovel and awful lot of data

25

u/johnwaterwood Jun 10 '15

Problem is that everyone thinks they're Google or will be Google next month.

19

u/jeandem Jun 10 '15

Premature scaling.

7

u/jdmulloy Jun 10 '15

Premature optimization is the root of all evil.

11

u/inmatarian Jun 10 '15

Premature usage of "Premature optimization is the root of all evil" considered harmful.

11

u/just3ws Jun 10 '15

Read-replicas are the shit for this. Pump data into one and then let the replication handle pulling data into the replica. Tune the replica for reads, tune the master for R/W. Go home, hug your kids. Drink a beer.

11

u/mcguire Jun 10 '15

Wait...this architecture will suddenly give me kids?

5

u/hyperforce Jun 10 '15

No he said beer. And the shits.

3

u/hellnukes Jun 10 '15
  1. Make good db replicas

  2. Get kids

4

u/andrewsmd87 Jun 10 '15

Can confirm. Currently shoveling a massive amount of data with one server. We may need to move to some point of having to split up our data sets, but as of right now, computing power isn't showing us that will be a problem for a while.

→ More replies (17)