Mastering SOA Service Oriented Architecture
description
Transcript of Mastering SOA Service Oriented Architecture
Mastering SOAService Oriented Architecture
Data Masters
S O A
Special Thanks To…
Miami Innovation Centerhttp://www.miamiinnovationcenter.com
Special Thanks to Our Sponsor!!
John Jadvani954-527-0090
Short bio about me… Andrew Simkovsky 15 years working with database technology
Oracle, MySQL/MariaDB, SQL Server, Postgres
Redis, MongoDB, CouchDB, Cassandra, Neo4j Worked across many industries
Consulting, Retail, Telecommunications, Energy
Data, Marketing, Gaming, Health care
Service Oriented Architecture
What is a Service Oriented Architecture?
Software architecture design pattern
Geared towards “platform”-level design
A collection of services is grouped together to make “platform”
Components are built as independent services, grouped together by functionality
All services are made available to applications or even other services to access
What is a Platform?
A technology stack
A system environment
A set of services made available, either internally or externally, to perform a collection of integrated functions
Traditional Platform
What is a Service?
A self-contained unit of functionality
Grouped together business or application logic
Simple interface to access
Functionality is independent of underlying hardware
Example services underlying a t-shirt vendor’s website: Inventory management Customer management Order management service
SOA Platform
What Does This Give Us?
Simple Integration
Interoperability
Fault Isolation
Scalability
Service Oriented Architecture
Goals
Business transparency Asset reuse and consolidation Loose coupling Modularity and
componentization
Service Oriented Architecture
Principles
Business value over technical strategy Strategic goals over project specific goals Intrinsic interoperability over custom
integration Flexibility over optimization Evolutionary refinement over pursuit of
initial perfection
SOA Concepts
Everything is a service
Each service has a “simple” interface
Each service does one thing and does it well
Direct communication
Indirect communication
Internal Services
External Services
Service Implementations
How Do You Get There?
Identify sets of common logic spread throughout platform
Group common logic together to create services
Implement service by service
Retrofit existing components to the new services as you go
Iterate each service to improve them over time
Questions?