-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathlecture1.html
667 lines (616 loc) · 20.5 KB
/
lecture1.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
<!DOCTYPE html>
<!--
Middleware and Web Services, CTU course slides
(cc) 2010-2023 Tomas Vitvar, http://vitvar.com
written for Humla, an open source HTML5 presentation environment
-->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta name="course" content="Middleware Architectures 1" />
<meta name="lecture" content="Lecture 1" />
<meta name="keywords" content="enterprise architecture, system integration, roles, software architecture" />
<link type="text/css" rel="stylesheet" href="css/meta.css">
</link>
<link type="text/css" rel="stylesheet" href="css/ctu-fit.css">
</link>
<link type="text/css" rel="stylesheet" href="humla/lib/core/humla.css">
</link>
<script type="text/javascript" src="humla/lib/humla.js"></script>
<title>Information System Architectures</title>
</head>
<body>
<footer>
<p><b>#META_LECTURE#: #TITLE#</b>, <span class="meta_semester" />,
<span class="meta_twitter" />
</p>
<p><b>‒ #SLIDE_NO# ‒</b></p>
</footer>
<div class="slide intro">
<hgroup>
<h1><span class="meta_course" /></h1>
<h2>#META_LECTURE#: #TITLE#</h2>
</hgroup>
<div class="author">
<p class="meta_author" />
<p><span class="meta_email" /> • <span class="meta_twitter" /> •
<span class="meta_web" />
</p>
</div>
<center>
<div class="meta_logo"></div>
</center>
<div class="org">
<p class="meta_org" />
<p><span class="meta_orgfac" /> • <span class="meta_field" />
• <span class="meta_orgweb" /></p>
</div>
<div class="etc">
<div class="text-info">
Modified: #LAST_MODIFIED#<br />
Humla v#HUMLA_VERSION#
</div>
<a href="http://creativecommons.org/licenses/by-sa/3.0/">
<div class="license"></div>
</a>
<div class="oppa"></div>
</div>
</div>
<div class="slide outline"></div>
<section>
<header>Architecture Overview</header>
<div class="slide">
<hgroup>
<h1>Global Architecture</h1>
</hgroup>
<ul class="x-small x-spacing">
<li>A <b>structure</b> and a <b>behavior</b> of system's parts</li>
<li>Complexity – views on the global architecture</li>
<ul>
<li>basic architectural views (also called dimensions): <br />enterprise, data,
functional, process, software, hardware.</li>
</ul>
<li>Development</li>
<ul>
<li>basic <b>methodology</b> and <b>actors</b>:<br />
~ analysis, design, implementation, testing, maintenance<br />
~ end-user, architect, developer, administrator</li>
<li>basic architectural <b>development levels</b>:<br />
~ conceptual, logical, physical.
</li>
</ul>
<li>Global architecture and cloud computing</li>
<ul>
<li>data, functions, processes are application (domain) specific</li>
<li>software architecture defines a <b>software platform</b></li>
<li>hardware architecture defines an <b>infrastructure</b></li>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Views</h1>
</hgroup>
<div class="h-drawing" style="height: 450px; margin-top: 25px"
id="1Ju9pP6mgYoFJuzhhqLP6JibZAXLM-UEgUDd_8rQp8og"></div>
</div>
<div class="slide">
<hgroup>
<h1>Enterprise Architecture</h1>
</hgroup>
<div class="h-drawing" style="height: 450px; margin-top: 25px"
id="1OdjNMgIXF5iKeBELzxGZmDLVQhVbteYoWLjNV29BfxA"></div>
</div>
<div class="slide">
<hgroup>
<h1>Enterprise Architecture Levels</h1>
</hgroup>
<ul class="x-small">
<li>Defines a structure of an enterprise system</li>
<ul>
<li>Abstracts from data, functions, processes, software, hardware</li>
<li>divides enterprise system into functional blocks – <b>applications</b></li>
<ul>
<li>Order Management System (OMS)</li>
<li>Customer Relationship System (CRM)</li>
<li>Billing and Revenue Management (BRM)</li>
</ul>
<li>applications correspond to <b>domains</b> such as sales, finance, procurement, production, etc.
</li>
</ul>
<li>Enterprise architecture levels</li>
<ul>
<li>Operational Support Systems (OSS)</li>
<li>Business Support System (BSS)</li>
<li>Executive Information Systems (EIS)</li>
<li class="space-before">Office Information Systems (OIS)</li>
<li>Integration</li>
<ul>
<li>Business-to-Business (B2B)</li>
<li>Enterprise Application Integration (EAI)</li>
</ul>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Enterprise Architecture Representation</h1>
</hgroup>
<div class="h-drawing" style="height: 470px" alt="Enterprise Architecture as a Pyramid"
id="1OkBUAAuC4sMc_paN2OYYyJLaLdvr4qzttqRPr0uhN9A"></div>
</div>
<div class="slide">
<hgroup>
<h1>Organization Types</h1>
</hgroup>
<ul class="spacing">
<li>Customer</li>
<ul>
<li>user needs: support for business processes</li>
<li>defines business requirements</li>
<li>roles: enterprise architect, developers, admins, users</li>
</ul>
<li>Supplier (enterprise system/application provider)</li>
<ul>
<li>solutions and customization according to requirements</li>
<li>roles: technical and solution architects, developers, admins</li>
</ul>
<li>Vendor (technology provider)</li>
<ul>
<li>product development according to market needs</li>
<li>roles: product managers, developers, reference users</li>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Architect Roles</h1>
</hgroup>
<ul class="spacing small">
<li>Technical Architect</li>
<ul>
<li>Technical architecture design</li>
<li>technology configurations, performance</li>
</ul>
<li>Solution Architect</li>
<ul>
<li>Requirements gathering, analysis</li>
<li>Solution design (data, functions, process)</li>
</ul>
<li>Enterprise Architect</li>
<ul>
<li>High-level enterprise architecture design</li>
<ul>
<li>Applications, processes, data models</li>
</ul>
<li>Should be aligned with industry standards</li>
<ul>
<li>APQC – American Productivity & Quality Center (Process Classification Framework)
</li>
<li>TM Forum – eTOM – Enhanced Telekom Operations Map (Business Process Framework)
</li>
</ul>
</ul>
</ul>
</div>
</section>
<div class="slide outline">
</div>
<section>
<header>Data, Functions and Processes</header>
<div class="slide">
<hgroup>
<h1>Process Classification Framework</h1>
</hgroup>
<div class="h-drawing" id="1ou4lOAvwaFP2MJo1RQbJOTF-DavfYjcUF6MELE6cWws"></div>
</div>
<div class="slide">
<hgroup>
<h1>Order Process Example in Telco</h1>
</hgroup>
<ul class="small">
<li>Order to Cash Process (O2C)</li>
<ul>
<li>end-to-end (E2E) order process</li>
</ul>
<div class="h-drawing" style="height: 100px; width: 700px"
id="1yX-8bZn0P2UwA06KeVJOgk4jaZ0EuMkWaIUa-RdMEno"></div>
<li style="margin-top: 15px;">Involved applications</li>
<ul>
<li>integrated applications</li>
</ul>
<div class="h-drawing" style="height: 200px; width: 700px"
id="1JRgVTqa43jbpGM6PYgGQQFk3mBFHqwWu_SGZHbd0fsY"></div>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Syntax and Domain Semantics</h1>
</hgroup>
<ul class="small">
<li>Syntax</li>
<ul>
<li>Data format, representation, serialization</li>
<li>Various languages at various architectural levels:<br />
XML, JSON, Class/object models in a specific programming language, SQL, DB native structures,
...</li>
<li>They have formal grammars, can be checked for the correct syntax</li>
</ul>
<li>Domain semantics</li>
<ul>
<li>Meaning of terms in a domain they are being used</li>
<li>We understand meaning of terms:</li>
<ul>
<li>Through syntax by using the natural language</li>
<li>Through some <b>agreement</b> among users of the terms</li>
</ul>
<li>Every applications can use different semantics</li>
<ul>
<li>Need to mediate data from one application to another</li>
</ul>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Simplified Order Type Example</h1>
</hgroup>
<div class="h-drawing" style="height: 450px; margin-top: 10px"
id="1o2nyoAPa9s78sXjWuRUNXYoh5uulvGiE7yrHpfsgrTw" format="png"></div>
</div>
<div class="slide outline">
</div>
<section>
<header>Integration</header>
<div class="slide">
<hgroup>
<h1>Integrating Applications</h1>
</hgroup>
<ul class="x-small">
<li>Intra-Enterprise Integration</li>
<ul>
<li>Applications exist in a specific area</li>
<li>Functions and data often overlap across areas</li>
<li>There is a need to integrate applications within enterprise:</li>
<ul>
<li>Applications need to share the same data that are often in different formats.</li>
<li>Applications need to communicate – a result of one process may trigger another one.
</li>
</ul>
</ul>
<li>Inter-Enterprise Integration</li>
<ul>
<li>Also called Business-to-Business Integration (B2B)</li>
<li>Automation support for communication and collaboration among enterprises</li>
<li>For example, B2B automates customers' orders processing, tracking orders, etc.</li>
</ul>
</ul>
</div>
<!-- <div class="slide">
<hgroup>
<h1>Integration Example – O2C</h1>
</hgroup>
<div class="h-drawing" style="height: 350px; margin-top: 60px"
id="1kSE87erCPlL8_3bKu9a7ufeIH71fU1RROcfB6b2yxA4" format="png"></div>
</div> -->
<div class="slide">
<hgroup>
<h1>Integration Example – O2C</h1>
</hgroup>
<img src="/img/order-management-process.png" style="width: 800px"></img>
</div>
<!-- <div class="slide">
<hgroup>
<h1>Example Oracle O2C Technical Flows</h1>
</hgroup>
<div class="h-drawing" style="height: 490px; margin-top: 10px"
id="1zgNezT0FKt69C2Ngqjeuwp1LNv_vKeDeKInxnULN6z8" format="png"></div>
</div> -->
<div class="slide">
<hgroup>
<h1>Integration Issues</h1>
</hgroup>
<ul class="x-small">
<li>Key to integration = <b>interface</b></li>
<ul>
<li>standards – data, functions, processes, technical aspects</li>
<ul>
<li>enterprise standards, committee standards</li>
<li>unified environment from a single vendor</li>
</ul>
<li>mediators</li>
<ul>
<li>where standard do not work out</li>
</ul>
</ul>
<li>Data</li>
<ul>
<li>Message exchange formats, data representation</li>
<ul>
<li>often standardized</li>
</ul>
<li>Semantics of data</li>
<ul>
<li>also standardized, more difficult</li>
</ul>
</ul>
<li>Functions and processes</li>
<ul>
<li>how apps' functionalities should be consumed and orchestrated, protocols, naming issues</li>
<li>A service concept</li>
</ul>
</ul>
</div>
</section>
</section>
<div class="slide outline">
</div>
<section>
<header>Software Architecture</header>
<section>
<header>Types, Separation of Concerns, Interface</header>
<div class="slide">
<hgroup>
<h1>Software Architecture Types</h1>
</hgroup>
<ul class="x-small spacing">
<li>Centralized – Client/Server (C/S)</li>
<ul>
<li>Central server, a bunch of clients</li>
<li>monolithic, <b>two–</b>, <b>three–</b>, <b>multi–tier</b> architectures
</li>
<li>Single point of failure!</li>
<ul>
<li>when a server fails the whole system fails</li>
<li>need for a scalable and <b>highly reliable</b> server-side solutions</li>
</ul>
<li>Enterprise systems (mostly) use centralized solutions</li>
<ul>
<li>But, enhanced with peer-to-peer principles</li>
</ul>
</ul>
<li>Decentralized – Peer-to-Peer (P2P)</li>
<ul>
<li>Reliability</li>
<ul>
<li>when a node fails, other nodes take up its function</li>
</ul>
<li>Scalability</li>
<ul>
<li>multiple nodes can share the load</li>
<li>such as messaging systems in enterprise systems</li>
</ul>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Separation of Concerns</h1>
</hgroup>
<ul class="small">
<li>Separation of Concerns</li>
<ul>
<li>also called Separation of Layers</li>
<li>Concern – any piece of interest (part) in the application</li>
<ul>
<li>concerns should overlap in functionality as little as possible</li>
</ul>
<li>Basic application concerns: data manipulation, data integrity,
application logic, user-interactions</li>
<li>Software architecture separates concerns into layers</li>
<ul>
<li>presentation, application, data</li>
</ul>
</ul>
<li><b>Interface</b></li>
<ul>
<li class="no-bullet">∼ agreement on "how layers should communicate"</li>
<li>most important artifact in Separation of Concerns</li>
<li class="space-before">If an interface is in place, application development and innovation can
happen <b>independently</b>
at each layer</li>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Interface</h1>
</hgroup>
<ul class="small">
<li>Definition</li>
<ul>
<li>Agreement (contract) between two or more layers during communication</li>
</ul>
<li>May be achieved by</li>
<ul>
<li>Through standards (accepted or enforced),</li>
<li>Through a social agreement during design</li>
<li>A dominant position of a technology on the market</li>
</ul>
<li>Interface includes subsets of domain architectures</li>
<ul>
<li>Subsets that are subject to communication between layers</li>
<li class="space-before"><b>data</b> – defines communication language (syntax, semantics),
</li>
<li><b>functions</b> – defines entry points (operations),</li>
<li><b>processes</b> – defines valid states and transitions between them</li>
<li><b>technical details</b> – protocols, ports, IP addresses, etc.</li>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Complex Interfaces</h1>
</hgroup>
<div class="h-drawing" style="height: 300px; margin-top: 10px"
id="1duolAS2N0L7UFhk75xuky5eV9V9x6isGos76S9MGBLE"></div>
<ul class="x-small">
<li>More levels of interfaces</li>
<ol>
<li>DBMS native interface</li>
<li>JDBC – universal connectors for various DBMS systems</li>
<li>JDO – mapping of Java classes to data objects</li>
<li>Domain Object Model (OM) – app-specific (~API, SDK)</li>
<ul>
<li>try to be as universal as possible; cover many technologies</li>
</ul>
</ol>
</ul>
</div>
</section>
<div class="slide outline"></div>
<section>
<header>Client/Server Architectures</header>
<div class="slide">
<hgroup>
<h1>Monolithic Architecture</h1>
</hgroup>
<div class="h-drawing" style="height: 150px" id="1LEdNt_g1CLOcf1sKpyHgQx93iAD9iHDrJRH3GUN00Ps"></div>
<ul class="x-small">
<li>All layers on a single machine</li>
<ul>
<li>usually non-portable apps; specific OS</li>
<li>first types of computer systems, typical for 90-ties</li>
<li>single-user only; standalone apps, minimal integration</li>
<li>technologies: third-gen programming languages, local storage systems</li>
</ul>
<li>Drawbacks</li>
<ul>
<li>hard to maintain (updates, distribution of new versions)</li>
<li>data security issues</li>
<li>performance and scalability issues</li>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Two-tier Client/Server Architecture</h1>
</hgroup>
<div class="h-drawing" style="height: 150px; margin-top: 20px"
id="1Hjo1rvLZShCzhrRfTXwohQfdHmb8-ivomul0HQ98qs0"></div>
<ul class="x-small">
<li>Presentation and app layers separated with data</li>
<ul>
<li>Thick client – desktop application, OS-dependent</li>
<li>Data on a separate server (DBMS)</li>
<li>Multi-user system, all sharing a database</li>
<li>Storage system of high performance, transactions
support</li>
<li>SQL technology; native OS desktop application</li>
</ul>
<li>Drawbacks</li>
<ul>
<li>Thick client hard to maintain (reinstallation with every update)</li>
<li>No app logic sharing (only through copies)</li>
<li>Data-oriented integration (integrity in the app logic!)</li>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Three-tier Client/Server Architecture</h1>
</hgroup>
<div class="h-drawing" style="height: 150px; margin-top: 20px"
id="1zSrBDm5DGLfV5XIKMzKvEMQY31y38KkHuawB9a0bhrA"></div>
<ul class="x-small">
<li>All layers on separated machines</li>
<ul>
<li>Thin client – desktop application or interpreted code</li>
<li>Multi-user system, all sharing app logic and a database</li>
<li>App server of high performance, scalability</li>
</ul>
<li>Drawbacks</li>
<ul>
<li>Spaghetti integration</li>
<li>Limited, single app server scalability</li>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Multi-tier Client/Server Architecture</h1>
</hgroup>
<div class="h-drawing" style="height: 120px; margin-top: 20px; margin-bottom: 20px"
id="1COkmR7I_1RUdIcrQw8_NYTA-qzY_rBrrZm5JdjkIFaY"></div>
<ul class="x-small">
<li>Additional middleware layer</li>
<ul>
<li>provides value-added services for communications</li>
<li>individual servers or a compact solution (e.g., Enterprise Service Bus)</li>
</ul>
<li>Drawbacks</li>
<ul>
<li>Monolithic apps are difficult to scale as a whole</li>
<li>Deployment overhead</li>
<li>A single technological environment for all app functions in the monolith</li>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Client/Server Architecture (microservices)</h1>
</hgroup>
<div class="h-drawing" style="height: 120px; margin-top: 20px; margin-bottom: 20px"
id="1cRwcuZjIcdyV0BKnrT0LqaVreQgSlCbuxmvhTHM2tlY"></div>
<ul class="x-small">
<li>Microservice architecture</li>
<ul>
<li>Middleware, app and DB monoliths are microservice architecture</li>
<li>Improved scalability and technology neutrality of app components</li>
</ul>
<li>Service orchestration layer</li>
<ul>
<li>Kubernetes (K8s)</li>
<li>Large K8s cluster for all, middleware, app, DB</li>
<li>Separate K8s cluster</li>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Client/Server Architecture (<span style="text-decoration: line-through;">microservices</span>)
</h1>
</hgroup>
<div class="h-drawing" style="height: 120px; margin-top: 20px; margin-bottom: 20px"
id="1_a-ZdIt4QylghhrPV1F3kWWcZDcm9OzdyHpK9YlJbv8"></div>
<ul class="x-small">
<li>Not-a-microservice Architecture</li>
<ul>
<li>Monoliths deployed to Kubernetes cluster</li>
<li>Improved Deployments (via container images)</li>
<li>Improved fail-over</li>
<li>Not cheaper (Kubernetes costs come into play)</li>
</ul>
</ul>
</div>
<div class="slide">
<hgroup>
<h1>Types of Middleware</h1>
</hgroup>
<ul class="x-small spacing">
<li>Scalability</li>
<ul>
<li>They help to achieve high performance through better scalability</li>
<li class="space-before">Messaging Servers (message queues, publish/subscribe)</li>
<li>Load Balancers</li>
<li>Proxy servers, reverse proxy</li>
</ul>
<li>Functional</li>
<ul>
<li>They help to achieve more flexible integration</li>
<li class="space-before">Process servers</li>
<li>Repositories, registries of services/components</li>
<li>Mediators – data interoperability, process interoperability, technical interoperability
(SOAP server)</li>
<li>Monitors for analytics of apps usages</li>
</ul>
<li>Security</li>
<ul>
<li>Firewalls, Gateways, ...</li>
</ul>
</ul>
</div>
</section>
</section>
</body>
</html>