• Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

The Generic API

Actually, he was. Were you there?
If it was in Wognum, NL, yes. What a f**king pile of tulipe.

Metadata and operational data all crammed in the same tables, nobody that knew the data model (basically there wasn't one), and some twunt who said 'we don't use referential integrity in oracle because it makes the performance worse'. FFS, the whole point of a RDBMS is referential integrity, but would Bob call Oracle and check his assertions with them? Of course not.

I didn't even get paid for half that contract because clientco AND agent went bust. The only good thing is that Bob didn't get paid either.
 
Last edited: 10:45
You mean an Entity-Attribute-Value database.

Good theory, awful practise.

Yeah, kind of, except it wasn't "sparse" data.

To be fair to said database vendor they advised in the manuals that each item (an in-flight proccess in a workflow system) have a small number of attributes corresponding to process state and keys in a properly designed relational schema.

Unfortunately the people who implemented the system at clientco didn't read the manual and every data item ended up as an atrribute of the associated process.

You can guess how the performance scaled with a few million processes and subprocesses (which would duplicate the data items they required) each having several hundred associated pieces of data.
 

Advertisers

Back
Top