Charla impartida en Hack Nights Guadalajara

1. https://cloudnative.mx/
https://www.youtube.com/CloudNativeMexico

2. Hi!
• I’m Domingo
• https://twitter.com/domix
• https://github.com/domix
• https://www.youtube.com/CoderDog
• http://domingosuarez.com/
• domingo.suarez@gmail.com

3. Cloud native technologies empower organizations to build and run scalable
applications in modern, dynamic environments such as public, private, and
hybrid clouds. Containers, service meshes, microservices, immutable
infrastructure, and declarative APIs exemplify this approach.
These techniques enable loosely coupled systems that are resilient,
manageable, and observable. Combined with robust automation, they allow
engineers to make high-impact changes frequently and predictably with
minimal toil.
The Cloud Native Computing Foundation seeks to drive adoption of this
paradigm by fostering and sustaining an ecosystem of open source, vendor-
neutral projects. We democratize state-of-the-art patterns to make these
innovations accessible for everyone.
https://github.com/cncf/toc/blob/master/DEFINITION.md

5. According to TheNewStack
1. Packaged as lightweight containers.
2. Developed with best-of-breed languages and frameworks.
3. Designed as loosely coupled microservices.
4. Centered around APIs for interaction and collaboration.
5. Architected with a clean separation of stateless and stateful services.
6. Isolated from server and operating system dependencies.
7. Deployed on self-service, elastic, cloud infrastructure.
8. Managed through agile DevOps processes.
9. Automated capabilities.
10.Defined, policy-driven resource allocation.
https://thenewstack.io/10-key-attributes-of-cloud-native-applications/

6. Micronaut
Cloud Native development in the JVM

7. Motivation
• Containers
• Microservice architecture
• Serverless
• Reduction of resource consumption
• New approaches

8. Micronaut features
• Dependency Injection and Inversion of
Control (IoC), JSR 330 compatible
• Sensible Defaults and Auto-Configuration
• Configuration and Configuration Sharing
• Service Discovery
• HTTP Routing
• HTTP Client with client-side load-
balancing
• Fast startup time
• Reduced memory footprint
• Minimal use of reflection
• Minimal use of proxies
• Easy unit testing
• CLI integration
• GraalVM Support
• Java, Kotlin, Groovy support

9. Modelo
• Tanto Spring como Grails no fueron diseñados para ejecutarse en escenarios
como Serverless, aplicaciones de Android o microservicios de bajo consumo de
memoria.
• Este objetivo se logra mediante el uso de los procesadores de anotaciones de
Java, que se pueden usar en cualquier lenguaje que la JVM admita.
• Proporciona un modelo de programación similar a Spring y Grails
• Los procesadores de anotación precompilan los metadatos necesarios para
realizar la DI, definen proxies AOP y configuración de la aplicación.
• Muchas de las API de Micronaut están fuertemente inspiradas en Spring y Grails.
Esto es por diseño y ayuda a que los desarrolladores lo adopten rápidamente.

10. Modules
• Consul
• Kafka
• Micrometer
• Groovy
• SQL
• MongoDB
• Neo4j
• Redis
• RabbitMQ
• Test
• Netflix
• AWS
• GRPC
• Flyway
• Liquibase
• Elasticsearch
• GraphQL
• OpenAPI

11. Cloud Native features
• Configuration
• Consul
• Spring Cloud
Config
• AWS parameter
store
• Service Discovery
• Consul
• Eureka
• Kubernetes
• AWS Route 53
• Distributed tracing
• Zipkin
• Jaeger

12. Demo 1
First Micronaut application

13. Demo 2
Micronaut fast reload

14. Demo 3
GraalVM support

15. Demo 4
• OpenAPI
• Consul configuration
• Migrations-JPA
• Tracing-Jaeger
• Dockerization
• Metrics (Micrometer, Prometheus)
• Kubernetes

16. Quarkus?