Aktuelle Änderungen Printable View Änderungen Bearbeiten
ActiveRecord > ActiveXDataObjects > AdHocProgramming > Hacking > AdSenseInXHTML > AdSenseTracking > Agile > AgileSoftwareEngineering > Agility > AgileSoftwareEngineering > Aikido > Ajax > AlanTuring > AlexanderStepanov > AlfonsKemper > AllRecentChanges > AlternativeDBSystemsClear TrailI’m personally convinced that write consistency is the reason RDBMS are imploding under their own weight. Features like referential integrity, constraints and atomic updates are really important in the client-server world, but irrelevant in a world of services.
You can do all of that in the service. And you can do better if you replace write consistency with read consistency, making allowances for asynchronous updates, and using functional programming in your code instead of delegating to SQL.[2]
Despite million man years of research databases are actually pretty dumb. You have to tell them about every nuance of your schema, you have to tell them about indexes and so on. If you forget an index they are perfectly happy to run sequentially run through all the data you ever inserted into them many times a second.[3]
You have to pay attention to the order of your commits, getting the more important ones in first. At each commit you have to check that it succeeded and decide what to do if it fails.