130 likes | 142 Vues
Cloud Native Development- A strategy to build and run applications utilizing Cloud Computing<br>
E N D
Cloud Native Development Source-mu-stack.com
KeyContents Introduction Howdoyoubuildcloudnative applications? Cloud Native Apps vs. TraditionalEnterpriseApps BenfitsOfCloudNative development Conclusion
INTRODUCTION Source-mu-stack.com A strategy to creating and executing apps known as "cloud native" makesuseofthebenefitsofthecloudcomputingdeliverymechanism. Businessesthatcreateand runtheir appsutilisingacloudnative architecture do so more quickly and in response to client requests. Both publicandprivatecloudsaresuitableforcloudnativedevelopment;thekey istofocusonhowratherthanwhereapplicationsarebuiltanddeployed. SSoouurcrcee--mmuu-s-statacckk.c.coomm
Howdoyoubuildcloud nativeapplications? Source-mu-stack.com DevOps - The purpose of DevOps is to deliver high-quality software that addressesconsumerconcernsbyworkingtogetherwithIToperations.Software development, testing, and release occur more quickly, often, and consistently in environmentscreatedbyDevOps. Microservices - A collection of small services, each of which implements a business capability, operates within its own process, and communicates with theothersviaHTTPAPIsormessaging,isreferredtoasamicroservice.Since each microservice can be independently delivered, updated, modified, and restartedfromotherserviceswithinthesameapplication,usuallyaspartofan automated system, rapid upgrades to live applications are possible without havinganadverseeffectonusers. Source-mu-stack.com
Howdoyoubuildcloud nativeapplications? Source-mu-stack.com Containers-Comparedtotraditionalvirtualmachines,containersoffer both efficiencyandspeed(VMs).AsingleOSinstanceisdynamicallysplitintooneor more isolated containers using operating-system-level virtualization, each of which has its own writable file system and resource allotment. Containers are the perfect computing vehicle for deploying lone microservices due to the low overhead of building and destroying them and the great packing density in a singleVM. Source-mu-stack.com
CloudNativeAppsvs.Traditional EnterpriseApps Source-mu-stack.com CLOUDNATIVEAPPS Predictable - The "contract" or architecture that cloud native programmes adhere to is intended to maximise resilience through predictableactions. The way software is built is dictated bytheautomated, container-driven infrastructurefoundincloud platforms. TRADITIONALENTERPRISEAPPS Thiskindofapplicationfrequentlytakes longer to develop, delivers updates in large,irregularbatches,scalesinrather than out, and presumptively ensures highavailabilityofdependentservices. Source-mu-stack.com
CloudNativeAppsvs.Traditional EnterpriseApps Source-mu-stack.com CLOUDNATIVEAPPS Right-sized capacity - When an application is deployed, resources are dynamically allocated and reallocated based on the requirements of the application via acloud native application platform, which automates infrastructure provisioning and configuration. Building on a cloud native runtime improves application lifecycle management, including scalability to meet demand, resource utilisation, orchestration acrossavailable resources,andfailurerecoverywith littletonodowntime. TRADITIONALENTERPRISEAPPS Oversized capacity - Traditional IT delays the launch of an application by creatingaspecial, specialised infrastructure solution (a "snowflake") for it. With minimal potential to scale beyond design restrictions to meet demand, the solution is frequently oversized and constructed to satisfy worst-casecapacitypredictions. Source-mu-stack.com
CloudNativeAppsvs.Traditional EnterpriseApps Source-mu-stack.com CLOUDNATIVEAPPS Independent - Applications are divided into small, loosely linked, independently operating services usingamicroservices architecture. These services enable frequent updates, scaling, and failover/restart without affecting other services and map to smaller, independent developmentteams. TRADITIONALENTERPRISEAPPS Dependent-Monolithicdesigns combine a variety of dissimilar services into a single deployment package, which results in unneeded dependenciesbetweenservices and reduces development and deploymentagility. Source-mu-stack.com
CloudNativeAppsvs.Traditional EnterpriseApps Source-mu-stack.com CLOUDNATIVEAPPS Rapid recovery - A dynamic, high- density virtualization overlay, perfectly suited to the microservices architecture, is provided by the container runtime and orchestrator. In order to allow elastic scaling and recovery/restart intheeventofapporinfrastructure failure, orchestration dynamically coordinates the placement of containersacrossa cluster. TRADITIONALENTERPRISEAPPS Slow recovery - Due to higher startup and shutdown times and operating system overhead for eachVM,VMsbythemselvesare a slower and less effective foundation for microservice- basedsystems. Source-mu-stack.com
BenefitsofCloudNativedevelopment Source-mu-stack.com COSTEFFICIENCY Cloud services only charge for necessary storage space andfeaturesetsrequiredfor your application development model. This pay-as-you-go system ensures lower costs and higherprofits. FASTERDEPLOYMENT Go from concept to implementation within a short span of time by dividing the application into descrete parts using microservices. These can then deployed into different environments without worrying aboutthedependenciesrequired. SECURITY The cloud service provider follows industry-leading securityregulationssuchas HIPPA,PCIDSSandISO 27002. This ensures your application is protected against data breaches, networkandDDoSattacks. Source-mu-stack.com
BenefitsofCloudNativedevelopment AVAILABILITYAND SCALABILITY Source-mu-stack.com SERVER-LESS RESILIENCY Cloud Native applications are designedinsuchawaythatthey don’tgoofflineevenifthere’san infrastructureoutage.Thesefault tolerantapplicationsarecapableof detecting uncertain issues like overload of requests, hardware failures,networkconnectiveerrors, etc. The cloud service provider follows industry-leading securityregulationssuchas HIPPA,PCIDSSandISO 27002. This ensures your application is protected against data breaches, networkandDDoSattacks. Byoptingfor aserverless applicationthedevelopers nolonger havetoworry about networks, security, andscalabilityoftheservers that runbehindthescenes. Theseserversareowned and maintained by service providers reducingtheTotal CostofOwnership(TCO)of theapplication.
Conclusion Source-mu-stack.com A hybrid cloud involves mixed-hybrid computing, storage, and service environmentthatcombineson-premisesinfrastructure,privatecloudservices, and a public cloud, with orchestration between the platforms. As the world has gone remote, there is an increasing demand for applications that are highlyavailablearoundtheglobe. Source-mu-stack.com
Thankyou! Source-mu-stack.com mu-stack.com