DEV5: Application Architecture Made Simple

1
DEV-5 Application Architecture Made Simple
Christian Stiller
Technical Account Manager
2
Software Architecture

• ProDatasets
• OO

The software architecture of a system consists
of software components, their external
properties, and their relationships with one
another.
Presentation
Enterprise Services
Business Components
Data Sources
Wikipedia The free encyclopedia
3
Software Architecture
4
The Use Cases

• Display customer information
• Change customer information
• Check premium access

5
The Use Cases
6
Agenda
Application Architecture

• The Break Up
• Matchmaking
• Multiple Personality Disorder

7
Before the Break Up

• UI and BL mixed
• Hard to maintain
• BL has UI knowledge
• Code is duplicated in multiple screens
• Not all instances of the code are changed
  consistently
• BL is tied to specific screen
• Adding new UI requires BL re-write (most often
  copy-paste and change)

8
Break Up goals

• Improve application maintainability
• UI and BL can be changed independent of each
  other
• Re-Use of BL
• No code duplication if BL is used in multiple
  screens
• Exposing services to other interfaces
• Re-use of BL with other applications or UIs

9
Evolution of Architecture Layers
Separating UI from BL
DATA
Result
QUERY
Request
10
Break Up
11
Break Up
12
Break Up
13
Break Up
14
Break Up
15
Break Up
16
Break Up
17
Break Up
18
Break Up
19
Evolution of Architecture Layers
Separating UI from BL
DATA
Result
QUERY
Request
20
Break Up Goals

• Improve application maintainability
• UI and BL can be changed independent of each
  other
• Re-Use of BL
• No code duplication if BL is used in multiple
  screens
• Exposing services to other interfaces
• Re-use of BL with other applications or UIs

21
Agenda
Application Architecture

• The Break Up
• Matchmaking
• Multiple Personality Disorder

22
Before the Matchmaking

• Service location
• Hard coded
• Spread throughout application
• Service signature
• Service format is used as-is everywhere
• Used in several places
• Common Infrastructure
• Mixed with BL and UI
• Hard to make changes to signature

23
Before the Matchmaking
24
Evolution of Architecture Layers
Service Adapter Service Interface
Result
Request
Service Requester
Service Provider
25
Service Adapter Goals / Purpose

• Isolate Service Requester
• Make separation transparent
• Provide Service Provider location independence
• Isolate common infrastructure
• Isolate requester from Service Provider format

26
Service Adapter
27
Service Adapter
28
Service Adapter
29
Service Adapter
30
Service Adapter Goals / Purpose

• Isolate Service Requester
• Make separation transparent
• Provide Service Provider location independence
• Isolate common infrastructure
• Isolate requester from Service Provider format

31
Evolution of Architecture Layers
Service Adapter Service Interface
Result
Request
Service Requester
Service Provider
32
Service Interface Goals / Purpose

• Isolate Service Provider
• Isolate Service Provider from Common Application
  Services
• Security, Context etc.
• Determine Service Provider Component to serve
  request
• Isolate Service Provider from technology
  differences or requirements
• Data formatting
• Data transformation

33
Service Interface
34
Service Interface
35
Service Interface
36
Service Interface Goals / Purpose

• Isolate Service Provider
• Isolate Service Provider from Common Application
  Services
• Security, Context etc.
• Determine Service Provider Component to serve
  request
• Isolate Service Provider from technology
  differences or requirements
• Data formatting
• Data transformation

37
Evolution of Architecture Layers
Service Adapter Service Interface
Result
Request
Service Requester
Service Provider
38
Location and common infrastructure
39
Location and common infrastructure
40
Location and common infrastructure
41
Location and common infrastructure
42
Location and common infrastructure
43
Location and common infrastructure
44
Evolution of Architecture Layers
Service Adapter Service Interface
Result
Request
Service Requester
Service Provider
45
Agenda
Application Architecture

• The Break Up
• Matchmaking
• Multiple Personality Disorder

46
Business Logic The Current Situation

• Logic uses physical data storage
• Complex joins
• Confusing fields names
• Changes to business rules require knowledge of
  physical data storage
• Changes to physical data storage require changes
  to implementation of business rules
• Database schema changes
• Use of different data source

47
Business Logic The Goals
Responsibility split

• A Business View of Data (Logical Model)
• Independent of physical storage (Physical Model)
  meaningful names
• Simplified view (more natural fit)
• Improved Application Maintenance
• Changing Business Logic does not impact Data
  Source or User Interface
• Changing User Interface or Data Source does not
  impact Business Logic

48
A Business View of Data

• Makes Business Logic independent of Physical
  Model
• Makes Business Logic more natural

49
Business Components and Data Access
Data Transformation Flow
50
Evolution of Architecture Layers
Business Component and Data Access
Result
Request
Service Provider
51
Data Access
52
Data Access
53
Data Access
54
Data Access
55
Data Access
56
Data Access
57
Data Access
58
Data Access
59
Data Access
60
Data Access
61
Evolution of Architecture Layers
Business Component and Data Access
Result
Request
Service Provider
62
Evolution of Architecture Layers
OpenEdge Reference Architecture
63
Next steps

• Application Architecture Made Simple

64
Next steps

• PSDN OpenEdge Principles
• Application Architecture Made Simple
• OpenEdge Reference Architecture
• OpenEdge 10
• OpenEdge Architect
• ProDataSet
• OO

65
Relevant Exchange Sessions

• DEV-11 Architecting Your Application in OpenEdge
  10
• DEV-17 Getting to SaaS
• DEV-18 Estimating Your TransformationThe Reality

66
Relevant Exchange Sessions

• DEV-1 What's New in OpenEdge 10.1C?
• DEV-2 Making OpenEdge Architect Work for You
• DEV-6 Introduction to the OpenEdge Advanced GUI
• DEV-12 What's New in the Object-Oriented ABL?
• DEV-24 What's New with ProDataSets in 10.1C?

67
?
Questions
68
Thank You
69
(No Transcript)