The Doppler Quarterly Summer 2018 - Page 26

That leaves Container Orchestration and Serverless – two legitimate platforms that are positioned to han- dle the demands cloud native imposes on IT environ- ments, now and in the future. IoT, big data and messages. Middleware layers can be optimized to improve application performance over time. And Serverless also allows for easy integration to third-party APIs and plug-ins. Container Orchestration — These platforms– But there are some downsides. Serverless is a less mature computing model, so there are less compre- hensive and stable samples, tools, best practices and documentation. It is harder to debug than other plat- forms. Due to the on-demand structure, revving up “cold starts” after the system sits idle can trigger problems. Serverless workload runtimes are also capped at five minutes; anything longer requires additional orchestration or refactoring into multiple microservices. such as Kubernetes, Swarm and Mesos–give develop- ers power they never had on PaaS or other conven- tional development platforms. They can build and deploy portable applications, and run them any- where, without having to reconfigure and deploy for different environments. This capability gives developers a tremendous amount of flexibility and control over which exact image versions to deploy, and where. They can essen- tially oversee the whole infrastructure – giving them the final say over runtimes, reusability of images and movements of containerized apps to the cloud. The downside to Container Orchestration? It intro- duces a new level of complexity to the process. Build- ing a Kubernetes cluster that is highly available is a complicated task. Adding more container orchestra- tors requires developers to pay more attention to things like service discovery, load balancing, capacity management, monitoring, logging, version upgrades and other common services. So, developers will l have their work cut out for them, or else they will have to rely on managed Kubernetes orchestrators, such as EKS, Fargate, AKS or GKE, which come with a certain degree of vendor lock-in and versions which lag behind the latest. Serverless — Serverless platforms involve much less hands-on care than container orchestrators. Using X\U[XK^\H[[ۜ܂PH[\][Y[X[\[ܚ]HX˜\X[YX\وH]\ۙXYX™][ˈ\\\\\[X[HHX[YY\XK][\[\ۈ\X][ۜ]\ۙY\[]H]ܛHZH\Hو[H[KB[[8$]][[][[\XY[[B[]˂\\ܙX]܈][\[]\YHB^KX\^[KY[[ X\\ۛH܈B[YH]H\XX[H[[ˈ\ܚ[܂][ Y][[[YXXHܚYX\ŒHTSSQT N\][]H]ܛH][ۂX]ܛH[HO\H\[BY[\8$ۙK\^KY]X[][ۋ\Z[\\وܚY]]\[۝Z[\[ B\\H[ܙH][Y\\\[\ۛY[ˈ[B[]ܚY\ \[[ۈZ\\XB\\X[Hܙ[^][۸&\YYˈH[\ܝ[[\\\H܈HڙX[\HY]Y\[ۜ[H[XZHH\X] H[B\\\[\ۛY[[HH\]܂ܙY[Y[\\Z[[ݙYHY ][][ܚY[[][]\]Z\\Hق[[ˈ[\]HX[\[ܚY]YY[H[ٙ\\H[[Y]\܂\\\ˈ[Y][ۋ[\^HX[\\B[]]\YH\\\XH˜]]X]H\X\\[]]]Y[X\]H][[YYX][ۜ[\\]]\[[]ˈۈH\[ YXHܚY]YY[ܙH۝[]HH[ݙY\[ [[]وHY ]\[۝Z[\ˈH[ܙBܘ[[\H\]Z\[Y[H[ܙH[][ۋBZ[\XYK]\H[\[Y\[ˈ]]X][ۜ\K[ܙ[^][ۜYYY[][KB][ۈ\YܙH[ۈH]ܛH] BYH܈Y []]H\][