3 ms·
Microservices can work great for v1, but you absolutely need a common rpc framework and a solid way to deploy, test and monitor. Most teams don't have the right
by simonhorlick 10y ago
Microservices can work great for v1, but you absolutely need a common rpc framework and a solid way to deploy, test and monitor. Most teams don't have the right building blocks. This will change with time.
- voodootrucker 10y agoYou can do this in a company that is already big and mature. If you're doing this from day #1 in a startup environment, then you aren't very lean, and you better have lots of funding and an expert team with experience doing this.
- thwarted 10y agoIf you want to help ensure success, having an expert team with experience on day #1 is going to have more positive influence than having a few, or a fleet, of inexperienced people banging on it.
- voodootrucker 10y agoMuch of the world lives outside of the bay, and isn't backed by lavish VC funding. You gotta do what you have to in order to survive. Many exciting innovations have come from the duck-tape and bailing wire community.
- thwarted 10y agoI assumed you were talking about those with VC funding and in the bay area when you referred to "startup environments". And that's exactly who I'm ragging on: SV startups who hire a fleet of inexperienced fresh grads because they are cheap. I agree that you're not going to end up with a solid SOA setup, or anything really, unless you're having experienced experts doing it from day #1. I think you have a greater chance of ending up with an impenetrable majestic monolith if a bunch of inexperienced people are working on it.
- pbreit 10y agoIn v1 you have to be spending nearly all your time on features that will gain users and usage. It's risky wasting energy optimizing your infrastructure since you're unlikely to need it because you fail to get traction.