Jemiah Sius at LeadDev West Coast 2023
summary
A team migrates a legacy PHP system to Laravel and React in an API-first design, grows to 10,000 users, then discovers outages via Twitter and decides to shift observability and security left. The claim: instrument during plan and code phases so production problems are predictable not reactive. Practical moves include adopting OpenTelemetry and Grafana, instrumenting code and dashboards with Terraform, automated deploys, tracing microservices, and enforcing SLOs (example: sub-2 second checkout) while patching OSS package vulnerabilities.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:09Modern software responsibilities
- 4:55Shifting left importance
- 8:46Planning and design
- 11:13Development best practices
- 13:19Testing automation
- 14:42Deployment automation
- 16:26Production monitoring
- 19:23Security in production
- 20:27Closing tips
related talks
44mBuilding a complex product while scaling a team and a business on Laravel
46mHow I Built and Scaled a SaaS Product Using Laravel
26mDevOps and Lean in Legacy Environments
48mMigrating a 15 Year Old Enterprise Application to Laravel: Lessons Learned and Opportunities Gained
48mDevops@Scale
28mCultivating success with Laravel
26mMaking internets great again - a story of working with legacy code
05mAdventures In Enterprise: Lessons Learned Promoting DevOps In A Legacy Organization