Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Modern problems in backend engineering, Joel Mislav Kunst

Modern problems in backend engineering, Joel Mislav Kunst

  • Sé el primero en comentar

  • Sé el primero en recomendar esto

Modern problems in backend engineering, Joel Mislav Kunst

  1. 1. Migrating from monolith to microservices Starship - Joel Mislav Kunst
  2. 2. Problems • hard to maintain a big codebase by many people • hard to get started for new people • lots of mixed logic understood by a very few people • inefficient to run
  3. 3. Action Plan • new stuff --> separate service • if new stuff is written in js --> extract common part from the monolith into modules • if bigger changes needed to a monolith part that has most of dependencies extracted --> extract it to a separate service
  4. 4. Problems 2 • distributed monolith • hard to debug • kubernetes packet loss
  5. 5. Action Plan 2 • new stuff --> it's own DB • critical existing services --> stop using central DB • distributed tracing (mongo proxy) • introduced kafka • js --> ts
  6. 6. Problems 3 • PDD (Production Driven Development) • most of the people know only about their stuff • multiple auth handlers
  7. 7. Action Plan 3 • Improve alerting and monitoring (influx --> prometheus) • e2e tests, more integration tests, better sandbox environment, canary deployment • knowledge sharing • all auth (internal) --> use auth service • extract more critical stuff from monolith
  8. 8. Conclusion • Be purposeful (unit tests) • No big plans, start NOW • Share knowledge
  9. 9. Questions?

×