Entrevistamos a Cristian Cotes
summary
Argues for gradual adoption: introduce practices that reduce risk first and postpone big structural changes until metrics justify them, using signals like deploy frequency, mean time to recovery and coupling as decision criteria. Recommends prioritizing continuous integration and automated tests to get fast feedback before adopting microservices or heavy DDD modeling. Offers a short checklist of hard signals (deploy pain, rollback rate, test flakiness) and a single-practice pick when time or budget is limited.
AI-written summary · about
related talks
27mThe technical journey to microservices
50mTactics and strategies on software development: how to reach ...
51mResponsible Microservices
45mBuilding and evolving microservices: lessons from the frontlines
27mTinkertoys, Microservices, and Feature Management: How to Build for the Future
49mCase study of a good enough architecture
01h 00mAgile Architecture
46mSix small steps towards continuous delivery