Big companies mostly seem to use the microservice(s) per team model. If your whole company is two founders, one account manager, and an engineer, you only have one team.

It can make sense to have more than one service for purely technical reasons. I once worked on a friend's startup where we built a separate ingress microservice so we could scale it independently from our monolith. There's no organisational benefit to doing so, however. The technical founder and the one engineer are hardly going to block each other.

▲

vjvjvjvjghv 44 minutes ago | parent | next [-]

"Big companies mostly seem to use the microservice(s) per team model. "

I am good with that. What we often see is 10 microservices per team of 3 devs. And ideally using the same database.

	▲	masonhensley 16 minutes ago \| parent [-]
		I've seen a startup with 10 devs + 60+ microservices and growing. The team was stuck in a mindset that they just hadn't split things up enough to arrive at nirvana.

▲

wredcoll 12 minutes ago | parent | prev [-]

Microservices are a solution to business/team organizational issues. Never technical ones.