data access tier options
-
hi there ... i am new to these forums (this is my first post) ... i am hoping you guys could help me make an architectural decision on how to implement a data access tier ... here is the situation: - we have a large oracle database (thousands of tables) - we want to isolate applications from database changes - applications can access the data access tier via soap or dcom our team came up with two options diagrammed below ... essentially, option 1 is creating a representation of the database in xml using oracle stored procedures, with a simple com+ component for client access ... option 2 is creating an object hierarchy in com+ that represents the database ... the hierarchy can be accessed directly or be converted to xml. any opinions on which option is better? thanks, john
-
hi there ... i am new to these forums (this is my first post) ... i am hoping you guys could help me make an architectural decision on how to implement a data access tier ... here is the situation: - we have a large oracle database (thousands of tables) - we want to isolate applications from database changes - applications can access the data access tier via soap or dcom our team came up with two options diagrammed below ... essentially, option 1 is creating a representation of the database in xml using oracle stored procedures, with a simple com+ component for client access ... option 2 is creating an object hierarchy in com+ that represents the database ... the hierarchy can be accessed directly or be converted to xml. any opinions on which option is better? thanks, john
ooops ... the image didn't show up ... here is a link ... http://www.lejuan5150.com/lejuan5150/media/dataaccesstier.jpg[^]
-
hi there ... i am new to these forums (this is my first post) ... i am hoping you guys could help me make an architectural decision on how to implement a data access tier ... here is the situation: - we have a large oracle database (thousands of tables) - we want to isolate applications from database changes - applications can access the data access tier via soap or dcom our team came up with two options diagrammed below ... essentially, option 1 is creating a representation of the database in xml using oracle stored procedures, with a simple com+ component for client access ... option 2 is creating an object hierarchy in com+ that represents the database ... the hierarchy can be accessed directly or be converted to xml. any opinions on which option is better? thanks, john
How about using a web service between teh stored procs and the client to take care of reading data and translating to XML...
-
hi there ... i am new to these forums (this is my first post) ... i am hoping you guys could help me make an architectural decision on how to implement a data access tier ... here is the situation: - we have a large oracle database (thousands of tables) - we want to isolate applications from database changes - applications can access the data access tier via soap or dcom our team came up with two options diagrammed below ... essentially, option 1 is creating a representation of the database in xml using oracle stored procedures, with a simple com+ component for client access ... option 2 is creating an object hierarchy in com+ that represents the database ... the hierarchy can be accessed directly or be converted to xml. any opinions on which option is better? thanks, john
Architecturally, here's a good reference: Designing Data Tier Components and Passing Data Through Tiers[^]. It is of course .NET. -- ian
"The greatest danger to humanity is humanity without an open mind."
- Ian Mariano
http://www.ian-space.com/ -
Architecturally, here's a good reference: Designing Data Tier Components and Passing Data Through Tiers[^]. It is of course .NET. -- ian
"The greatest danger to humanity is humanity without an open mind."
- Ian Mariano
http://www.ian-space.com/thanks ... excellent article