Adopting a new standard will force a re-write of all Federal software. Push SQL back into the database where it belongs.
This I agree with. The only SQL that should be executed from the app layer should be calls to stored procedures.
All software is built to textbook standards.
Ehhh... I'm all for having a set of standard guidelines but at the end of the day, "the right tool for the job" should take precedence. I'll thake "Faster & More Efficient" over "Textbook" all day, every day.
Load/Store/Delete follows proper architectural n-tier design
???... I don't see that being defined anywhere, so no comment.
Most systems can be re-written side-by-side with no downtime.
Given unlimited manpower, hardware & $... Sure, anything is possible. I don't see a compelling argument that I could use to persuade those that hold the purse strings.
Supports surveillance and law enforcement while providing accountability.
Orwell's 1984 should be read as a cautionary tale, not an instruction manual.
As DBAs & Developers, our duty is to protect our customer's data , not support surveillance or law enforcement.
Sufficient savings can follow through on Congress' 'borrow and pay from savings' plan.
My libertarian must be showing by now... Seriously, just shoot me in the face now.
Allows control into the, otherwise opaque, 'cloud'.
? Okay... I'm done...
Seriously, there are already ANSII & ISO standards that each vendor follows to some degree and varies from to some degree... Which is how things should be is a free market system.
All database already have exposed interfaces that allow them to communicate with external applications. They'd be useless without them.
I don't see anything here that illustrates a "enormous efficiency and accelerates the development cycle" advantage to simply calling a stored procedure.