55 business logic services? Sounds extremely overengineered. I'm sure at least half of those services should be consolidated into others.
There is no universally "correct" granularity.
You could easily scoff the same way about some number of API endpoints, class methods, config options, etc, and it still wouldn't be meaningful without context.
It's ok to split or lump as the team sees fit.
There is no universally "correct" granularity.
You could easily scoff the same way about some number of API endpoints, class methods, config options, etc, and it still wouldn't be meaningful without context.
It's ok to split or lump as the team sees fit.