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.
Gradual OLTP DB Development - from Zero to 10 Billion Transactions per Year and Beyond
December 13, 2016 by • “No Bugs” Bunny
Quote:
to make an efficient representation usable for OLAP – we need to modify our data on its way to OLAP replicas
Another Quote:
Each of the DB Server Apps is a replica master, but all replica targets are within the same Replica DB
Filed under: Book: D&D of MOGs1st beta of Vol. IV-VIOn.System ArchitectureDesign decisionsDistributed systems(Re)Actors
Read moreRepresenting The Same Data Structure in SQL and NoSQL (from Classical Codd-style SQL to Key-Value NoSQL with SQL-with-XML and Structured NoSQL in between)
December 5, 2016 by • “No Bugs” Bunny
Quote:
while duplication MAY indeed improve performance – undue duplication also MAY hit performance pretty badly
Another Quote:
NoSQL will usually call for another denormalisation on top of what we’ve described above for SQL-with-XML.
Filed under: Book: D&D of MOGs1st beta of Vol. IV-VIOn.System ArchitectureDesign decisions
Read moreOLTP. Compiling SQL Bindings.
November 28, 2016 by • “No Bugs” Bunny
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 moreHistorical Data in Databases. Audit Tables. Event Sourcing
November 21, 2016 by • “No Bugs” Bunny
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
Six Impossible Things Before Breakfast Ltd. © 2026. All rights reserved.
