Sharing an effort we are working on for the architecture committee to share
with all. Focused specifically on defining the app patterns that will be deployed with a cloud native infrastructure. Also, specifically defining the enablers that must reside within the cloud native infrastructure to establish a programmable infrastructure
topology. Lastly, proposing interface agreements which must exist among the elements to function together when enabling cloud native behaviors.
The approach is intended to tease out for the team/consideration/discussion
the specific details associated with “container-packaged”, “dynamically scheduled” and “micro-services oriented”. The intent is to assume three major role categories of enablers that contribute to establish cloud native behaviors: Host/Infra foundations, distribution
foundations and app/platform foundations.
Offering an example of a pattern being analyzed I’d offer the following:
Application decomposes into Gateway service, UI/UX services, App Logic Interface, Data Layer Adapter/Interface, Data Model services
Legacy deployment model (Physical or Virtualized) co-locates grouping of these services across typical web/app/db service stack.
Interaction/discovery among intra-app services and from client/peer apps to app services is traditional DNS, IP Route, Load Balancer, ARP, Mac
pathway in an active-active, active-passive failover model.
While elements of the application service model is decomposed and packaged (Containerized) and can be distributed across a container fabric it
does not refactor application logic.
Contrast this with application refactoring to establish a micro-service orientation and illustrate the new platform services that must be present
within the programmable infrastructure topology to support endpoint registration, Service discovery, centralized eventing/messaging and shared frameworks, runtimes and services.
Spinning this up next week on the architecture committee mailing list and welcome
all participation and super-smart brains to collaborate. Huge disconnect in the market right now between containerization and ipso-facto micro-services. Good opportunity for us to provide leadership/clarity imo. Delineation for the masses of the difference
between a virtually hosted workload and true micro-service and the investment/return case inclusive of cloud native elements that must be included.
Look forward to your thoughts.
On Behalf Of Camille Fournier via cncf-toc
Sent: Tuesday, February 14, 2017 1:25 PM
To: Alexis Richardson <alexis@...>
Subject: Re: [cncf-toc] Interesting tech marketing from Amazon