53
1 Technology Review Rattakorn Poonsuph D.Sc. School of Applied Statistics, NIDA
| Date post: | 12-May-2015 |
| Category: |
Technology |
| Upload: | aamir97 |
| View: | 625 times |
| Download: | 3 times |
1
Technology Review
Rattakorn Poonsuph D.Sc.School of Applied Statistics, NIDA
2
Technology PerspectivesTechnology Perspectives
3
The Enterprise Platform ArchitecturesThe Enterprise Platform Architectures
Gartner Group ©
4
Architecture TrendsArchitecture Trends
Today, the value is not defined as much by functionality anymore but by connectivity
However, we need a new programming model
Why SOA today? We are reaching a new threshold of connectivity and computing power
Today, the value is not defined as much by functionality anymore but by connectivity
However, we need a new programming model
Why SOA today? We are reaching a new threshold of connectivity and computing power
Mainframe Client Server Web SOA
5
Software Technology Evolution
Modularity Architecture
6
Modularity (Procedural Languages)Process Boundary
Spaghetti Thread Spaghetti Thread
7
Static Binding
C
C
Lib……
obj
objLi
nkin
g
EXE
8
Dynamic Binding
C
C
DynLib…
obj
objLi
nkin
g
EXE
DLL
Runtime
Shared
9
Dynamic Binding VS Messaging
Container
Machine BoundaryMachine Boundary
Machine Boundary
Container
Container
EXE
DLLDLL
DLL
Container
DLL
DLL
DLL
DLL
DLL
DLL
DLL
10
Question
JAVA ? .NET ?
11
Object-oriented Architecture
12
Characteristics of OOA Objects are abstractions of real-world or system entities
and manage themselves. Objects are independent and encapsulate state and
representation information. System functionality is expressed in terms of object
services. Shared data areas are eliminated. Objects
communicate by message passing. Objects may be distributed and may execute
sequentially or in parallel.
13
Advantages of OOD
Easier maintenance. Objects may be understood as stand-alone entities.
Objects are potentially reusable components.
For some systems, there may be an obvious mapping from real world entities to system objects.
14
Object-Oriented
Data
Polymorphism
Inheritance
Encapsulation
Dat
a
Inhe
ritan
ce
Encapsulation
Pol
ymor
phis
m
Inhe
ritan
ce
EncapsulationPolymorphism
Data
Data
Polymorphism
Inhe
ritan
ce
Encapsulation
15
Component-Base Architecture
16
Component Base
Process Boundary
17
Component-based development Component-based software engineering
(CBSE) is an approach to software development that relies on software reuse.
It emerged from the failure of object-oriented development to support effective reuse. Single object classes are too detailed and specific.
Components are more abstract than object classes and can be considered to be stand-alone service providers.
18
CBSE and design principles Apart from the benefits of reuse, CBSE is
based on sound software engineering design principles: Components are independent so do not
interfere with each other; Component implementations are hidden; Communication is through well-defined
interfaces; Component platforms are shared and
reduce development costs.
19
Container 2
Component Scalability
Container 3
•Scalable•Failover•Load Balancing•High Performance•Low Cost
20
Component model services
Platform services
AddressingInterfacedefinition
Componentcommunications
Exceptionmanagement
Horizontal services
Security
Transactionmanagement
Concurrency
Componentmanagement
Persistence
Resourcemanagement
21
Question
What different between Program Library & Component-base
22
Distributed Architecture
23
Remote Procedure Call -DCEClient Server
24
Distributing Component (DCOM)
Client Server
25
Remote Method Invocation (RMI)
Client Server
26
Object Request Broker
Proxy
Proxy
Client Server
27
CORBA / J2EE
Proxy
Proxy
Client Server Container
28
Scalability
Proxy
Client Server Container
Server Container
29
The Architecture Train Hype Cycle
Time
Visibility
DCECORBA
Technology
Trigger
Peak of Inflated
Expectation
Slope ofEnlightenment
Plateau ofProductivity
COM
DCOM
J2EE
COM+/MTS
.NETWeb Services
?
MOM
30
The Disintegration of AD: Replacing Procedures With Services
Web Services
Services
Components
Granularity
Scope
B2B Market,Global Enterprise
Coarse
Objects
HTTP+
MOM
ORB
Typical Access via
Small Enterprise,Complex Application
Homogeneous Application
Program
Tighter LooserCoupling
Procedural
Call
31
Component Model
32
Component modelsComponent models
A component model is a definition of standards for component implementation, documentation and deployment.Examples of component models
EJB model (Enterprise Java Beans)COM+ model (.NET model)Corba Component Model
The component model specifies how interfaces should be defined and the elements that should be included in an interface definition.
A component model is a definition of standards for component implementation, documentation and deployment.Examples of component models
EJB model (Enterprise Java Beans)COM+ model (.NET model)Corba Component Model
The component model specifies how interfaces should be defined and the elements that should be included in an interface definition.
33
Relationship to Other StandardsRelationship to Other Standards
Microsoft COM and ActiveXProvides component interoperability on Windows platform with language-independence
Sun JavaBeans and EJBCross-platform component architecture based on the Java programming language
CORBA 2.0Cross-language, cross-platform distributed object model
Microsoft COM and ActiveXProvides component interoperability on Windows platform with language-independence
Sun JavaBeans and EJBCross-platform component architecture based on the Java programming language
CORBA 2.0Cross-language, cross-platform distributed object model
34
Visual Studio
COM/DCOM ModelCOM/DCOM Model
ActiveX DLLForm
Interface { ListAccount() Deposit() Withdraw() Transfer()}
Implementation ListAccount() { ….. }
COM.DLLWindows
Registry
CLSID
Name of new group:
Desciption
Group type:
Security
Distribution
Group scope:
Domain local
Global
Universal
Look-up
Remote Call
UI.EXE
35
Distributed COM+ / MTSDistributed COM+ / MTSClient Machine
Remote Server
M T
S
Windows
Registry
UI.EXE
Look-up
Remote Call
36
Serviced Components
Microsoft .NET vs. J2EE
Visu
al Stu
dio
.NE
T
Operating System
Common Language Runtime
.NET Framework
ADO.NET, XML
Multiple Languages
Common Language Specification
ASP.NET Windows Forms
To
ols
Operating Systems
JVM
System Classes
JDBC, XML, JDO
Java
EJBs
Java Byte Code Specification
JSP Swing
The Microsoft Platform Generic J2EE Platform
37
Scorecard: Enterprise Architect
Scaling options J2EE OS-based, clustering & failover
Functional richness J2EE Reflected by APIs & services
Security J2EE Experience & architecture
Hardware/OS choice J2EE Range of options
Vendor choice J2EE Sources of supply
Developer tools Microsoft Functional richness, ease of use
XML & Web Services Microsoft Depth & maturity
Manageability Neutral Application dependent
Costs Neutral Application dependent
Advantage
38
Developer tools Microsoft GUI richness, ease of use
Manageability Microsoft Appropriate, easy to use function
Costs Microsoft Deployment, development, skills
Scorecard: Web Project Leader
Scaling options J2EE But Microsoft is good enough
Functional richness Microsoft Rich client function is vital
Security J2EE A manageable risk
Hardware/OS choice NA Wintel is the choice
Vendor choice J2EE Microsoft is the choice
XML & Web Services Microsoft A low priority
Advantage
39
Summary Analysis of Current Platforms
Platform Strengths
J2EE
Platform choice for reliability, scale-up and legacyGreater vendor leverageStronger architecture focus, interfaces & clusteringTools more team-orientedGreater adoption rate / opennessGreater platform depth
.NET
Best GUI developmentTighter platform integration & unified managementBetter, cheaper toolsMulti-language & cross-language supportMore developers (but many are not “enterprise
class”)ASP.NET better than JSPs (for now)
© 2002 Giga Information Group, Inc.
40
Technical Design Pattern
41
Browser
HTML
Applets
Bean
XML/XSL
DMZ Corporate or Service Provider Network
Transactional B2C
J2EE AppServer
JavaBeanEJB
JSPsWeb
Server
JDBCJDBCDataStore
HTTPHTTP
42
Browser
HTML
Applets
Bean
XML/XSL
J2EE AppServer
JavaBeanEJB
JSPsWeb
Server
HTTPHTTPJDBCJDBC
DataStore
Legacy Data/Transfer
COBOL Application
Flat File
IMS
CICS
Messaging Bean
Interface
J2EEConnector
Transactional B2C With LegacyDMZ Corporate or Service Provider Network
43
B2B Integration
J2EE AppServer
EJB
DataStore
DMZ Corporate or Service Provider Network
WebServer
XML / HTTP
Corporate or Service Provider Network
Partner Applications
Custom
XML
Interface
Package
Data Access
DataStore
JDBCWeb
Server
XML
Interface
44
Service-Based Data Access
Message Bus
EJB
DataServic
e
StandardJava
Persistence
C++
DataServic
e
StandardC/C++
Persistence
DataStore
DataStore
45
JSP/Struts/EJBBrowser
HTMLForm
(Tag Libraries)
HTML
Application Server
Web Container
StrutsAction Servlet
XML
HTTP/HTTPS
StrutsAction Class
JSPHTML
JSPXML
BusinessServices
EJB Container
BusinessServices
BusinessObject
(Session Bean)
Data AccessServices(Entity Bean)
Database
(1)
(2)
(3)(4)
(5)(6)
(7)
DataBeans
DataBeans
TRANSACTION
SERVICES
stateless
Container ManagedPersistant (CMP)
FormBeans
Cardinarity1:N Relationship
BusinessFacade
J2EE Design Principle
46
.NET & J2EE IntegrationBrowser
DHTML
Java Application Server
Web Container
BusinessServices
EJB Container
WebServices
BusinessObject
(Session Bean)
Data AccessServices(Entity Bean)
Database
(4)
(5)DataBeans
TRANSACTION
SERVICES
stateless
Container ManagedPersistant (CMP)
.NET Application Server
ADO.NETBusinessContext
WebServices
.Net Web Server
WebForm
(ASP.NET)
Client
Windows Form(.NET)
Combine the benefits of both .NET & J2EE
47
Technology Trends
2006 & Beyond
© 2006, Gartner, Inc. All Rights Reserved.
CHANGES ON THE COMMUNICATIONS HORIZON
“By 2010, 30 percent of US homes will use only cellular or Internet telephony”
Ken Dulaney | Bob Hafner | Wm. L. Hahn | Tole J. Hart
Gartner’s Top Predictions for 2006 and Beyond
PREDICTION
© 2006, Gartner, Inc. All Rights Reserved.
PC’s
“By 2008, 10 percent of companies will require employee-purchased notebooks”.
Leslie Fiering | Brian Gammage | Martin Reynolds
Gartner’s Top Predictions for 2006 and Beyond
PREDICTION
© 2006, Gartner, Inc. All Rights Reserved.
I.T. WORKFORCE
“The job market for IT specialists will shrink 40 percent by 2010”.
Diane Morello
Gartner’s Top Predictions for 2006 and Beyond
PREDICTION
© 2006, Gartner, Inc. All Rights Reserved.
Dep
th o
f S
kill
Sp
ecia
list
Generalist
WORKFORCE PREDICTION
The rise of VERSATILISTSpecialist
• Deep skills• Narrow Scope• Peer recognition• Unknown Outside domain
Generalist• Superficial skills• Broad Scope• Quick response• Others lack confidence
Versatilist• Deep skills• Wide scope of Roles• Broad Experience• Recognized in other domains
Versatilist
Scope of Roles and assignments
© 2006, Gartner, Inc. All Rights Reserved.
© 2006, Gartner, Inc. All Rights Reserved.
