What we’re about
Grupo de usuarios de Groovy/Grails/Griffon/Gr* de Madrid.
Twitter: https://twitter.com/madridgug
Web: http://www.madridgug.com
Lista de correo: https://groups.google.com/forum/#!forum/madrid-gug
Servidor Mastodon: https://jvm.social
Upcoming events (2)
See all- From Monolith to (µ)Services. What happens with my Data? [Presencial]Red Hat, Madrid, MD
Este es el evento para registrarse si vas a asistir presencialmente. Si no podrás venir en persona y prefieres seguir el evento en remoto por Streaming, debes registrarte en el Evento en Streaming.
Rewriting systems from a monolithic architecture to a services architecture is a common task nowadays to make applications more accessible to maintain, deploy, and release. This migration should not be a big-bang rewrite where you directly switch from the old application to the new one. Instead, it is an incremental process during which functionalities are extracted one at a time into separate services.
The Strangler Fig Pattern describes a method whereby a new system slowly and incrementally grows over the top of an old system. Along the way, the whole system is continuously monitored so that old parts can be removed after the new services show correct behavior. The theory is pretty clear, and in services where no persistence is needed, it's considerably easier, but things become way more complex as soon as data is involved.
Come to this session to learn how Kafka and Debezium, through Change Data Capture and the Strangler Fig pattern, can help you confidently migrate from monoliths to a (micro)services architecture, even though databases are involved.Ponente: Alex Soto
- From Monolith to (µ)Services. What happens with my Data? [Streaming]Link visible for attendees
Este es el evento para registrarse si no vas a poder venir presencialmente y vas a seguirnos en remoto por Streaming. Si vas a asistir presencialmente, debes registrarte en el Evento Presencial.
Rewriting systems from a monolithic architecture to a services architecture is a common task nowadays to make applications more accessible to maintain, deploy, and release. This migration should not be a big-bang rewrite where you directly switch from the old application to the new one. Instead, it is an incremental process during which functionalities are extracted one at a time into separate services.
The Strangler Fig Pattern describes a method whereby a new system slowly and incrementally grows over the top of an old system. Along the way, the whole system is continuously monitored so that old parts can be removed after the new services show correct behavior. The theory is pretty clear, and in services where no persistence is needed, it's considerably easier, but things become way more complex as soon as data is involved.
Come to this session to learn how Kafka and Debezium, through Change Data Capture and the Strangler Fig pattern, can help you confidently migrate from monoliths to a (micro)services architecture, even though databases are involved.Ponente: Alex Soto
![From Monolith to (µ)Services. What happens with my Data? [Presencial] cover photo](https://secure.meetupstatic.com/photos/event/5/2/b/a/event_520581178.webp "From Monolith to (µ)Services. What happens with my Data? [Presencial]")
