cloud

Friday, June 25, 2021

- CEST
Automating & Monitoring Seedling Growth in the Cloud Using IoT, Messaging & Micronaut
Todd Sharp
Todd Sharp
Oracle, Developer Advocate

It all started with a small project to pass the time during The Great Quarantine of 2020. I bought some chiles from the local farmer’s market (with proper face coverings and social distancing, of course), fermented my first batch of hot sauce, and shared it with a few friends around the globe. I had no idea the sauce would be such a massive success, so I resolved to build on that triumph in 2021. But this time, I knew that I would have to start from the very beginning and grow the chiles myself. Of course, this presented the wonderful opportunity to combine two of my life’s greatest passions - the culinary arts and technology - to ensure that my growth operation was the ultimate success. Join me in this session where I show you how I used a microcontroller, some sensors, and the cloud to monitor and automate the germination and maturation of this year’s crop.

- CEST
Replicating production on your laptop using the magic of containers
Grace Jansen
Grace Jansen
IBM, Developer Advocate

This will include a short introductory presentation on what test containers are, how they differ from other types of testing, and why they’re useful, as well as showing a live demo of how to use tools like MicroShed testing to enable this.

Saturday, June 26, 2021

- CEST
Exploring Stateful Microservices built with Open Source Java in Kubernetes
Mary Grygleski
Mary Grygleski
IBM, Senior Developer Advocate

How does one choose to architect a system that has a Microservice / REST API endpoints? There are many solutions out there. Some are better than others. Should state be held in a server side component, or externally? Generally, we are told this is not a good practice for a Cloud-Native system, when the 12-factor guidelines seem to be all about stateless containers, but is it? It’s unclear and this confusion may lead to poor technology stack choices that are impossible or extremely hard to change later on as your system evolves in terms of demand and performance.

While stateless systems are easier to work with, the reality is that we live in a stateful world, so we have to handle the state of data accordingly to ensure data integrity beyond securing it.

We will examine and demonstrate the fundamentals of a Cloud Native system with Stateful Microservices that’s built with Open Liberty in Kubernetes:

  • Microservices/REST API – Options to use when running your apps in the JVM
  • Concurrency – how to take advantage of multi-core CPUs and clustered distributed systems
  • Stateful vs Stateless - while stateless apps are easier to implement, the bulk of the apps in production are stateful which involve a higher level of complexity and risk, especially when data would need to travel across multiple machines and network boundaries
  • Deployment – how about containerization and orchestration using Kubernetes?
- CEST
Survival Guide for the Java Architect in the Cloud Era
Otavio Santana
Otavio Santana
ZupInnovation, Principal Engineer

Let's be very honest, cloud computing cannot be learned in one day. There are several architectural challenges to deploying your application, such as which framework to choose, reflection or reflectionless, native or non-naive. We also have the operational challenges such as backups, CI/CD, and much more.

This presentation explains how to make some of these design choices and the tradeoffs to consider when building applications to run in a virtual cloud environment.