Entries in Architecture (3)
Terracotta - the return of OODBMS?
Do you remember?
About 10 years ago OODBMS (Poet, Gemstone, Versant, ...) seemed to be starting to replace RDBMS; The idea for using OODBMS was simple - if the programming model is OOP why not persist Objects with an OODBMS directly instead of populating it's properties and class hierarchy into a couple of tables? It was the reason Oracle 8 came with object relational features; But they (OODBMS) failed for following reason:
Oracle 12 the Green Database - Oracle 12 Eco
Now living in a time of financial crisis and a growing gap of natural resources
a new paradigma - a new database paragdima is needed.
For Oracle 12 i think this could be Oracle 12 Eco;
Accessing Application Data only via PL/SQL Procedures?
Dear reader,
frequently i hear from different sources that a solid access to the Database must be based on a PL/SQL API - a technique wrapping Table access with PL/SQL. Currently i support a project developing a CRM system based on C#/.NET 2.0 and using an ORM (Object Relational Mapper) to store the content of the application. At the beginning of the project i was indeed sceptical about this approach. But on the long run i experienced it as a remarkable alternate approach interfacing a database for an application.

