Domain Driven Design When Surrounded by Legacy Development (2013) [pdf]
domainlanguage.com
domainlanguage.com
When I first got to the job I thought it might be worthwhile to refactor and upgrade the old codebase, but eventually settled on the cordon strategy because it's ultimately more flexible, and not having to touch the production site every day gives me a lot of peace of mind.
Anyone in this situation, I would recommend re-implementing your Active Record models with an external database connection using Sequel or even just regular SQL queries. I have a giant query with a crapload of joins that can retrieve product data, it's among the very first things I built at this job.
This provides a nice base to build on, the database is the heart and soul of the business, and it is far easier to work at that level of abstraction rather than trying to mess around inside the codebase.
To the op and the author, my most sincere thanks.
http://www.infoq.com/interviews/eric-evans-brian-foote-desig...
Mud flowing into a project scope is a powerful image.
Bonded contexts, for example, immediately clarified how to establish naming conventions across micro-services.
No one sets out to create a legacy system (maybe some consulting companies do), they just get more complex/ scary overtime. As the codebase and layers of technical debt are added, while documentation and the original creators disappear.
I'd love to know the economic cost of businesses held back by legacy systems each year.
I used to think that an open source project that hadn't been updated since 2002 was inherently bad. Now I've realized that sometimes this means that it is just done and it's so simple that everything that has changed over the past decade is addressed by ./configure and make.
http://stackoverflow.com/questions/25648676/ddd-repository-u...