how to make the management of a league system less traumatic
summary
Shows how to migrate a fragile legacy database into a Laravel 5.5 backend without changing the schema by using Eloquent models to map inconsistent column names, Laravel resources to normalize API output, and accessors/casts to preserve legacy formats. Describes adding targeted unit tests to avoid regressions, incrementally growing a new web app to replace old clients, and reusing an existing boolean soft-delete field to represent suspension; notes the system is running in production though some input normalization and front-end tests are still incomplete.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:36Choosing Laravel
- 6:51Database consistency issues
- 9:07Laravel models for messy tables
- 11:37Normalizing data with Resources
- 14:04Testing importance
- 15:49Suspending maintenance safely
- 17:39Future improvements
related talks
48mMigrating a 15 Year Old Enterprise Application to Laravel: Lessons Learned and Opportunities Gained
30mLegacy to Laravel in 30 minutes
28mDaniel Coulbourne :: Flip the Switch Slowly
28mMigrating to Laravel: Managing the ick
44mBuilding a complex product while scaling a team and a business on Laravel
25mWriting resilient code
40mEngineering Complex Applications with Laravel 4
49mLaravel - If, how and why you should use it!