Architecture Architecture Non EJB Architecture Architecture Non EJB

  • Slides: 20
Download presentation
Architecture

Architecture

Architecture – Non EJB Architecture

Architecture – Non EJB Architecture

Architecture – Non EJB Architecture 장점!! • Servlet Engine에서 서비스 가능. - Cheaper License,

Architecture – Non EJB Architecture 장점!! • Servlet Engine에서 서비스 가능. - Cheaper License, Easier administration. • Application Server, Servlet Engine에 대해 더 좋은 Portability. • Simpler Implemenation - POJO business Object, No JNDI lookup • 번거로웠던 Deployment descriptors가 필요없음 • Quicker code-deployment cycle. 단지 war파일 하나만 deploy하면 됨

Architecture – Classic EJB Architecture

Architecture – Classic EJB Architecture

Architecture – Local EJB Architecture

Architecture – Local EJB Architecture

Architecture – Lightweight Container Architecture

Architecture – Lightweight Container Architecture

Architecture – Lightweight Container Architecture 장점!! • A simple but powerful • Horizontal scalability는

Architecture – Lightweight Container Architecture 장점!! • A simple but powerful • Horizontal scalability는 높음. • EJB보다 배우기 쉬우며, Configuration 또한 쉽다. • AOP의 지원으로 인해 선언적인 Transaction 관리와 같이 EJB에서 지원하던 기능들의 지원이 가능함.

Architecture – Lightweight Container Architecture 장점!! • Servlet Engine에서 실행이 가능함. • Application Server와

Architecture – Lightweight Container Architecture 장점!! • Servlet Engine에서 실행이 가능함. • Application Server와 Servlet Engine의 Portability 높음. • Io. C(Inversion of control)을 통한 Business Object의 관리가 용이함. • POJO임으로 Testability가 높음. • OOP의 제한이 없음.

Spring Introduction Spring은 Lightweight Application Framework

Spring Introduction Spring은 Lightweight Application Framework

Spring Introduction

Spring Introduction