The reasoning
behind the system.
Six published articles on integration boundaries, reliable events and engineering workflow. Original language, original dates. More room for the details.
From legacy systems to reliable events.
Start with the polling problem, follow changes through MySQL, establish an event contract, then handle duplicates and protect the domain.
All published articles.
Newest first. English and Spanish,
each in its original edition.
Consumers that handle duplicates
Handle repeated events, protect the domain model and separate analytical reads from operational writes.
· ENGLISH · LEGACY TO EVENTS / 4 OF 4From database changes to durable events
Turn database changes into stable event contracts and introduce a durable messaging boundary.
· ENGLISH · LEGACY TO EVENTS / 3 OF 4Reading MySQL changes with Go
Follow MySQL BinLogs with GTIDs, checkpointing and a bounded pipeline instead of introducing another polling loop.
· ENGLISH · LEGACY TO EVENTS / 2 OF 4Legacy integration without polling
Capture relevant changes with triggers and a transactional outbox, without rewriting the legacy application.
· ENGLISH · LEGACY TO EVENTS / 1 OF 4Pruebas más rápidas en CI/CD
Cómo reducir la espera de las pruebas y los pre-push hooks sin renunciar a las comprobaciones importantes.
· ESPAÑOLGit hooks sin frenar el feedback
Una estrategia de comprobaciones locales y draft pull requests para acortar los ciclos de feedback.
· ESPAÑOL