Re:Kill “Microservices” Before Its Too Late by Chad Fowler
by Terr_ on Thursday October 20, 2016 @06:11PM
(#12756632)
> [16:35] Maybe you should just plan to throw it away.
Definitely. To reiterate something I posted on Reddit a while back:
___
The lesson I've drawn from it is this: Design for deletion. Your first priority is to design your code for the inevitable day when your successor (or perhaps you yourself) dislikes it. The less effort/risk to uncouple and remove it, the better.
Even the most elegant work will eventually stop being relevant as the business' underlying problems change. If that's not true, then what you're working on should probably be structured as an independent library anyway.
Definitely. To reiterate something I posted on Reddit a while back:
___
The lesson I've drawn from it is this: Design for deletion. Your first priority is to design your code for the inevitable day when your successor (or perhaps you yourself) dislikes it. The less effort/risk to uncouple and remove it, the better.
Even the most elegant work will eventually stop being relevant as the business' underlying problems change. If that's not true, then what you're working on should probably be structured as an independent library anyway.