SlideShare ist ein Scribd-Unternehmen logo
1 von 23
The SPOSAD Architectural Style
for Multi-tenant Software Applications




                            Heiko Koziolek
                          Industrial Software Systems
                           ABB Corporate Research




                                                        1
Source: salesforce.com

                  2
28.04.2008:
     „SAPs new SME software
‚Business By Design‘ jammed“


                 25.10.2008:
         „SAP will part with
        outsourcing partner“


                  19.02.2009:
      „SAP denies sales stop
    for ‚Business by Design‘“
                     Source: heise.de
                                        3
Single-Tenancy                 Multi-Tenancy

Tenant1   Tenant2   Tenant3   Tenant1   Tenant2    Tenant3

  App      App       App                  App

Database Database Database              Database

  OS        OS        OS                  OS

Hardware Hardware Hardware              Hardware




                                                             4
Challenges
   Lack of        Ad-hoc     Technology
Documentation    Solutions      Focus




                                          5
Architectural Styles

An architectural /style is a coordinated set of
         Client Server  Blackboard
architectural constraints that restricts
         Pipe-and-Filter  C2
the roles / features of architectural elements
and the  Peer-to-Peer
        allowed relationshipsREST (WWW)
                               among those elements
within any architecture that conforms to that style.
         Mobile Code          SPIAR (AJAX) [Fielding2000]



   Idea: Multi-tenancy Style
                                                              6
Resource Sharing                     Elasticity
                   Architectural
                    Architectural
                    Properties
                     Properties




     Maintainability            Customizability
                                                  7
SPOSAD Style for Multi-Tenancy

  Shared

  Polymorphic

  Scalable

  Application   and
  Data
SPOSAD Style for Multi-Tenancy

Client Tier                              Application Tier                            Data Tier



                                                          Application                Multi-tenant
  Browser             Cache (optional)


                                          Load Balancer
                                                           Threads                    Database
               REST
                                                                          Asynch,
                                                          Customization    Synch         Data
               REST                                                       Transfer
                                                           Meta-Data                  Meta-Data
 Rich Client
                                                            Manager




                                                                                                    9
SPOSAD Style for Multi-Tenancy

Client Tier                               Application Tier                              Data Tier

                                         Elasticity                     Maintainability

                                                            Application                 Multi-tenant
  Browser             Cache (optional)


                                            Load Balancer
                                                             Threads                     Database
               REST
                                                                             Asynch,
                                                            Customization     Synch         Data
               REST                                                          Transfer
                                                             Meta-Data                    Meta-Data
 Rich Client
                                                              Manager




                        Customizability                               Resource Sharing                 10
Multi-tenant Database

Private Table Layout   Extension Table Layout   Universal Table Layout




                                                                   11
Multi-tenant Database

Private Table Layout      Extension Table Layout    Universal Table Layout



           Account27
           AID     Name       Robot Speed     Account33
           1       ABC        X     20        AID     Name
           2       DEF        Y     50        1       GHI


                  Account46
                  AID     Name     Lines
                  1       JKM      12


                                                                       12
Multi-tenant Database

Private Table Layout       Extension Table Layout           Universal Table Layout

                                      Industrial-Account
                                      Tenant ID     Row         Robot   Speed
 Account-Extension
                                      27            0           X       20
 Tenant ID   Row     AID   Name
                                      27            1           Y       50
 27          0       1     ABC
 27          1       2     DEF          Telecommunication-Account
 33          0       1     GHI          Tenant ID       Row     Lines
 46          0       1     JKM          46              0       12




                                                                                13
Multi-tenant Database

Private Table Layout      Extension Table Layout     Universal Table Layout



     Universal
     Tenant ID    Table   Col1   Col2    Col3   Col4    Col5   Col6
     27           0       1      ABC     X      20      -      -
     27           0       2      DEF     Y      50      -      -
     33           1       1      GHI     -      -       -      -
     46           2       1      JKM     12     -       -      -




                                                                        14
Shared
Single Code Base
                   Architectural
                    Architectural      Data Resources
                    Constraints
                     Properties


                               STATE



Customization Component      Stateless Application Tier
                                                      15
Architectural Trade-offs

                              Resource Sharing
                          vs. Security / Availability




    Complexity
vs. Time to market

                             Customizability
                            vs. Maintainability
                                                        16
Evaluation?




              17
Client Tier                               Application Tier                            Data Tier
                      Virtual Application                                        Customized
                         Components                                              Oracle RAC

                                                           Application                Multi-tenant
  Browser              Cache (optional)


                                           Load Balancer
                                                            Threads                    Database
               REST
                                                                           Asynch,
                                                           Customization    Synch         Data
               REST                                                        Transfer
                                                            Meta-Data                  Meta-Data
 Rich Client
                                                             Manager



                                                                            Universal Table
                                                Runtime Engine
                                                                                Layout


                                                                                                     18
Client Tier                              Application Tier                              Data Tier
                          Web / Worker                                            Blobs, Tables,
                             Roles                                                 SQL Azure

                                                            Application                Multi-tenant
  Browser             Cache (optional)


                                          Load Balancer
                                                             Threads                    Database
               REST
                                                                            Asynch,
                                                            Customization    Synch         Data
               REST                                                         Transfer
                                                             Meta-Data                  Meta-Data
 Rich Client
                                                              Manager



                                                      Worker Role


                                                                                                      19
Client Tier                              Application Tier                                  Data Tier
                                JSP / Servlet,
                                                                                    Google Big Table
                                   Python

                                                                Application                Multi-tenant
  Browser             Cache (optional)


                                          Load Balancer
                                                                 Threads                    Database
               REST
                                                                                Asynch,
                                                                Customization    Synch         Data
               REST                                                             Transfer
                                                                 Meta-Data                  Meta-Data
 Rich Client
                                                                  Manager



                                                          App Engine
                                                           Services


                                                                                                          20
…and SAP?   ?

                                         27.01.2010

                             „With feature pack 2.5,
                       appearing in summer this year,
                                   Business ByDesign
                gets a multi-tenant architecture“

                                      Peter Lorenz
                           Chief SME Solutions SAP
                                            Source: isreport.de




                                                        21
Conclusions




Multi-tenancy as an Architectural Style

                                          22
23

Weitere ähnliche Inhalte

Was ist angesagt?

E force dnw rewrite-draft-v7-080607
E force dnw rewrite-draft-v7-080607E force dnw rewrite-draft-v7-080607
E force dnw rewrite-draft-v7-080607
Debjani Roy
 
Orders of-magnitude-scale-out-your-sql-server-data-slideshare
Orders of-magnitude-scale-out-your-sql-server-data-slideshareOrders of-magnitude-scale-out-your-sql-server-data-slideshare
Orders of-magnitude-scale-out-your-sql-server-data-slideshare
Mark Broadbent
 
Microsoft SQL Server - SQL Server 2008 R2 Editions Datasheet
Microsoft SQL Server - SQL Server 2008 R2 Editions DatasheetMicrosoft SQL Server - SQL Server 2008 R2 Editions Datasheet
Microsoft SQL Server - SQL Server 2008 R2 Editions Datasheet
Microsoft Private Cloud
 
Data in your SOA: From SQL to NoSQL and Beyond
Data in your SOA: From SQL to NoSQL and BeyondData in your SOA: From SQL to NoSQL and Beyond
Data in your SOA: From SQL to NoSQL and Beyond
WSO2
 
Data Virtualization Primer -
Data Virtualization Primer -Data Virtualization Primer -
Data Virtualization Primer -
Kenneth Peeples
 
Res tful web services oracle
Res tful web services oracleRes tful web services oracle
Res tful web services oracle
knoxxs
 
Imaginea Performance Engineering
Imaginea Performance EngineeringImaginea Performance Engineering
Imaginea Performance Engineering
RajaneeshChandra
 
Building a Hybrid Platform as a Service
Building a Hybrid Platform as a ServiceBuilding a Hybrid Platform as a Service
Building a Hybrid Platform as a Service
WSO2
 

Was ist angesagt? (20)

Oracle Data Warehouse
Oracle Data WarehouseOracle Data Warehouse
Oracle Data Warehouse
 
Couchbase Server and IBM BigInsights: One + One = Three
Couchbase Server and IBM BigInsights: One + One = ThreeCouchbase Server and IBM BigInsights: One + One = Three
Couchbase Server and IBM BigInsights: One + One = Three
 
Cloudian at cassandra conference in tokyo
Cloudian at cassandra conference in tokyoCloudian at cassandra conference in tokyo
Cloudian at cassandra conference in tokyo
 
CMS Solution Benefits
CMS Solution BenefitsCMS Solution Benefits
CMS Solution Benefits
 
E force dnw rewrite-draft-v7-080607
E force dnw rewrite-draft-v7-080607E force dnw rewrite-draft-v7-080607
E force dnw rewrite-draft-v7-080607
 
Orders of-magnitude-scale-out-your-sql-server-data-slideshare
Orders of-magnitude-scale-out-your-sql-server-data-slideshareOrders of-magnitude-scale-out-your-sql-server-data-slideshare
Orders of-magnitude-scale-out-your-sql-server-data-slideshare
 
Microsoft SQL Azure - Cloud Based Database Datasheet
Microsoft SQL Azure - Cloud Based Database DatasheetMicrosoft SQL Azure - Cloud Based Database Datasheet
Microsoft SQL Azure - Cloud Based Database Datasheet
 
Microsoft SQL Server - SQL Server 2008 R2 Editions Datasheet
Microsoft SQL Server - SQL Server 2008 R2 Editions DatasheetMicrosoft SQL Server - SQL Server 2008 R2 Editions Datasheet
Microsoft SQL Server - SQL Server 2008 R2 Editions Datasheet
 
Oracle: Fundamental Of DW
Oracle: Fundamental Of DWOracle: Fundamental Of DW
Oracle: Fundamental Of DW
 
Data in your SOA: From SQL to NoSQL and Beyond
Data in your SOA: From SQL to NoSQL and BeyondData in your SOA: From SQL to NoSQL and Beyond
Data in your SOA: From SQL to NoSQL and Beyond
 
Ssrs introduction session 1
Ssrs introduction session 1Ssrs introduction session 1
Ssrs introduction session 1
 
Task Factory - Pragmatic Works
Task Factory - Pragmatic WorksTask Factory - Pragmatic Works
Task Factory - Pragmatic Works
 
Data Virtualization Primer -
Data Virtualization Primer -Data Virtualization Primer -
Data Virtualization Primer -
 
Res tful web services oracle
Res tful web services oracleRes tful web services oracle
Res tful web services oracle
 
Introducing Open XDX Technology for Open Data API development
Introducing Open XDX Technology for Open Data API developmentIntroducing Open XDX Technology for Open Data API development
Introducing Open XDX Technology for Open Data API development
 
Introducing SQL Server Data Services
Introducing SQL Server Data ServicesIntroducing SQL Server Data Services
Introducing SQL Server Data Services
 
DB Luminous... Know Your Data
DB Luminous... Know Your DataDB Luminous... Know Your Data
DB Luminous... Know Your Data
 
Imaginea Performance Engineering
Imaginea Performance EngineeringImaginea Performance Engineering
Imaginea Performance Engineering
 
IMGS Local Gov User Group Presentation
IMGS Local Gov User Group PresentationIMGS Local Gov User Group Presentation
IMGS Local Gov User Group Presentation
 
Building a Hybrid Platform as a Service
Building a Hybrid Platform as a ServiceBuilding a Hybrid Platform as a Service
Building a Hybrid Platform as a Service
 

Andere mochten auch

ICSE 2011: Q-ImPrESS - An Industrial Case Study on Quality Impact Prediction
ICSE 2011: Q-ImPrESS - An Industrial Case Study on Quality Impact Prediction ICSE 2011: Q-ImPrESS - An Industrial Case Study on Quality Impact Prediction
ICSE 2011: Q-ImPrESS - An Industrial Case Study on Quality Impact Prediction
Heiko Koziolek
 
A Model Transformation from the Palladio Component Model to Layered Queueing ...
A Model Transformation from the Palladio Component Model to Layered Queueing ...A Model Transformation from the Palladio Component Model to Layered Queueing ...
A Model Transformation from the Palladio Component Model to Layered Queueing ...
Heiko Koziolek
 
Rapid Performance Modeling by transforming Use Case Maps to Palladio Componen...
Rapid Performance Modeling by transforming Use Case Maps to Palladio Componen...Rapid Performance Modeling by transforming Use Case Maps to Palladio Componen...
Rapid Performance Modeling by transforming Use Case Maps to Palladio Componen...
Heiko Koziolek
 
Sustainability Evaluation of Software Architectures: A Systematic Review
Sustainability Evaluation of Software Architectures: A Systematic ReviewSustainability Evaluation of Software Architectures: A Systematic Review
Sustainability Evaluation of Software Architectures: A Systematic Review
Heiko Koziolek
 
Evolving Industrial Software Architectures into a Software Product Line: A Ca...
Evolving Industrial Software Architectures into a Software Product Line: A Ca...Evolving Industrial Software Architectures into a Software Product Line: A Ca...
Evolving Industrial Software Architectures into a Software Product Line: A Ca...
Heiko Koziolek
 
A Large-Scale Industrial Case Study on Architecture-based Software Reliabilit...
A Large-Scale Industrial Case Study on Architecture-based Software Reliabilit...A Large-Scale Industrial Case Study on Architecture-based Software Reliabilit...
A Large-Scale Industrial Case Study on Architecture-based Software Reliabilit...
Heiko Koziolek
 

Andere mochten auch (14)

PerOpteryx
PerOpteryxPerOpteryx
PerOpteryx
 
Parameter Dependencies for Component Reliability Specifications
Parameter Dependencies for Component Reliability SpecificationsParameter Dependencies for Component Reliability Specifications
Parameter Dependencies for Component Reliability Specifications
 
Q-ImPrESS
Q-ImPrESSQ-ImPrESS
Q-ImPrESS
 
Towards Software Sustainability Guides for Industrial Software Systems
Towards Software Sustainability Guides for Industrial Software SystemsTowards Software Sustainability Guides for Industrial Software Systems
Towards Software Sustainability Guides for Industrial Software Systems
 
ICSE 2011: Q-ImPrESS - An Industrial Case Study on Quality Impact Prediction
ICSE 2011: Q-ImPrESS - An Industrial Case Study on Quality Impact Prediction ICSE 2011: Q-ImPrESS - An Industrial Case Study on Quality Impact Prediction
ICSE 2011: Q-ImPrESS - An Industrial Case Study on Quality Impact Prediction
 
A Model Transformation from the Palladio Component Model to Layered Queueing ...
A Model Transformation from the Palladio Component Model to Layered Queueing ...A Model Transformation from the Palladio Component Model to Layered Queueing ...
A Model Transformation from the Palladio Component Model to Layered Queueing ...
 
Rapid Performance Modeling by transforming Use Case Maps to Palladio Componen...
Rapid Performance Modeling by transforming Use Case Maps to Palladio Componen...Rapid Performance Modeling by transforming Use Case Maps to Palladio Componen...
Rapid Performance Modeling by transforming Use Case Maps to Palladio Componen...
 
Sustainability Evaluation of Software Architectures: A Systematic Review
Sustainability Evaluation of Software Architectures: A Systematic ReviewSustainability Evaluation of Software Architectures: A Systematic Review
Sustainability Evaluation of Software Architectures: A Systematic Review
 
MORPHOSIS: A Case Study on Lightweight Architecture Sustainability Analysis
MORPHOSIS: A Case Study on Lightweight Architecture Sustainability AnalysisMORPHOSIS: A Case Study on Lightweight Architecture Sustainability Analysis
MORPHOSIS: A Case Study on Lightweight Architecture Sustainability Analysis
 
Evolving Industrial Software Architectures into a Software Product Line: A Ca...
Evolving Industrial Software Architectures into a Software Product Line: A Ca...Evolving Industrial Software Architectures into a Software Product Line: A Ca...
Evolving Industrial Software Architectures into a Software Product Line: A Ca...
 
6 Years of Performance Modeling at ABB
6 Years of Performance Modeling at ABB6 Years of Performance Modeling at ABB
6 Years of Performance Modeling at ABB
 
2011 05-27-icse
2011 05-27-icse2011 05-27-icse
2011 05-27-icse
 
A Large-Scale Industrial Case Study on Architecture-based Software Reliabilit...
A Large-Scale Industrial Case Study on Architecture-based Software Reliabilit...A Large-Scale Industrial Case Study on Architecture-based Software Reliabilit...
A Large-Scale Industrial Case Study on Architecture-based Software Reliabilit...
 
Towards the Automation Cloud: Architectural Challenges for a Novel Smart Ecos...
Towards the Automation Cloud: Architectural Challenges for a Novel Smart Ecos...Towards the Automation Cloud: Architectural Challenges for a Novel Smart Ecos...
Towards the Automation Cloud: Architectural Challenges for a Novel Smart Ecos...
 

Ähnlich wie The SPOSAD Architectural Style for Multi-tenant Software Applications

Summer School Delivering On-Demand Shared Middleware Services
Summer School   Delivering On-Demand Shared Middleware ServicesSummer School   Delivering On-Demand Shared Middleware Services
Summer School Delivering On-Demand Shared Middleware Services
WSO2
 
Scalable Architecture on Amazon AWS Cloud - Indicthreads cloud computing conf...
Scalable Architecture on Amazon AWS Cloud - Indicthreads cloud computing conf...Scalable Architecture on Amazon AWS Cloud - Indicthreads cloud computing conf...
Scalable Architecture on Amazon AWS Cloud - Indicthreads cloud computing conf...
IndicThreads
 
Choosing Your Windows Azure Platform Strategy
Choosing Your Windows Azure Platform StrategyChoosing Your Windows Azure Platform Strategy
Choosing Your Windows Azure Platform Strategy
drmarcustillett
 
Understanding the WSO2 Platform and Technology
Understanding the WSO2 Platform and TechnologyUnderstanding the WSO2 Platform and Technology
Understanding the WSO2 Platform and Technology
WSO2
 
Data Driven Innovation with Amazon Web Services
Data Driven Innovation with Amazon Web ServicesData Driven Innovation with Amazon Web Services
Data Driven Innovation with Amazon Web Services
Amazon Web Services
 

Ähnlich wie The SPOSAD Architectural Style for Multi-tenant Software Applications (20)

Introducing SQL Server Data Services
Introducing SQL Server Data ServicesIntroducing SQL Server Data Services
Introducing SQL Server Data Services
 
Software Architecture Definition for On-demand Cloud Provisioning
Software Architecture Definition for On-demand Cloud ProvisioningSoftware Architecture Definition for On-demand Cloud Provisioning
Software Architecture Definition for On-demand Cloud Provisioning
 
SnapLogic corporate presentation
SnapLogic corporate presentationSnapLogic corporate presentation
SnapLogic corporate presentation
 
Cloud architecture and deployment: The Kognitio checklist, Nigel Sanctuary, K...
Cloud architecture and deployment: The Kognitio checklist, Nigel Sanctuary, K...Cloud architecture and deployment: The Kognitio checklist, Nigel Sanctuary, K...
Cloud architecture and deployment: The Kognitio checklist, Nigel Sanctuary, K...
 
Cloudian_Cassandra Summit 2012
Cloudian_Cassandra Summit 2012Cloudian_Cassandra Summit 2012
Cloudian_Cassandra Summit 2012
 
Summer School Delivering On-Demand Shared Middleware Services
Summer School   Delivering On-Demand Shared Middleware ServicesSummer School   Delivering On-Demand Shared Middleware Services
Summer School Delivering On-Demand Shared Middleware Services
 
Scalable Architecture on Amazon AWS Cloud - Indicthreads cloud computing conf...
Scalable Architecture on Amazon AWS Cloud - Indicthreads cloud computing conf...Scalable Architecture on Amazon AWS Cloud - Indicthreads cloud computing conf...
Scalable Architecture on Amazon AWS Cloud - Indicthreads cloud computing conf...
 
The Modern Web Part 4: Cloud Computing
The Modern Web Part 4: Cloud ComputingThe Modern Web Part 4: Cloud Computing
The Modern Web Part 4: Cloud Computing
 
Engineering practices in big data storage and processing
Engineering practices in big data storage and processingEngineering practices in big data storage and processing
Engineering practices in big data storage and processing
 
Choosing Your Windows Azure Platform Strategy
Choosing Your Windows Azure Platform StrategyChoosing Your Windows Azure Platform Strategy
Choosing Your Windows Azure Platform Strategy
 
Introduction to AWS tools
Introduction to AWS toolsIntroduction to AWS tools
Introduction to AWS tools
 
SQL Server Reporting Services: IT Best Practices
SQL Server Reporting Services: IT Best PracticesSQL Server Reporting Services: IT Best Practices
SQL Server Reporting Services: IT Best Practices
 
SwiftKnowledge Multitenancy
SwiftKnowledge MultitenancySwiftKnowledge Multitenancy
SwiftKnowledge Multitenancy
 
Qué hay de nuevo en sql azure
Qué hay de nuevo en sql azureQué hay de nuevo en sql azure
Qué hay de nuevo en sql azure
 
Database as a Service - Tutorial @ICDE 2010
Database as a Service - Tutorial @ICDE 2010Database as a Service - Tutorial @ICDE 2010
Database as a Service - Tutorial @ICDE 2010
 
Understanding the WSO2 Platform and Technology
Understanding the WSO2 Platform and TechnologyUnderstanding the WSO2 Platform and Technology
Understanding the WSO2 Platform and Technology
 
End-to-End Integrated Management with System Center 2012
End-to-End Integrated Management with System Center 2012End-to-End Integrated Management with System Center 2012
End-to-End Integrated Management with System Center 2012
 
Treasure Data: Big Data Analytics on Heroku
Treasure Data: Big Data Analytics on HerokuTreasure Data: Big Data Analytics on Heroku
Treasure Data: Big Data Analytics on Heroku
 
Data Driven Innovation with Amazon Web Services
Data Driven Innovation with Amazon Web ServicesData Driven Innovation with Amazon Web Services
Data Driven Innovation with Amazon Web Services
 
Using Distributed In-Memory Computing for Fast Data Analysis
Using Distributed In-Memory Computing for Fast Data AnalysisUsing Distributed In-Memory Computing for Fast Data Analysis
Using Distributed In-Memory Computing for Fast Data Analysis
 

Mehr von Heiko Koziolek

Mehr von Heiko Koziolek (8)

Bottleneck Identification and Performance Modeling of OPC UA Communication Mo...
Bottleneck Identification and Performance Modeling of OPC UA Communication Mo...Bottleneck Identification and Performance Modeling of OPC UA Communication Mo...
Bottleneck Identification and Performance Modeling of OPC UA Communication Mo...
 
Architectural Decision Forces at Work: Experiences in an Industrial Consultan...
Architectural Decision Forces at Work: Experiences in an Industrial Consultan...Architectural Decision Forces at Work: Experiences in an Industrial Consultan...
Architectural Decision Forces at Work: Experiences in an Industrial Consultan...
 
OpenPnP: a Plug-and-Produce Architecture for the Industrial Internet of Things
OpenPnP: a Plug-and-Produce Architecture for the Industrial Internet of ThingsOpenPnP: a Plug-and-Produce Architecture for the Industrial Internet of Things
OpenPnP: a Plug-and-Produce Architecture for the Industrial Internet of Things
 
Tool-Driven Technology Transfer in Software Engineering
Tool-Driven Technology Transfer in Software EngineeringTool-Driven Technology Transfer in Software Engineering
Tool-Driven Technology Transfer in Software Engineering
 
Self-commissioning Industrial IoT Systems
Self-commissioning Industrial IoT SystemsSelf-commissioning Industrial IoT Systems
Self-commissioning Industrial IoT Systems
 
IoT challenges for Smart Manufacturing
IoT challenges for Smart ManufacturingIoT challenges for Smart Manufacturing
IoT challenges for Smart Manufacturing
 
Software Architecture in Process Automation: UML & the "Smart Factory"
Software Architecture in Process Automation: UML & the "Smart Factory"Software Architecture in Process Automation: UML & the "Smart Factory"
Software Architecture in Process Automation: UML & the "Smart Factory"
 
Plug-and-Produce based on Standardized Industrie 4.0 Asset Admin Shells
Plug-and-Produce based on Standardized Industrie 4.0 Asset Admin ShellsPlug-and-Produce based on Standardized Industrie 4.0 Asset Admin Shells
Plug-and-Produce based on Standardized Industrie 4.0 Asset Admin Shells
 

Kürzlich hochgeladen

+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...
+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...
+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...
?#DUbAI#??##{{(☎️+971_581248768%)**%*]'#abortion pills for sale in dubai@
 

Kürzlich hochgeladen (20)

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
Connector Corner: Accelerate revenue generation using UiPath API-centric busi...Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
 
Manulife - Insurer Transformation Award 2024
Manulife - Insurer Transformation Award 2024Manulife - Insurer Transformation Award 2024
Manulife - Insurer Transformation Award 2024
 
Ransomware_Q4_2023. The report. [EN].pdf
Ransomware_Q4_2023. The report. [EN].pdfRansomware_Q4_2023. The report. [EN].pdf
Ransomware_Q4_2023. The report. [EN].pdf
 
presentation ICT roal in 21st century education
presentation ICT roal in 21st century educationpresentation ICT roal in 21st century education
presentation ICT roal in 21st century education
 
Corporate and higher education May webinar.pptx
Corporate and higher education May webinar.pptxCorporate and higher education May webinar.pptx
Corporate and higher education May webinar.pptx
 
A Year of the Servo Reboot: Where Are We Now?
A Year of the Servo Reboot: Where Are We Now?A Year of the Servo Reboot: Where Are We Now?
A Year of the Servo Reboot: Where Are We Now?
 
DBX First Quarter 2024 Investor Presentation
DBX First Quarter 2024 Investor PresentationDBX First Quarter 2024 Investor Presentation
DBX First Quarter 2024 Investor Presentation
 
Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
Strategize a Smooth Tenant-to-tenant Migration and Copilot TakeoffStrategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
 
Artificial Intelligence Chap.5 : Uncertainty
Artificial Intelligence Chap.5 : UncertaintyArtificial Intelligence Chap.5 : Uncertainty
Artificial Intelligence Chap.5 : Uncertainty
 
+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...
+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...
+971581248768>> SAFE AND ORIGINAL ABORTION PILLS FOR SALE IN DUBAI AND ABUDHA...
 
Boost Fertility New Invention Ups Success Rates.pdf
Boost Fertility New Invention Ups Success Rates.pdfBoost Fertility New Invention Ups Success Rates.pdf
Boost Fertility New Invention Ups Success Rates.pdf
 
Data Cloud, More than a CDP by Matt Robison
Data Cloud, More than a CDP by Matt RobisonData Cloud, More than a CDP by Matt Robison
Data Cloud, More than a CDP by Matt Robison
 
Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...
Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...
Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...
 
A Beginners Guide to Building a RAG App Using Open Source Milvus
A Beginners Guide to Building a RAG App Using Open Source MilvusA Beginners Guide to Building a RAG App Using Open Source Milvus
A Beginners Guide to Building a RAG App Using Open Source Milvus
 
Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...
Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...
Emergent Methods: Multi-lingual narrative tracking in the news - real-time ex...
 
Axa Assurance Maroc - Insurer Innovation Award 2024
Axa Assurance Maroc - Insurer Innovation Award 2024Axa Assurance Maroc - Insurer Innovation Award 2024
Axa Assurance Maroc - Insurer Innovation Award 2024
 
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
 
AWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of TerraformAWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of Terraform
 
EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER
EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWEREMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER
EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER
 
Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe
Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, AdobeApidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe
Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe
 

The SPOSAD Architectural Style for Multi-tenant Software Applications

  • 1. The SPOSAD Architectural Style for Multi-tenant Software Applications Heiko Koziolek Industrial Software Systems ABB Corporate Research 1
  • 3. 28.04.2008: „SAPs new SME software ‚Business By Design‘ jammed“ 25.10.2008: „SAP will part with outsourcing partner“ 19.02.2009: „SAP denies sales stop for ‚Business by Design‘“ Source: heise.de 3
  • 4. Single-Tenancy Multi-Tenancy Tenant1 Tenant2 Tenant3 Tenant1 Tenant2 Tenant3 App App App App Database Database Database Database OS OS OS OS Hardware Hardware Hardware Hardware 4
  • 5. Challenges Lack of Ad-hoc Technology Documentation Solutions Focus 5
  • 6. Architectural Styles An architectural /style is a coordinated set of  Client Server  Blackboard architectural constraints that restricts  Pipe-and-Filter  C2 the roles / features of architectural elements and the  Peer-to-Peer allowed relationshipsREST (WWW)  among those elements within any architecture that conforms to that style.  Mobile Code  SPIAR (AJAX) [Fielding2000] Idea: Multi-tenancy Style 6
  • 7. Resource Sharing Elasticity Architectural Architectural Properties Properties Maintainability Customizability 7
  • 8. SPOSAD Style for Multi-Tenancy  Shared  Polymorphic  Scalable  Application and  Data
  • 9. SPOSAD Style for Multi-Tenancy Client Tier Application Tier Data Tier Application Multi-tenant Browser Cache (optional) Load Balancer Threads Database REST Asynch, Customization Synch Data REST Transfer Meta-Data Meta-Data Rich Client Manager 9
  • 10. SPOSAD Style for Multi-Tenancy Client Tier Application Tier Data Tier Elasticity Maintainability Application Multi-tenant Browser Cache (optional) Load Balancer Threads Database REST Asynch, Customization Synch Data REST Transfer Meta-Data Meta-Data Rich Client Manager Customizability Resource Sharing 10
  • 11. Multi-tenant Database Private Table Layout Extension Table Layout Universal Table Layout 11
  • 12. Multi-tenant Database Private Table Layout Extension Table Layout Universal Table Layout Account27 AID Name Robot Speed Account33 1 ABC X 20 AID Name 2 DEF Y 50 1 GHI Account46 AID Name Lines 1 JKM 12 12
  • 13. Multi-tenant Database Private Table Layout Extension Table Layout Universal Table Layout Industrial-Account Tenant ID Row Robot Speed Account-Extension 27 0 X 20 Tenant ID Row AID Name 27 1 Y 50 27 0 1 ABC 27 1 2 DEF Telecommunication-Account 33 0 1 GHI Tenant ID Row Lines 46 0 1 JKM 46 0 12 13
  • 14. Multi-tenant Database Private Table Layout Extension Table Layout Universal Table Layout Universal Tenant ID Table Col1 Col2 Col3 Col4 Col5 Col6 27 0 1 ABC X 20 - - 27 0 2 DEF Y 50 - - 33 1 1 GHI - - - - 46 2 1 JKM 12 - - - 14
  • 15. Shared Single Code Base Architectural Architectural Data Resources Constraints Properties STATE Customization Component Stateless Application Tier 15
  • 16. Architectural Trade-offs Resource Sharing vs. Security / Availability Complexity vs. Time to market Customizability vs. Maintainability 16
  • 18. Client Tier Application Tier Data Tier Virtual Application Customized Components Oracle RAC Application Multi-tenant Browser Cache (optional) Load Balancer Threads Database REST Asynch, Customization Synch Data REST Transfer Meta-Data Meta-Data Rich Client Manager Universal Table Runtime Engine Layout 18
  • 19. Client Tier Application Tier Data Tier Web / Worker Blobs, Tables, Roles SQL Azure Application Multi-tenant Browser Cache (optional) Load Balancer Threads Database REST Asynch, Customization Synch Data REST Transfer Meta-Data Meta-Data Rich Client Manager Worker Role 19
  • 20. Client Tier Application Tier Data Tier JSP / Servlet, Google Big Table Python Application Multi-tenant Browser Cache (optional) Load Balancer Threads Database REST Asynch, Customization Synch Data REST Transfer Meta-Data Meta-Data Rich Client Manager App Engine Services 20
  • 21. …and SAP? ? 27.01.2010 „With feature pack 2.5, appearing in summer this year, Business ByDesign gets a multi-tenant architecture“ Peter Lorenz Chief SME Solutions SAP Source: isreport.de 21
  • 22. Conclusions Multi-tenancy as an Architectural Style 22
  • 23. 23

Hinweis der Redaktion

  1. Salesforce-Amerikanische Silicon Valley FirmaEiner der berühmtestenSoftware as a Service providerCustomerRelationship SoftwareUmsatz 2009: 1 Mrd US$, 47000 Kunden, über 1.1 Mio Benutzer, auf angeblich weniger als 1000 ServernKunden: z.B. Deutsche Bank, Allianz VersicherungSalesforce.com zählt zu den am schnellsten wachsenden Technologieunternehmen weltweit. Laut Forbes wächst nur Google schneller (Stand: Januar 2008).Technisch beeindruckend: hohe Skalierbarkeit, steigende Anzahl an Transaktion: mehr als 14 MrdTransaction pro Quartalsinkende Antwortzeiten: weniger als Viertelsekunde mittlere Antwortzeit pro ausgelieferter Seite
  2. SAP Business By DesignVoll integrierte Enterprise ResourcePlanning Lösung für kleine und mittelständische Unternehmen in einer gehostetenSaaS LösungEntwicklung seit 2003, angekündigt 2007 für 2008, 2010 noch nicht voll ausgerolltGerüchte: Entwicklungskosten bei über 500 Mio EuroKlemmt:-"Das System hat noch nicht die erforderliche Performance und hat noch zu viele Aussetzer", zitiert die Zeitung einen SAP-Entwickler. Es müsse noch viel zu viel aufwendig nachjustiert werden.- massive Performance-Probleme in der früherern Entwicklung, unterstützte nur 10 Benutzer pro ServerVerkaufsstopp?- Ursprünglich hatte man in Walldorf mit 10,000 zahlenden Kunden bis zum Jahr 2010 kalkuliert, doch derzeit scheint es davon noch keine 100 zu geben. -SAP sei mit seinen Diensten einfach zu teuer, und außerdem gebe es speziell bei Mittelständlern anhaltende Ängste, ihre wertvollen Geschäftsdaten einem Software-Dienstleister außerhalb ihrer Kontrolle anzuvertrauen. Die Probleme von Business by Design haben verschiedene Ursachen. Meiner Meinung nach ist eine dieser Ursachen, dass SAP auf eine single-tenant Architektur und nicht auf eine multi-tenant Architektur gesetzt hat
  3. Tenant = Organization, Unternehmen mit Mitarbeitern als BenutzerMTEine applikation / eine Code Basis, zentrale Updates/Patches, spezielle Vorrichtungen für Kundenspezifische AnforderungenEine DB, geteilte Schemata, gemeinsame TabellenEin OSEine Hardware, verteilt, LastverteilungSkalierbarkeit durch Lastverteilung auf Cluster, spezielle Datenbankabfragen, wenig overheads, minimum an mehrfach Vorhandenen RessourcenST- Angepasste Applikation pro Kunde (Firma)DB pro Kunde Viele OS LizenzenServer pro KundeVorteil Sicherheit, Nachteil: Skalierbarkeit, schwierig sich an Lastspitzen anzupassen
  4. Was ist also das Problem? Die Herausforderung?Documentation:Kein Handbuch für Multi-tenancyarchitekturen, keine BücherKaum wissenschaftlich LiteraturDas Umsetzen von Multi-tenancy wird weitläufig noch als Wettbewerbsvorteil gesehen und daher verschleiertKonstruktion schwierig, ohne Hilfestellung/Doku sehr teuerAd-hoc SolutionsTry-and-error Prinzip, kein Erfahrungsschatz, Wissen wird von Unternehmen nicht weitergeben Wacklige LösungenArchitekten können trade-offs (Zielkonflikte) nur schwierig einschätzenTechnologieGuides für Microsoft-Produkte und SaaS, Guides von IBM für Java Produkte und SaaSHöhere Abstraktion fehltArchitekturkonzepte nicht formal und technologie-unabhängig dokumentiert
  5. Jetzt die Lösungidee, mein Ansatz!Was könnte die Lösung sein?Fielding, REST, WWW, 2000: Ein Architekturstil ist eine koordinierte Menge von architektonischen Bedingungen / Einschränkungen, die die Rolle der Architekturelement und deren Beziehungen zu einander einschränken.Beispiele: Client-Server, der Server arbeitet nur auf Anfrage, verschickt keine eigenen AnfragenPipe-and-Filter: es gibt keinen Zwischenspeicher, alle Informationen für die Berechnungen werden zwischen den Komponenten weitergereichtUsw.Modernere Stile sind REST für das WWW und SPIAR for AJAX AnwendungenDie Idee ist nun, Multi-tenancy in diese Liste einzureihen und explizit als Architektur Stil zu dokumentieren.Dokumentationsschema nach Perry und Wolf: Komponenten, Konnektoren, Daten Elemente und constraints auf diesen Elementen
  6. ArchitecturalProperties = Ziele, können auch als Anforderungen verstanden werden,Hier 4 der wichtigsten:ResourceSharing:Möglichst viel Hardware und Software soll gemeinsam genutzt werdeVerhindert die Verschwendung von Ressource, kompliziert aber Isolation von ClientsBeispiele: -Kosteneinsparung für Datenbankadministration durch gemeinsame Datenbanken-Speichereinsparung durch nicht-dedizierte ServerElasticity:Hier könnte auch Scalability stehen, also die Fähigkeit mit wachsender Anfragelast zurecht zukommen (siehe Salesforcefolie)Elasticity schließt auch das Stoppen von Servern mit ein wenn die Anfragelast sinkt, daher werden die Ressourcen am effektivsten genutztWichtig für MT systeme wegen der hohen Anzahl an Tenants und der potentziell sehr großen Anfragelast mit LastspitzenMaintainability:Einsparung von Wartungskosten durch eine einzelne Anwendung und Codebasis für alle TenantsBugs müssen nur einmal behoben werdenBugfixes müssen nur einmal eingespielt werden, es müssen keine Fixes von Kunden installiert werden, dies erfolg zentralCustomizability:-bei nur einer geteilten Anwendung: Anpassungen an eigene Geschäftprozesse und Datenmodelle notwendig-Kunden geben sich nicht mit Standardlösungen zufrieden
  7. SPOSAD steht für Shared, Polymorphic, ScalableApplication and Data- Hier jetzt Teil der Lösung, high-level Ansicht der Komponenten und Connectoren die in diesem Stil zum Einsatz kommenBasiert auf multi-tierarchitektur: clienttier, evtl. presentationtier, applicationtier, datatierClient: Web Browser (Internet Explorer), Rich Client (Eclipse RCP)Synchrone REST Kommunikation mit ApplicationtierOptionale Cache, Lastverteiler für meherer Server ApplicationThreads, stellen Präsentation und Business Logic bereit, basieren auf gleichem Code sind aber für verschiedene Tenants über Metadata anpassbarMeta-Data Manager verwaltet Meta-Daten (z.B. proprietäre Datenfelder, GUI, Workflows, Forms, usw.) und passt den Applikationscode anMulti-tenant Datenbank, gemeinsam genutzt von allen Tenants, Enthält Daten (Kundennr, Konto, usw.) und Meta-daten (Datentypen, proprietäre Erweiterungen)Asynchrone KommunikationAndere Sichten hier nicht gezeigt, Virtualisierung kann drunterliegenErstmal nur highlevel, man kann die einzelnen Komponenten noch aufschlüsseln und die Kommunikationsbeziehungen detailierter beschreibenWie bilden sich nun die gewünschten Architektureigenschaften ab?
  8. SPOSAD steht für Shared, Polymorphic, ScalableApplication and Data- Hier jetzt Teil der Lösung, high-level Ansicht der Komponenten und Connectoren die in diesem Stil zum Einsatz kommenBasiert auf multi-tierarchitektur: clienttier, evtl. presentationtier, applicationtier, datatierClient: Web Browser (Internet Explorer), Rich Client (Eclipse RCP)Synchrone REST Kommunikation mit ApplicationtierOptionale Cache, Lastverteiler für meherer Server ApplicationThreads, stellen Präsentation und Business Logic bereit, basieren auf gleichem Code sind aber für verschiedene Tenants über Metadata anpassbarMeta-Data Manager verwaltet Meta-Daten (z.B. proprietäre Datenfelder, GUI, Workflows, Forms, usw.) und passt den Applikationscode anMulti-tenant Datenbank, gemeinsam genutzt von allen Tenants, Enthält Daten (Kundennr, Konto, usw.) und Meta-daten (Datentypen, proprietäre Erweiterungen)Asynchrone KommunikationAndere Sichten hier nicht gezeigt, Virtualisierung kann drunterliegenErstmal nur highlevel, man kann die einzelnen Komponenten noch aufschlüsseln und die Kommunikationsbeziehungen detailierter beschreibenWie bilden sich nun die gewünschten Architektureigenschaften ab?
  9. ResourceSharing vor allem in der Datenbank aber auch in der Infrastruktur (App Container, VM, OS, Hardware)Elasticity z.B. durch LoadBalancer, die auto-scaling unterstützen also auch downgraden.Maintainbility durch gemeinsame Code-basis der ApplicationThreads, nur einmalige Wartung notwendingCustomizability durch Meta-data Manager, der tenant-spezfischen Anpassungen durchführen kannDatenbank im folgenden noch mal genauer, verschieden Schemata zum ResourceSharing möglich
  10. VorherComponent&connectorView, jetzt Information View, wie sind die Daten strukturiert
  11. Jeder Tenant bekommt seine eigenen Tabellen mit möglicherweise eigenen Datenfeldern 27, 33, 46 sind die TenantidsVorteil: keine komplizierten Joins notwendig, einfach zu implementierenNachteil: Overhead für die Erstellung und Verwaltung von vielen kleinen Tabellen bei großer Anzahl von Tenants
  12. Gemeinsame Daten werden in einer großen Tabelle gehalten für alle TenantsTenant-spezifische Erweiterungen über eigene TabellenVorteil: weniger Tabellen, weniger OverheadNachteil: möglicherweise aufwändige, ineffiziente Joins um die Daten zu rekonstuieren
  13. -Daten aller Tenants in einer einzigen Tabelle, Spalten im Varchar Datentyp für beliebige Erweiterungen-Vorteil: sehr geringer Verwaltungs- und Speicheroverhead-Nachteil: Rekonstruktion der Datentypen, Backups, Rowlevelaccesscontrolusw-> keine one-size-fitsit all Lösung, jedoch ist das Universal Table Layout dasjenige mit dem meisten ResourceSharing- Wird so von force.com genutzt, eine Tabelle mit 500 variablen Spalten für alle 50000 tenants, spezielle Query-Optimierungs Routinen
  14. Nach der Definition von Fielding zeichnen vor allem die Einschränkungen einen Stil ausHier 4 der wichtigsten EinschränkungenNur eine Code-Basis für alle Tenants: Einsparung von Wartungskosten, mehrere Codebasen angepasst für individuelle Tenants/Clients sind nicht zulässingGemeinsame Datenressourcen: keine eigenen Datenbanken pro Tenant zur Einsparung von OverheadsEs gibt eine Komponente zur Anpassung der Applikation an Kundenanforderungen: keine StandardapplikationKein client-spezifischer Zustand darf im Application Tier gehalten werden: Erhöht die Skalierbarkeit, keine Wartezeiten für ApplikationsthreadssEvaluation schwierig. Es müssten erste Applikationen nach dem Stil gebaut werden und dann getestet werden, ob sie die angestrebten Architektureigenschaften erfüllenAuch der Aufwand für die Entwicklung auf Basis des Stils müsste mit einer Ad-hoc Entwicklung verglichen werdenDas ist bisher auch für andere Stile nicht gemacht worden.- Hier nur sehr eingeschränkte Form der Evaluierung: Vergleich der Architekturkonzepte mit den Konzepten der neuen PaaS Plattformen
  15. Force.com basiert auf der Salesforce Infrastruktur, lässt es zu dort eigene Applikationen zu erstellenWindows Azure ist Microsofts Antwort auf Cloud computing, viele MS technologien, .NET, basiert auf Windows Server 2008Google AppEngine: Java und Python Welt
  16. Die Idee ist MT als Architekturstil zu dokumentierenVorteileLeichtere Entwicklung für zukünftige Projekte, schränkt den Entwurfsraum einKosteneinsparungen durch weniger Try-and-errorIngenieursmäßiger Ansatz, best PracticesTechnologieagnostik, keine Spezifika von .NET oder Enterprise Java, Fokus auf ArchitekturkonzepteQuantifizierung und Konkretisierung von Trade-offs, ZielkonfliktenFuture Work: stilbeschreibung verfeinern, detaillieren, Evaluation verbessern, SaaSapplikationen untersuchen