2 ms·
Accountants invented the concept of a queue of transactions causing predictable updates. They also invented eventual consistency in the form of special and gen
by jacques_chester 14y ago
Accountants invented the concept of a queue of transactions causing predictable updates. They also invented eventual consistency in the form of special and general ledgers.
However, ACID is four requirements and they're all still valuable and useful defaults. Atomicity comes from double-entry bookkeeping, consistency from the idea that data is meaningless without structure, isolation from the demands of consistency and durability because people get grumpy when you tell that that umpteen jillion dollars may ... or may not ... have been recorded.
Like I said, I'm a data-safety bigot. I greatly prefer to start with a safe default and then relax the guarantees. Retrofitting safety is harder, especially when you don't have a uniform statement of what your data is.
For something like a blog, an RDBMS is probably overkill. And MySQL got its start in life because it so thoroughly (silently) relaxed the standard guarantees that it was much faster than anything else.
> major-version upgrade capable HA while under load
The strategies are the same as for NoSQL.
Either you stop the world, or you run versions in parallel and drain traffic from the old versions.
I also find it slightly hilarious that just casually upgrading something without exercising great caution is seen as a good idea.