Ekon20 mORMot SOA Delphi Conference
-
Upload
arnaud-bouchez -
Category
Software
-
view
456 -
download
8
Transcript of Ekon20 mORMot SOA Delphi Conference
![Page 1: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/1.jpg)
Arnaud Bouchez | Synopse
From RAD to SOA with mORMot
20161107T101500 - 20161107T113000
![Page 2: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/2.jpg)
From RAD to SOA with mORMot
• Notions
– Design
RAD, OOP, SOLID, DDD
– Architecture
2-Tier, 3-Tier, SOA, MicroServices
![Page 3: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/3.jpg)
From RAD to SOA with mORMot
• Customer-focused Architecture
• Implicit BBM Architecture
• Is it worth it?
• N-Tier
• SOA
• mORMot to the rescue
![Page 4: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/4.jpg)
Customer-focused Architecture
• You can't talk about architecture
in isolation
• Architecture is always driven
by the actual needs
of the application
![Page 5: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/5.jpg)
Customer-focused Architecture
• There is no such "one architecture fits all"
nor "one framework fits all" solution
• Architecture is just a thinking of
how you are building your own software
• Design is architecture applied in code
![Page 6: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/6.jpg)
Customer-focused Architecture
• is not about theory and diagrams
• nor just about best practice
• but an attempt to find
– a way of implementing
– a working solution
– for your customers
![Page 7: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/7.jpg)
Customer-focused Architecture
![Page 8: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/8.jpg)
Customer-focused Architecture
• Premature architecture
may be the root of all evil (as optimization is)
• But no architecture, nor abstraction,
will close many doors, and let maintainability
be a nightmare, even impossible
![Page 9: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/9.jpg)
Implicit BBM Architecture
• No Architecture?
• Will end with an implicit architecture
• Big Ball of Mud (BBM) design pattern
![Page 10: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/10.jpg)
Implicit BBM Architecture
![Page 11: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/11.jpg)
Implicit BBM Architecture
• Make explicit choices
– At Design / code level
– At Architecture / functional level
![Page 12: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/12.jpg)
Design
• RAD
• OOP
• SOLID
• DDD
![Page 13: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/13.jpg)
Design
• RAD
Quick and efficient via components
• OOP
Business separated from UI
• SOLID
Proper classes & interfaces
• DDD
Uncouple your Domain
![Page 14: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/14.jpg)
Design - TDD
• RAD
Manual testing
• OOP
System testing
• SOLID
Injection allow proper unit testing
• DDD
Testing from isolation
![Page 15: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/15.jpg)
Design – Long Term
• RAD
Fast to write, difficult to maintain
• OOP
Dependencies between classes
• SOLID
Agility through Uncoupling and IoC
• DDD
Safe and sound Domain
![Page 16: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/16.jpg)
Architecture
• 2-Tier
• 3-Tier
• N-Tier / SOA
• Micro Services
![Page 17: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/17.jpg)
Architecture
• 2-Tier
DB / UI
• 3-Tier
DB / Logic / UI
• N-Tier / SOA
Mesh of services
• Micro Services
SOLID principles applied to SOA
![Page 18: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/18.jpg)
Architecture
• 2-Tier
Single application
• 3-Tier
Client-Server
• N-Tier / SOA
Integration and vertical scaling
• Micro Services
Agility and horizontal scaling
![Page 19: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/19.jpg)
Is it worth it?
http://martinfowler.com/bliki/DesignStaminaHypothesis.html
![Page 20: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/20.jpg)
Is it worth it?
http://martinfowler.com/bliki/DesignStaminaHypothesis.html
RAD
OOP
SOLID
DDD
![Page 21: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/21.jpg)
Is it worth it?
http://martinfowler.com/bliki/DesignStaminaHypothesis.html
2-Tier
3-Tier
n-Tier/SOA
MicroServices
![Page 22: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/22.jpg)
N-Tier … a piece of cake?
![Page 23: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/23.jpg)
N-Tier … a piece of cake?
Presentation Tier
Application Tier
Business Logic Tier
Data Tier
![Page 24: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/24.jpg)
2-Tier
• VCL/FMX/IW app
• SQL Database
![Page 25: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/25.jpg)
2-Tier
• VCL/FMX/IW app
• SQL Database
Application Tier
Data Tier
![Page 26: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/26.jpg)
2-Tier
• VCL/FMX/IW app
• SQL Database
Logic is usually either in the UI…
Application Tier
Data Tier
![Page 27: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/27.jpg)
2-Tier
• VCL/FMX/IW app
• SQL Database
Logic is usually either in the UI or the DB (stored procedures)
Application Tier
Data Tier
![Page 28: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/28.jpg)
3-Tier
Presentation Tier
Logic Tier
Data Tier
![Page 29: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/29.jpg)
4-Tier
Presentation Tier
Application Tier
Business Logic Tier
Data Tier
![Page 30: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/30.jpg)
N-Tier
• Logical and Physical Views
Most of the time, n-Tier is intended
to be a physical (hardware) view
– e.g. separation between the database server
and the application server
– placing any tier on a separate machine
to facilitate ease of maintenance
or integrate with IT/SaaS requirements
![Page 31: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/31.jpg)
N-Tier
• Logical and Physical Views
In SOA, we deal with logical layout
– Separation of layers through logic interfaces
– Underlying hardware implementation may,
but will usually not, match the logical layout
![Page 32: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/32.jpg)
N-Tier
• Logical and Physical Views
![Page 33: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/33.jpg)
N-Tier
• Physical View
• Web Client
• Web Server
• SQL Database
![Page 34: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/34.jpg)
N-Tier
• Physical View
• Web Client
• Web Server
Embedded SQLite3 Database
![Page 35: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/35.jpg)
N-Tier
• Logical View
• Web app
Client & Server
• SQL Database
Application Tier
Data Tier
![Page 36: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/36.jpg)
N-Tier
• Logical View
• Web app
Client & Server
• SQL Database
with stored procedures
Application Tier
Data Tier
![Page 37: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/37.jpg)
N-Tier
• Logical and Physical Views
Presentation Tier
Application Tier
Business Logic Tier
Data Tier
Client 1 (Delphi) Client 2 (AJAX)
Application Server
DB Server
Presentation Tier
Application Tier
Presentation Tier
Business Logic Tier
Data Tier
![Page 38: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/38.jpg)
SOA
• Service-Oriented Architecture
Definition:
A flexible set of design principles
used during the phases of
systems development and integration
![Page 39: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/39.jpg)
SOA
• Service-Oriented Architecture
Goal:
Package functionality as a suite of
inter-operable services
that can be used within multiple, separate
systems from several business domains
![Page 40: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/40.jpg)
SOA
• Service-Oriented Architecture
– The SOA implementations rely
on a mesh of uncoupled software services
– Software Service:
• A consumer asks a producer
to act in order to produce a result
• Invocation is (often) free from previous invocation
(stateless), to minimize resource consumption
![Page 41: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/41.jpg)
SOA
• Service-Oriented Architecture
– The SOA implementations rely
on a mesh of uncoupled software services
– Those Services comprise
• unassociated, loosely coupled
units of functionality
(each service implements one action)
• that have no direct call to each other
(via protocols, catalogs over a bus)
![Page 42: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/42.jpg)
SOA
• Service-Oriented Architecture
– The SOA implementations rely
on a mesh of uncoupled software services
Consumers Service Bus Publishers
Client A Publisher 1
Publisher 2Client B
Publisher 3Client C
Service 1
Service 2
Service 3
![Page 43: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/43.jpg)
SOA
• Service-Oriented Architecture
– The SOA implementations rely
on a mesh of uncoupled software services
– Service composition
• Logical multi-tier orchestration (transactional)
• A higher level service invokes several services
• Works as a self-contained, stateless service
• Lower-level services can still be stateless
• E.g. application services over business services
![Page 44: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/44.jpg)
SOA
• Service-Oriented Architecture
– The SOA implementations rely
on a mesh of uncoupled software services
– Service composition
Consumers Application Service Bus Application Publishers
Business Service Bus Business Publishers
Client AComposition
PublisherComposition
Service
Publisher 1
Publisher 2
Publisher 3
Service 1
Service 2
Service 3
![Page 45: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/45.jpg)
SOA
• SOA is mainly about decoupling
• It enables implementation independence
in a variety of ways
– Platform
– Location
– Availability
– Versions
![Page 46: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/46.jpg)
SOA
• SOA is mainly about decoupling
Dependency Desired decoupling Decoupling technique
Platform Hardware, Framework or Operating System should not constrain choices of the Services consumers
Standard protocols, mainly Web services (e.g. SOAP or RESTful/JSON)
Location Consumers may not be impacted by service hosting changes
Routing and proxies will maintain Services access
Availability Maintenance tasks shall be transparent
Remote access allows centralized support on Server side
Versions New services shall be introduced without requiring upgrades of clients
Contract marshaling can be implemented on the Server side
![Page 47: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/47.jpg)
SOA
• Micro Services
– SOLID principles meet SOA
![Page 48: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/48.jpg)
SOA
• Micro Services
– SOLID principles meet SOA
• Single responsibility principle
• Open/closed principle
• Liskov substitution principle (design by contract)
• Interface segregation principle
• Dependency inversion principle
![Page 49: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/49.jpg)
SOA
• Micro Services • Single responsibility principle
Object should have only a single axis of change
• Open/closed principle Open for extension, but closed for modification
• Liskov substitution principle (design by contract) Replaceable with subtypes without breaking the contract
• Interface segregation principle Many specific classes/interfaces are better than one
• Dependency inversion principle Depend upon abstractions not concretion, using injection
![Page 50: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/50.jpg)
SOA
• Micro Services
– SOLID principles meet SOA
– Favor stateless calls, and/or event-driven
– Implemented as stand-alone nodes
– Enhance scaling abilities
– Expects services discovery
![Page 51: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/51.jpg)
SOA
• Favor logical Multi-tier architecture
• Put business intelligence on the server side
• Use less bandwidth than a fat client
• From fat client to rich clients (new platforms)
• Leverage resources (DB, cache)
• Easier to upgrade
• Cheaper / Safer for the customer (backup, cloud)
![Page 52: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/52.jpg)
SOA
• Expects a top/down implementation
– Don’t start from the DB, but end-user app
• Forget about bottom/up design
• Define services, not data structures
– Ability to uncouple things
• Identify bounded contexts and needed information
![Page 53: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/53.jpg)
SOA
• Expects a top/down implementation
– Modelize your business in reusable services
• Interfaces and explicit types (DTO) everywhere
• Focus on domain to build tools and maximize ROI
– Cross-cutting features may be delegated
• Emailing, CRM, billing, reporting, UI…
• If this is not where money comes from
![Page 54: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/54.jpg)
SOA
• Expects a top/down implementation
– From n-Tier vertical Architecture
• DB as Root
• Business over DB
– to Clean “onion” Architecture
• Domain as Core
• Persistence as a service
![Page 55: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/55.jpg)
SOA
![Page 56: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/56.jpg)
SOA with mORMot
![Page 57: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/57.jpg)
SOA with mORMot
• Services can be implemented as:
– Method-based resource-focused services
– Interface-based services
• RESTful architecture
– Over several protocols, e.g. HTTP/1.1
– JSON and UTF-8 based
• KISS / CoC design
![Page 58: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/58.jpg)
SOA with mORMot
• Method-based services
type TSQLRestServerTest = class(TSQLRestServerFullMemory) (...) published procedure Sum(Ctxt: TSQLRestServerURIContext); end; procedure TSQLRestServerTest.Sum(Ctxt: TSQLRestServerURIContext); begin with Ctxt do Results([Input['a']+Input['b']]); end;
![Page 59: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/59.jpg)
SOA with mORMot
• Method-based services
type TSQLRestServerTest = class(TSQLRestServerFullMemory) (...) published procedure Sum(Ctxt: TSQLRestServerURIContext); end; procedure TSQLRestServerTest.Sum(Ctxt: TSQLRestServerURIContext); begin Ctxt.Results([Ctxt['a']+Ctxt['b']]); end;
![Page 60: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/60.jpg)
SOA with mORMot
• Method-based services
type TSQLRestServerTest = class(TSQLRestServerFullMemory) (...) published procedure Sum(Ctxt: TSQLRestServerURIContext); end;
by convention, accessible e.g. from http://server/root/sum?a=123&b=456
where root comes from REST server model
![Page 61: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/61.jpg)
SOA with mORMot
• Method-based services
– Give full access to the request
• e.g. 30# replies or static content delivery
– Manual marshalling, e.g. for parameters
• on the server side (error prone)
• on the client side (dedicated code to write)
– Still too close to the metal
![Page 62: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/62.jpg)
SOA with mORMot
• Interface-based services
– Follow Delphi native abstraction of interface
• Strong naming and typing
• Parameters are marshaled via method signature
• SOLID abstractions
• Reference-counted memory management
• Optional dual-way callbacks (WebSockets)
![Page 63: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/63.jpg)
SOA with mORMot
• Interface-based services
– Client-side wrapper is generated at runtime
• Features RESTful UTF-8 JSON, so AJAX ready
– Tied to mORMot’s REST and security model
• From stand-alone app to complex MicroServices
• Easily integrated with stubbing/mocking features
![Page 64: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/64.jpg)
SOA with mORMot
• Interface-based services steps:
– Define a contract
– Implement the contract on server side
– Host and publish the service
– Access the service from client side
![Page 65: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/65.jpg)
SOA with mORMot
• Define a contract type
ICalculator = interface(IInvokable)
['{9A60C8ED-CEB2-4E09-87D4-4A16F496E5FE}']
/// add two signed 32 bit integers
function Add(n1,n2: integer): integer;
end;
• ICalculator interface defines the contract
• Add() method defines the operation
• Handle any kind of parameters
– Including classes, variants, dynamic arrays or records
![Page 66: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/66.jpg)
SOA with mORMot
• Implement the contract on server side type TServiceCalculator = class(TInterfacedObject, ICalculator) public function Add(n1,n2: integer): integer; end; function TServiceCalculator.Add(n1, n2: integer): integer; begin result := n1+n2; end;
… and that’s all !
![Page 67: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/67.jpg)
SOA with mORMot
Host and publish the service
Server.ServiceRegister( TServiceCalculator,[TypeInfo(ICalculator)],sicShared);
– will register the TServiceCalculator class
– to implement the ICalculator service
– with a single shared instance life time
– to any TSQLRestServer instance
![Page 68: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/68.jpg)
SOA with mORMot
Host and publish the service
Server.ServiceRegister( TServiceCalculator,[ICalculator],sicShared);
– will register the TServiceCalculator class
– to implement the ICalculator service
– with a single shared instance life time
– to any TSQLRestServer instance
![Page 69: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/69.jpg)
SOA with mORMot
Access the service from client side
Client.ServiceDefine([ICalculator],sicShared);
• Register to any kind of TSQLRestClient via named pipes, messages, HTTP, WebSockets
• Execution will take place on the server side
• ICalculator type defines the contract
![Page 70: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/70.jpg)
SOA with mORMot
Access the service from client side var I: ICalculator; begin if Client.Services['Calculator'].Get(I) then result := I.Add(10,20); end;
• A “fake” class implements ICalculator
• Data is transmitted by representation as JSON / REST
• Any server-side exception will be transmitted back
![Page 71: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/71.jpg)
SOA with mORMot
Access the service from client side var I: ICalculator; begin if Client.Services.Resolve(ICalculator,I) then result := I.Add(10,20); end;
• Implements IoC / DI patterns
• You can inject other local (mocked) services
![Page 72: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/72.jpg)
SOA with mORMot
Access the service from server side var I: ICalculator; begin if Server.Services.Resolve(ICalculator,I) then result := I.Add(10,20); end;
• Direct in-process execution
• Service composition with no performance penalty
• Business logic uncoupled from actual execution
![Page 73: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/73.jpg)
SOA with mORMot
• Interface-based services instance lifetime Lifetime Use case
sicSingle An asynchronous process (may be resource consuming)
sicShared Either a very simple process, or requiring some global data
sicClientDriven The best candidate to implement a Business Logic workflow and light transactional process (Unit-Of-Work pattern)
sicPerSession To maintain some data specific to the client application
sicPerUser Access to some data specific to one user
sicPerGroup Access to some data shared by a user category (e.g. administrators, or guests)
sicPerThread Thread-oriented process (e.g. for proper library initialization)
![Page 74: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/74.jpg)
SOA with mORMot
• Interface-based services routing
– Classes available by default:
– you can define your own class
TSQLRestRoutingREST TSQLRestRoutingJSON_RPC
Description RESTful mode JSON-RPC mode
Default Yes No
URI scheme
/Model/Interface.Method[/ClientDrivenID]
or /Model/Interface/Method[/ClientDrivenID]
+ optional URI-encoded params
/Model/Interface
Body content JSON array (or object) of parameters
or void if parameters were encoded at URI
{"method":"MethodName",
"params":[...]
[,"id":ClientDrivenID]}
Security RESTful authentication for each method
or for the whole service (interface)
RESTful authentication for the
whole service (interface)
![Page 75: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/75.jpg)
SOA with mORMot
• Interface-based services execution modes
– Per-method threading behavior TServiceMethodOptions Description
none (default) All methods are re-entrant and shall be coded to be thread-safe (best scaling performance, but may be error prone)
optExecLockedPerInterface Each interface will be protected/locked by its own mutex
optExecInMainThread optFreeInMainThread
Methods will be executed in the process main thread Interface will be released in the process main thread
optExecInPerInterfaceThread optFreeInPerInterfaceThread
Each interface will execute its methods in its own thread Each interface will be freed in its own thread
![Page 76: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/76.jpg)
SOA with mORMot
Interface-based services Security
– Based on framework’s RESTful authentication
– Expects a user to be authenticated
and an in-memory session to be initiated
![Page 77: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/77.jpg)
SOA with mORMot
Interface-based services Security
– Based on framework’s RESTful authentication
– Restrain execution via fluent interface, e.g.
Server.ServiceDefine( TServiceCalculator,ICalculator,sicShared). DenyAll. AllowAllByName(['Supervisor']);
![Page 78: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/78.jpg)
SOA with mORMot
• Interface-based services callbacks
– Specify the callback as an interface parameter
• Native way of coding
– Real-time push notifications over WebSockets
• Upgraded from a standard HTTP connection
– Peer To Peer communication
• No need of a centralized message bus / server
![Page 79: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/79.jpg)
SOA with mORMot
• Interface-based services callbacks
– Specify the callback as an interface parameter
ILongWorkCallback = interface(IInvokable)
['{425BF199-19C7-4B2B-B1A4-A5BE7A9A4748}']
procedure WorkFinished(const workName: string;
timeTaken: integer);
procedure WorkFailed(const workName, error: string);
end;
![Page 80: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/80.jpg)
SOA with mORMot
• Interface-based services callbacks
– Specify the callback as an interface parameter
ILongWorkCallback = interface(IInvokable)
…
ILongWorkService = interface(IInvokable)
['{09FDFCEF-86E5-4077-80D8-661801A9224A}']
procedure StartWork(const workName: string;
const onFinish: ILongWorkCallback);
function TotalWorkCount: Integer;
end;
![Page 81: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/81.jpg)
SOA with mORMot
• Interface-based services callbacks
– Real-time push notifications over WebSockets
![Page 82: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/82.jpg)
SOA with mORMot
• Interface-based services callbacks
– Real-time push notifications over WebSockets
• Once upgraded, communicates using frames
over a bi-directional socket connection
using application-level protocols
• Security, frames gathering, REST emulation,
binary encryption and compression
![Page 83: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/83.jpg)
SOA with mORMot
• Cross-platform Interface-based services
– Generated client code
• Using Mustache templates
• Delphi: Windows, MacOS, Android, iOS
• FPC: Windows, MacOS, Android, iOS, Linux, …
• (Cross)Kylix: Linux
• SmartMobileStudio, EWB: Ajax / HTML5
– Featuring almost all framework abilities
• JSON marshalling, security, instance lifetime
![Page 84: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/84.jpg)
SOA with mORMot
• REST design at class level
Following SOLID principles
TSQLRestServer
TSQLRest
TSQLRestClientURI
TSQLRestClient
![Page 85: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/85.jpg)
SOA with mORMot
![Page 86: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/86.jpg)
SOA with mORMot
![Page 87: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/87.jpg)
SOA with mORMot
![Page 88: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/88.jpg)
SOA with mORMot
• Interface-based services sample
– Sample 14
• ICalculator Client/Server
– Sample 27
• Cross-platform REST clients
![Page 89: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/89.jpg)
SOA with mORMot
• Interface-based services callbacks
– Sample 31
• Long-Work Push Notification
also known as “Sagas”
• Publish/Subscribe Pattern
also known as “Observer”
![Page 90: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/90.jpg)
SOA with mORMot
• Resources
– http://synopse.info
– http://synopse.info/forum
– http://blog.synopse.info
– http://github.com/synopse/mORMot
Includes exhaustive documentation,
samples and regression tests.
![Page 91: Ekon20 mORMot SOA Delphi Conference](https://reader033.fdocuments.in/reader033/viewer/2022042600/58aa7eb31a28ab2e448b4605/html5/thumbnails/91.jpg)
Q & A
©2016 Synopse / A.Bouchez