• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Multi-site Architecture Considerations
 

Multi-site Architecture Considerations

on

  • 1,634 views

 

Statistics

Views

Total Views
1,634
Views on SlideShare
466
Embed Views
1,168

Actions

Likes
1
Downloads
20
Comments
0

10 Embeds 1,168

http://www.platformcf.com 686
http://www.cfsummit.com 268
http://cfsummit.com 89
http://localhost 68
http://platformcf.com 32
http://www.cloudfoundry.org 9
http://cloudfoundry.org 7
http://platformcf2.cfapps.io 5
http://platformcf1.cfapps.io 3
http://plus.url.google.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Multi-site Architecture Considerations Multi-site Architecture Considerations Presentation Transcript

    • 1
    • 2 Michael Behrendt, IBM Senior Technical Staff Member Multi-site Architecture Considerations
    • 3  Improve redundancy of apps and CloudFoundry itself  Control location of apps and services – for latency, governance, etc. reasons Objectives of running CloudFoundry across multiple sites
    • 4  All CloudFoundry- internal components  Apps  Services Components in scope NATS RouterRouterRouters Blobstore Health Manager RouterRouterDEAs RouterRouterServicesUAA UAA_DB RouterRouterCloud Controllers CC_DB AppsApps Apps Application End users Developers
    • 5 Key Considerations
    • 6 1. Support any number of sites Site A Site B Site … Site C Application End usersDevelopers
    • 7 2. Tolerate outage of any number of sites Site A Site B Site … Site C X X Application End usersDevelopers
    • 8 2. Tolerate outage of any number of sites  dedicated CF deployment per site? Site A Site B Site … Site C A p p s A p p s A p p s A p p s A p p s A p p s A p p s A p p s Application End usersDevelopers
    • 9 3. Access all sites from a single point of entry  cross-site management & traffic distribution function needed? Site A Site B Site … A p p s A p p s A p p s A p p s A p p s A p p s Cross-site management & traffic distribution • “See” all apps & services across sites • Push & update etc. apps in dedicated regions • Create/bind service instances in dedicated regions Access apps deployed across multiple sites via a single URL Site C A p p s A p p s Application End usersDevelopers
    • 10 Site A Site B Site … Site C A p p s A p p s A p p s A p p s A p p s A p p s A p p s A p p s Cross-site management & traffic distribution 4. Cross-regional management  Shared cross-regional knowledge needed? • Bind service instances against apps running in multiple sites • Spaces across sites • … Shared data • Cross-site app  services binding • Use of linked data? Application End usersDevelopers
    • 11 Thank you – We’re hiring –
    • 12