Holly leads the "Cloud Garage" at IBM, working with customers to create solutions when moving to the cloud.

Holly gives the summary of the "Cloudy With A Chance Of Meatballs" movie.

Story of the hero who wanted to make the world better, but ended up making some mistakes.

Cites Joseph Campbell, who observed the commonalities among the world's myths. He finds the recurring themes among them. He formed the idea of the "monomyth". There is actually only one story: the quest.

  • all to action

  • obstacles

  • reward

Observes we are the hero of our own story.

Some aspects of being that with respect to being a developer.

Listed some rockstar programmer skills: automate, tools mastery, etc.

Hero stories for the cloud

Long deploy times.

But what about the obstacles

Adoption is still not complete. Relates this to the hero's "call to action".

  • Security fears

    Bank: Watson discovery. The crawler that populates the ML by putting all the data in the cloud.

    But you must encrypt it.

    In the traditional stack, the dev is responsible for the security of their code. In the cloud, the entire stack, including the OS, is the built artifact. So the developer must take responsibility for OS patches, and everything on up through the stack.

  • Cloud-nativeness

    Definition: it's not just centralized computing.

    History lesson: tty, mirocomputer, client-server, PC, Grid computing, laptops, cloud, edge computing. She used a sine wave to cover what I often depict as a pendulum.

    CNCF: Containerized, Dynamically orchestrated, microservices oriented.

    Holly adds: elasticity and agility, as well as assuming everything is unreliable.

    JVM considerations: the traditional Rafael Benevides concerns: containers get killed.

    Logging: the need for data analytics simply to get access to the logs. Prometheus.

    Microservices are hard. They seem like a great idea, but when you try them. Here is where she brings back in the meatball movie.

    Cost for Kubernetes clusters, especially if you fail to tear them down when you are done.

    Needing a cloud to manage your cloud.


QaaS quantum as a service

renewed interest in IaaS because the I can have super expensive hardware, such as GPU loaded machines.

Cloud Native Thinking

Digital Native analogy