IT Hare on Soft.ware
If you're in trouble and cannot find an answer to a question which goes beyond Stack Overflow...
If you have a not-so-usual solution for your problems but need to justify it to your boss...
If you like to think on your own rather than blindly follow "common wisdom" and "profound truth"...
...then 'No Bugs' Hare on Soft.ware might be the right place for you.
Your mileage may vary. Batteries not included
 
“No Bugs” Hare		Author:“No Bugs” Hare  Follow: TwitterFacebook
Species:H.A.R.E. (as "Honest And Restless Engineer")
Job Title:Sarcastic Architect
Hobbies:Thinking Aloud, Arguing with Managers, Annoying HRs,
Calling a Spade a Spade, Keeping Tongue in Cheek
 
'No Bugs' Bunny

Once upon a time, in a rabbit outsourcing warren of Bunnylore, there was a young software developer bunny. And as a developer, he has had one very unusual treat: he was obsessed with eliminating all the bugs he can get his forelegs on. So, it is not surprising that his friends called him a “No Bugs” Bunny (or simply “NoBugs”).

Later on, he grew up, so he decided that “Bunny” in his name has became inappropriate (not to mention potential arguments with Warner Brothers), so he has asked all his friends to call him “No Bugs” Hare. He has made a career as a team lead and software architect, and they lived happily ever after.

“No Bugs” Hare Opera Omnia, Vol.16:

Historical Data in Databases. Audit Tables. Event Sourcing

posted by

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”
[→]

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

posted by

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”
[→]

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

posted by

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.”
[→]

Distributed Databases 101: CAP, BASE, and Replication

posted by

Quote: “The worst case of inconsistency happens when row X in database A is modified (by a Client connected to datacenter A), and the same row X in database B is independently modified too (by a Client connected to datacenter B).”
Another Quote: “One way to avoid reports affecting operational DB, is via creating a read-only replica of our main operational DB – and running our reports off that replica.”
[→]

Databases 101: ACID, MVCC vs Locks, Transaction Isolation Levels, and Concurrency

posted by

Quote: “for larger-scale MOGs, functionality-wise it is common to have 4 different types of databases: transactional processing (OLTP) DBs, real-time reporting DBs, archive DBs, and analytical DBs (OLAP)”
Another Quote: “both MVCC-based and Lock-based DBMS issue locks (and therefore, both can cause all kinds of trouble such as deadlocks etc.); however, the difference lies with the number of locks issued by them.”
[→]
Copyright © 2014-2016 ITHare.com