O’Reilly Software Architecture Conference 2019 – New York, New York

Sobre este curso

I started my career working in the IBM Watson Research Center on desired state based techniques to address the gap between developers and operators that

was more than 15 years ago since then I was fortunate to be part of an extraordinary evolution in this space in 2009 DevOps was coined and it advocated a cultural transformation as well as

some technological principles where everything is treated as code and is put together in a unified continuous delivery process but software was still complicated and this is mainly due to

the fact that it was written as a big monolith in 2011 micro services were introduced as a set of software engineering principles that advocated fine grained loose coupling and designed

for resiliency applications that were written according to these principles were termed cloud native applications now in the last several years we have made tremendous progress coming together

as a community to build a common cloud platform to run cloud native applications but first why do we need a platform well that's because we want the developer to focus on what she knows

best which is coding we want the platform to take care of the rest which is the container lifecycle the orchestration the networking routing telemetry collection and visibility

building and serving applications and all the rest the emerging cloud platform is really addressing all these issues so at the bottom of course you have kubernetes which addresses the container

lifecycle doja stration and the low-level networking the next layer up is the SEO service mesh and this addresses the routing the security the visibility

the communication and so on and then the next layer up is a new project which is called K native and is addressing unifying the way we're building and serving our applications so this is

great news for us because it allows us to write our code and run it the same way no matter where it runs and this is especially important because we live in a multi cluster multi-cloud reality the

majority of enterprises have a hybrid cloud strategy and many of the applications are written to run on Prem and off Prem and potentially even on multiple public cloud environments some

technologies are emerging to manage these multi cloud environments IBM multi cloud manager is managing the kubernetes cluster lifecycle in multiple different clouds

it checks compliance and it deploys applications into these multi cloud environments based on placement policy all right so what is next I believe we made a tremendous progress

as a community but there's still some challenges ahead of us otherwise it wouldn't be interesting so when you look at the anatomy of cloud native applications they are still very diverse

so they include elements such as event based functions request driven web apps batch analytics such as AI streaming analytics to address large volumes of data stateful stateless and so on and

it's still very hard to write and run these types of applications and this is mainly due to the fact that the space is still very fragmented so if we look for example just like if

event-based functions we have lambda in Amazon we have IBM cloud functions Google Cloud functions just to mention a few I believe what we need to do is to continue to work together as a community

on the next level of abstraction which is a service model for running a diverse cloud native applications I believe we need to do that by building on extending and adding to this common cloud platform

with these three layers iBM is committed to open source I invite everyone to join us on this journey I also invite you to try out this stuff IBM kubernetes cloud service includes an easy installation of

SEO and K native and is running very complicated services such as Watson III and weather company ok thank you you