Honey, I shrunk the Types—How Behavioral Types lose relevance on the edges of OO Applications
Golden West Room
Wednesday, 10:30, 30 minutes
John Kuriakose, Infosys Technologies
How Behavioral Types lose relevance on the edges of OO Applications and why a core Data fabric is useful for adaptability? OO Programs are built by first defining User Types within the language environment and then realizing program requirements by using the behavior defined by these Types.
We argue against defining types to deal with every scenario. OO Programs within an enterprise have to deal with the non-OO world that includes RDBMS, Other Applications, and Humans etc. On these EDGES that OO Programs interact with the non-OO world we have observed that there is little respect for Types and behavior and the requirements and expectation is most often data. If this is true, then OO application developers will repeatedly have to extract Data to and from Objects defined by Types to support the pure data interface that the non OO world supports.
In this paper we attempt to highlight some benefits we have realized by equipping an OO Application (Banking Middleware in Java) with a core representation for data which we refer to as the "data fabric". We further show that seemingly unrelated problems in Database persistence, data-binding, message data transformation and metadata management that appear within an Enterprise context can now be addressed well within the data fabric. The Data fabric is itself realized using reflective uniform data API defined using a few Types that abstract data definition as Meta-data.
This then reopens the case for OO developers to enhance their effectiveness with generic Data Models and principles of Data Driven Programming.