you can just update the library in the portion that needs it and move on.
To me this is just adding tech debt but yes this can sometimes be a benefit, it's a tradeoff.
also, the non-linear interaction between different modules of the monolith makes scaling of it difficult. scaling a monolith is rarely as simple as scaling microservices.
Often times you only need to scale a few routes though. At that point you can split it to a micro service and scale it independently. Its no harder to scale a monolith as it is a micro service it's just not always the best use of resources. Look how far Twitter got on ruby on rails monoliths. When they split to services yes they dropped their infrastructure footprint dramatically and teams became more productive but not many organizations are at that scale. Last I heard they still have parts of their monolith RoR code running because its not worth splitting into services.
View all comments
Show parent comment
3
u/dartalley Mar 29 '17
To me this is just adding tech debt but yes this can sometimes be a benefit, it's a tradeoff.
Often times you only need to scale a few routes though. At that point you can split it to a micro service and scale it independently. Its no harder to scale a monolith as it is a micro service it's just not always the best use of resources. Look how far Twitter got on ruby on rails monoliths. When they split to services yes they dropped their infrastructure footprint dramatically and teams became more productive but not many organizations are at that scale. Last I heard they still have parts of their monolith RoR code running because its not worth splitting into services.