287 karma · joined September 14, 2016
So you have to do extra work to make a monolith scale but micro services doesn't have to be that extra work. Much cheaper to spin up redis and have all your backend instances use redis for caching sessions, etc then it is to split your app in to micro services.
From what I can tell, micro services are primarily a solution to an organizational problem and not a technical one and I think people trip over this. If you have 600 developers working on the same back-end then you can benefit from micro services, because you can't possibly fit 600 developers into one standup. You'd never be able to coordinate.
There are rare technical reasons to choose micro services and there is value to micro services when they're used correctly but if you don't have those precise problems then you don't need micro services. List would include situations like having a subsystem that utilizes far greater resources then any other sub system and would be more cost effective running on specialized hardware
Most importantly tho for going 0 to 1 is context. Context is king and always will be. Start ups should not do enterprise services patterns because their not enterprises and neither is the guy coding alone in his bedroom. Your not Netflix. Your not Google. Those companies are going to be so large that they'll encounter every kind of architectural problem. All a start up needs to do is communicate, release, communicate, iterate, repeat. It's the equivalent of asking yourself what did NASA engineers do to send a rocket to the Moon when you're just a guy trying to start a car and get it down the road. Baby steps, for the love of god, baby steps.
I think being a CTO brings it's own unique challenges, perspectives and context. You were a developer. Your not exactly one now and that has to be considered. For one you have context that developers don't and they may not understand that. It also depends on the specific situation. Good code, 'right way', it often just translates to "my definition of right or good". Lots of subjectivity to software development, as weird as that sometimes feels. Lots of ego and ego is a problem.
In my experience a group of developers can believe something is right very strongly and be completely wrong about it and that really sucks because we're social animals and, for better or worst, concensus is often at play in decision making.
No idea how to fix your specific issue but I think it requires openness and sharing and accepting that different people have different opinions on what's correct and everyone has to accept that it differs from person to person. Did you want to share anything specific? Not sure if it'll help but it might give you more insights to get a set of different opinions from outside your usual circle.
Your picking precise word definitions and expecting me to guess which ones your using and yet calling me pedantic. The irony.
Today we have peer review journals, LHC, computers etc and we use that when we practice Science but the tools and the social structure are not Science. Science is a process and anyone can do it.
Your definition of uncoupled makes some sense. It's a good starting place at the very least.