Design decisions

When architecting a system, it is inevitable to make certain high-level design decisions.

Some of these decisions, if they’re wrong, can lead to the re-architecturing and re-writing of the whole system some months later, so there is an incentive to keep things rather generic. On the other hand, trying to make system too generic is just another recipe to disaster (usually expressed in terms of missed deadlines and unmanageable code).

IT Hares try to describe certain not-so-obvious architectural decisions, and some considerations which should be kept in mind while making them.

Choosing RDMBS for OLTP DB

November 14, 2016 by “No Bugs” Bunny

Multiple Connections vs Single Connection

Quote:

As the RDBMS keeps modifying its tables – the tables gradually degrade

Another Quote:

As we can see from the table above – choosing your RDBMS it is not as easy as it might seem.

Filed under: Book: D&D of MOGs1st beta of Vol. IV-VIOn.System ArchitectureDesign decisions

Read more

Ultimate DB Heresy: Single Writing DB Connection. Part II. Gradual Scalability. All the way from no-scale to perfect-scale.

November 7, 2016 by “No Bugs” Bunny

Multiple Connections vs Single Connection

Quote:

And after this split of USERS table, the system has achieved perfectly linear scalability.

Another Quote:

Start with a simple single-write-connection DB, with reporting running off the same DB

Filed under: Book: D&D of MOGs1st beta of Vol. IV-VIOn.System ArchitectureDesign decisions(Re)Actors

Read more

Ultimate DB Heresy: Single Modifying DB Connection. Part I. Performance (Part II. Scalability to follow)

October 31, 2016 by “No Bugs” Bunny

Multiple Connections vs Single Connection

Quote:

Dealing with transaction isolation is very far from being a picnic

Another Quote:

One of such real-world systems was consistently processing over 30M real-world write transactions/day over one single DB connection, supporting ~100K simultaneous players.

Filed under: Book: D&D of MOGs1st beta of Vol. IV-VIOn.System ArchitectureDesign decisions(Re)Actors

Read more

NoSQL vs SQL for MOGs

October 24, 2016 by “No Bugs” Bunny

SQL vs NoSQL. Box!

Quote:

in real world, after deployment, most of the changes in DB structure are about widening columns and adding the new ones

Another Quote:

For documents and BLOBs, NoSQL is a natural habitat

Filed under: Book: D&D of MOGs1st beta of Vol. IV-VIOn.System ArchitectureDesign decisions

Read more