At TaskRabbit, we split up our “monolith” into several services with varying degrees of success. It worked from a team organizational perspective but there were unexpected downside in ops, testing, and agility. We tried again along a different axis with more success and solved the noted issues by putting the apps in a single repo.
Conclusions…
Separation and namespacing is the key. It’s about service area of changes, not git repos
One project eases the pain of testing and deployment
Your architecture does not have to match your organization
SOA and/or microservices are talked about a lot, but each case is different.