Container Microservices vs. PaaS
Transcript
hey how's it going to ski from the CTO of Viacom today you CTO daily dose for October 24th 2017 I've been working on this blog post at least I've been working on it in my mind I got the first paragraph written down about containers versus platform-as-a-service so this is therapeutic for me as much as it's hopefully informative to you and I've been working through this concept since before daca con 2017 EU last week there's this thing that that's been kind of eating at me as to
what is it applicable if at all to use a platform as a service such as cloud foundry Microsoft Azure platform as a service and the number of passes that's available versus constructing and bringing your own to bear there's variations of the two it's not a new topic you know we've had service-oriented architectures in the past and now we've just layered cloud on top and pivotal Cloud Foundry has been teaming up with VMware to blur the lines between containers pass traditional infrastructure whereas all of this kind
of play so let's start off with the basic concept of a micro service versus a platform as a service so typically we're thinking about building micro services based off of containers application that has micro service based on containers so we might have sam'l running in a container as a micro service I'm trying to think of other services so we might have a messaging bus running as part of a container platform and then finally we may have specific to your application let's say a encoding app servers
running inside of a content you could then bond do all of this off put it into a kubernetes scheduler and then have your applications consume each individual micro service that leads lives in a container and you can pretty much build your own path so to speak without engaging a pivotal oars or or set or etc that allows developers to pull pull out containers and micro services from repository as needed so if they want to use tip coal as the messaging bus they could use typical for
their messaging bus that's compared to kind of the black box that is a path so let's say we have pile foundry as a pass so Kyle foundry will have in that a very rigid set it has and I don't know enough about Kyle founder you say that it has his own messaging bus but as an example would have his own messaging bus it has its own equivalent for sam'l it would have an API gateway etc to have all these services already bonded in you basically rolled
out Cloud Foundry and your developers have to consume it as available so as the as a as a developer needs a new micro service they consume the micro service from Cloud Foundry and build their application based on that cloud Cloud Foundry principle I don't think anyone from Cloud Foundry or pivotal would disagree with me it's called an opinionated pass for a reason it gives you a consistent platform across application teams to develop your solution versus containers as they bring your own micro services or bring your
own pass solution the blog post that I'm working on is kind of comparing those two approaches when should you use one versus the other application development isn't my core skill set so you know what it is a bit of a stretch project for me but I'd love to hear your feedback container based approach to micro services or a opinionated path such as or or on-premises Cloud Foundry or even stuff that redhead is doing hit me up on the twitter at CTO advisor on twitter or on
the web the c2 advisor calm or the best place to have a conversation is only and Keith the LinkedIn profile is linkedin.com for /i e n4 /k l townsend talk to you next CTO daily dose
