物件關聯對映技術(O/R Mapping)在服務導向架構(SOA)應用之探討

隨著網際網路的發達，資訊科技技術不停地進步，讓企業的資訊部門經常面臨到軟硬體升級或者是資訊整合所發生的問題，包括了系統平台之間的整合以及底下程式與程式之間的整合。同時對系統架構的需求也有了重大改變，漸漸發展為服務導向架構(Service Oriented Architecture，SOA)。當企業的需求改變時，企業必須做出對應的系統更新，若無法順利整合或者更新系統，可能造成企業的資訊系統不符使用需求而損失了資訊系統對企業所應帶來的益處。隨著服務導向架構的興起，為達到資料庫層與業務邏輯層之間的切割，使程式撰寫人員能夠專注於業務邏輯的實現，同時也降低資料庫相關程式碼的數量與維護便利性，在這中間的物件關聯對映技術也隨之成長。由於服務導向架構所帶來的優勢，本研究便對於分散式系統架構中的業務邏輯層與資料庫層之間的連接來做探討，本研究針對分散式系統架構中的持久層中的物件關聯對映技術以SOA雲端服務中心的開放平台工具與Hibernate兩相比較來做探討，了解目前的物件關聯對映技術是否能達到服務導向架構的需求以期使企業能夠因應需求的改變順利的作系統與應用程式的變更，以便維持資訊系統對企業所帶來的效益。研究發現理想上的持久層應達到以下五點需求：完整封裝的持久性機制、多物件的操作、資料交易、可擴展性與支援各種資料庫。SOA雲端服務中心的開放平台工具，在服務導向架構下的應用對於On-demand的需求雖然可以達到，但在功能性上並不完整，尤其是上述五點需求中的多物件操作與支援各種資料庫，而此問題在Hibernate的架構下得以解決，未來可再針對持久層的資料交易做更深入的研究。

關鍵字

物件關聯對映技術；服務導向架構； Hibernate ；持久層

並列摘要

With the development of internet and technology changing, IT departments had often faced to hardware and software's upgrade and integration between the platforms and the Programs. At the same time demand on the system architecture has changed significantly, and gradually developed into a service-oriented architecture (SOA). When enterprise's requirement change, enterprise must do corresponding system updates, if the system's integration or update is not successful, it may cause the information system could not conform to enterprise's requirements or lose the business benefits that information systems should brought at first. With the rise of service-oriented architecture, the object relational mapping also grow for the cutting of database layer and business logic, so that programming can focus on implementing of business logic, while also reducing the coding of database layer and easier to maintenance. As service-oriented architecture brings the advantages, in this research will do an exploration of object relational mapping for persistence tier applying on service-oriented architecture, and compare SOA could service center's open source tool with Hibernate to find out the object relational mapping could or couldn't arrived the requirement of service-oriented architecture, except information system could correspond to enterprise's requirement to keep the business benefits that information system should brought. The results find that persistence layer should meet the following five requirements: the full encapsulation of the persistence mechanism, multi-object actions, data transaction, scalability and support for various databases. SOA cloud service center open source tools, could do the On-demand for service-oriented architecture, but in functionality is not complete, especially on requirement of multi-object actions and support for various database, but these problems can be solved under the Hibernate framework, in the future can do more research on the data transaction for object relational mapping.

並列關鍵字

Service-Oriented Architecture (SOA) ； Persistence tier ； Hibernate ； Object Relational Mapping

參考文獻

3. 易志中，(2007)，“SOA 與GIS的結合”，地理資訊系統季刊，崧旭資訊股份有限公司。

1. Ali Arsanjani, “Service-oriented modeling and architecture – How to identify,specify,and realize services for your SOA, ” IBM Developer Works

5. Chuanlong Xia,Guangcan Yu,Meng Tang.," Efficient Implement of ORM (Object/Relational Mapping) Use in J2EE Framework: Hibernate," Computational Intelligence and Software Engineering, 2009(1):1-3

8. Howerton, J.T.; , "Service-Oriented Architecture and Web 2.0," IT Professional , vol.9, no.3, pp.62-64, May-June 2007

9. IBM corp, Service Oriented Architecture — SOA, Retrieved July, 2010 from http://www01.IBM.com/software/solutions/SOA/

國際替代計量

物件關聯對映技術(O/R Mapping)在服務導向架構(SOA)應用之探討

未授權

主題瀏覽