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, ...
4
 All CloudFoundry-
internal components
 Apps
 Services
Components in scope
NATS
RouterRouterRouters
Blobstore
Health
...
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
...
9
3. Access all sites from a single point of entry
 cross-site management & traffic distribution function needed?
Site A
...
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 & tra...
11
Thank you
– We’re hiring –
12
Upcoming SlideShare
Loading in …5
×

Multi-site Architecture Considerations

2,579 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,579
On SlideShare
0
From Embeds
0
Number of Embeds
1,631
Actions
Shares
0
Downloads
29
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Multi-site Architecture Considerations

  1. 1. 1
  2. 2. 2 Michael Behrendt, IBM Senior Technical Staff Member Multi-site Architecture Considerations
  3. 3. 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. 4. 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. 5. 5 Key Considerations
  6. 6. 6 1. Support any number of sites Site A Site B Site … Site C Application End usersDevelopers
  7. 7. 7 2. Tolerate outage of any number of sites Site A Site B Site … Site C X X Application End usersDevelopers
  8. 8. 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. 9. 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. 10. 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. 11. 11 Thank you – We’re hiring –
  12. 12. 12

×