Dave Syer,
@david_syer,
dsyer@pivotal.io
Loosely coupled service oriented architecture with bounded contexts…
@adrianco
If every service has to be updated in concert, it’s not loosely coupled.
If you have to know about the internals of surrounding services you don’t have a bounded context.
Easy but Complex
Simple but Hard
No such thing as a free lunch
Q: There’s a technology solution to all those problems?
A: TL;DR Probably not
Paraphrasing @adrianco:
Get out of the business of infrastructure and
automation (a.k.a. "undifferentiated heavy lifting")
Platform features:
Infrastructure | Application |
---|---|
Environment Provisioning |
Distributed/Versioned Config |
On-Demand/Automatic Scaling |
Service Registration/Discovery |
Failover Resilience |
Routing/Load Balancing |
Routing/Load Balancing |
Service Integration |
Data Service Operations |
Fault Tolerance |
Monitoring |
Asynchronous Messaging |
If you make the rule that you own the code that you write, you soon get to know what #cloudnative means!
@david_syer
/