Proposing a Reference Model for Transferable Cloud -Native ...€¦ · Center of Excellence...

1
Center of Excellence Proposing a Reference Model for Transferable Cloud-Native Applications Nane Kratzke Lübeck University of Applied Sciences A cloud-native application is a (micro)service-based, elastic and horizontal scalable application where each self-contained deployment unit of that application is designed according to cloud-focused software design patterns and operated on a self-service agile infrastructure platform. 2 2 2 4 6 7 7 7 7 11 11 1 1 2 4 7 10 14 21 26 42 44 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 Relation of considered services considered by CIMI, OCCI, CDMI, OVF, OCI, TOSCA not considered Coverage by cloud standards decreases year by year. So, cloud-native applications are vulnerable to vendor lock-in. Layer 4 provides a transferable cloud runtime environment to avoid vendor lock-in. Years of a service ”birthday” have been analyzed using over 2300 offical release notes of AWS. Data for other providers like Google, Azure, Rackspace, etc. not presented. Basic conclusions for these providers are the same. Operate application on current provider. Scale cluster into prospective provider. Shutdown nodes on current provider. Cluster reschedules lost container. Migration finished.

Transcript of Proposing a Reference Model for Transferable Cloud -Native ...€¦ · Center of Excellence...

Page 1: Proposing a Reference Model for Transferable Cloud -Native ...€¦ · Center of Excellence Proposing a Reference Model for Transferable Cloud -Native Applications Nane Kratzke Lübeck

Center of Excellence

Proposing aReferenceModelforTransferableCloud-NativeApplicationsNaneKratzkeLübeckUniversityof AppliedSciences

Acloud-nativeapplication is a(micro)service-based,elastic and horizontalscalable application whereeach self-contained deployment unit of that application is designed according to cloud-focused

software designpatterns and operated onaself-serviceagileinfrastructure platform.

2 2

2 4 6 77

7 7 11 11

1 1

2 4 7 1014

21 26 42 44

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016

Relationofconsid

eredservices

consideredbyCIMI,OCCI,CDMI,OVF,OCI,TOSCA notconsidered

Coverage by cloud standards decreases year byyear.So,cloud-nativeapplications are vulnerableto vendor lock-in.

Layer4provides atransferablecloud runtime environment to avoid vendor lock-in.

Years of aservice ”birthday”have been analyzed using over 2300offical releasenotes of AWS.Datafor other providers like Google,Azure,Rackspace,etc.notpresented.Basicconclusions for these providers are the same.

Operate application oncurrent provider.

Scale cluster into prospective provider.

Shutdown nodes oncurrent provider.Clusterreschedules lostcontainer.

Migrationfinished.