Week 16, year 2013
- Decoupling (Symfony2) Forms from Entities - I usually tell people to stay away from the Symfony2 Form component, or forms libraries in general. The problem is that all these libraries are designed in a very CRUD mindset. You’ve done all the work to keep your models, views, and controllers nicely separated, and then this component comes along and violates every boundary. The good news is that there is a solution, that allows you to cleanly separate your model from UI. Another example of Encapsulating Operations In my post about the CRUD anti-pattern, I showed how to get rid of setters, using the Encapsulate Operations pattern. Let’s now take the example of an Employee in an HR system. [Mathias Verraes]
- CRUD is an antipattern - CRUD is, as Greg Young calls it, our industry’s Grand Failure. We have deluded our users, and ourselves, that applications are nothing more than a thin layer around our database. We present the user with grids and edit forms, and ask them to fill in fields, that we map more or less directly to our relational tables. We use terms like “data model”. Real processes and businesses are not CRUD though. Real people don’t say “I’ve set the paid amount of the order to ‘120’, the paid currency to ‘EUR’, and status to ‘paid’”. [Mathias Verraes]