Re:Avoiding the Distributed Monolith
by sebringj on Tuesday April 10, 2018 @05:02PM
(#16805395)
Yah funny you say that about versioning and breaking changes. The side effect of the CMS one for example is its been around for 7 years now and I want to kill it off but there are clients depending on it. I don't even update the code anymore so I guess its ok but from that lesson learned, making the other "microservices" as I've defined them you should build a microservice so it can also be used individually for a client as well as multiple clients where the work of doing one or many is the same so you could easily walk away from the responsibility of hosting it if you wanted.
[ Parent
| on HN ]
It’s good that you want to update it and make it better. However, it it works fine for the clients and they are happy, you should be too.
We all look back on our previous work and see room for improvement, that’s a good thing. However, spending too many cycles trying to achieve perfection where it’s not desired will prevent you from moving on with your life to bigger and better pursuits.
Be really happy that you have a software project which survived for 7 years. Many fail in far shorter time and provide no value.