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.

OLTP. Compiling SQL Bindings.

November 28, 2016 by “No Bugs” Bunny

OLTP. Compiling SQL Bindings. - Post preview image

Quote:

If we’re speaking about millions transactions per day over just a few hundred of different SQL statements – compiling those statements a million times (instead of a few hundred times) will be a dramatic waste of resources.

Another Quote:

Once upon a time, I observed the largest C++ file in my career – it was a 30’000-line file(!) consisting merely of ODBC bindings (and that was just for 300 or so SQL statements)

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

Read more

Historical Data in Databases. Audit Tables. Event Sourcing

November 21, 2016 by “No Bugs” Bunny

Historical Data in Databases. Audit Tables. Event Sourcing - Post preview image

Quote:

99% of reporting requests and 99.9% of analytics is purely historical

Another Quote:

Information within the audit table should be sufficient to validate/justify current state

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

Read more

Choosing RDMBS for OLTP DB

November 14, 2016 by “No Bugs” Bunny

Choosing RDMBS for OLTP DB - Post preview image

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

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

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