5 ms·
You can have services, just not micro. Splitting into few services that are obviously conceptually separate is enough. If you are a typical web company, you can
by aschatten 7y ago
You can have services, just not micro. Splitting into few services that are obviously conceptually separate is enough. If you are a typical web company, you can have a dedicated service for search, maybe a separate service for internal tools and the main app. Granular enough that teams in charge can be focused on on their area and wide enough to avoid complexity.
- jayd16 7y agoImo, that is identical to "microservices" but you're right that there's no reason to go any more than what you need. I always felt the whole microservice hype/movement was simply about defining multiple services as a useful pattern you'll want to use and how to build infrastructure to make it easy. But I agree wholeheartedly. You don't need 100+ services to get the benefits of converting your tool chain to handle deploying n services even if n=3.
- aschatten 7y agoI think prefix “micro“ confuses me :) Opens up a debate as to how granular you need to go. Another thing that confuses me is whether microservice architecture is conceptually different to SOA. Some say it is, some view it as another iteration of SOA.
- VBprogrammer 7y agoIn that case I'd say it's unlikely you are truly embracing microservices in the manner that their evangelists intended (and don't misunderstand me, you are probably right not to). One of the characteristics of microservices is that they are small enough that they can be completely written in a couple of weeks. Like every other fad in technology the nuances and practicalities are lost along the way. Now that we have all started bashing microservices can we all take a minute to reflect on what a steaming pile of shit monoliths can turn into without a huge amount of respect for the artificial boundaries and interfaces that you create.
- aschatten 7y agoWhere was it stipulated that a characteristic of a microservice is that it can be completely written in a couple of weeks?
- VBprogrammer 7y agoIf I remember correctly it's mentioned in Building Microservices - Sam Newman. I confess I don't have it on me at the moment to confirm that though.
- aschatten 7y agoThanks for the reference.
- jayd16 7y agoI've always felt the "micro" terminology just meant that a service might be that small and that's ok. I don't think of it as a requirement. I don't really read any comments recommending I break up services more than I need. Usually its a conversation about "hey sometimes its better to have n services and you should spend a little time making that easy."