4 ms·
I've yet to see a big reason for this whole SOA / microservices architecture other than in 2 specific instances: 1) massive projects with lots of developers/te
by manigandham 11y ago
I've yet to see a big reason for this whole SOA / microservices architecture other than in 2 specific instances:
1) massive projects with lots of developers/teams that work on well-defined functionality
2) massive projects that need to have precise capacity at each service level rather than the application level
Other than these situations, monoliths (both in architecture and deployment) will likely be faster, easier, more reliable and more productive.
- krooj 11y agoThere are two insidious angles at play with the push for MSAs: 1. Software stacks for MSAs dovetail too well with the cloud service offerings from the same company or a division of the parent (EMC/Pivotal) 2. Latency kills. How are you avoiding it with highly distributed choreographed flows that are present in MSAs?
- joshwa 11y ago#1 describes most software projects of any business significance.
- pbreit 11y agoBut describes near zero projects in startup world.
- manigandham 11y agoThis would most likely be separate applications, perhaps sharing some configuration or central service like authentication, rather than what is commonly referred to as microservices.
- lobster_johnson 11y agoOne big reason I always bring up and which I never ever see spoken of is reuse. Our microservices are reusable. We have lots of user-facing apps -- different web sites, each with their constellation of services required -- that all use an overlapping set of microservice backends. If we have a new app, we are usually able to write it entirely as a front end. We pick and mix those backends we need. For example, we have microservices for: Identity/auth/authorization; messaging (SMS, email); image processing; geocoding and various other GIS operations; event logging; site map management; and so on. One of most important services manages data as documents, with data in Postgres and queries through ElasticSearch, with a fine-grained security system. All our apps use it, and many of the microservices are layered on top of it. With a monolithic architecture we would have been forced to write this stuff as libraries, and forced our apps to use a single language. (Our microservices are written in Go, Ruby and JavaScript.)
- seanp2k2 11y agoI mean no disrespect by this, but those things sound more like modules / libraries than services with their own infrastructure.
- lobster_johnson 11y agoYou can be forgiven for thinking that. But these microservices require configuration and often multiple running processes. For example, our image scaling pipeline runs multiple processes per machine, all coordinated through RabbitMQ. Ideally we'd scale deployment automatically based on the number of queued-up tasks, but we don't have the infrastructure set up for that at the moment. There's also language issue, as mentioned: A library-oriented design would require everything to be written in the same language (modulo anything you can do with C bindings and such — no thanks!). We have stuff written in three different languages, and it's actually very nice to be able to do that, and not worry about language-level compatibility. For example, we are in the process of writing a completely new data backend in Go (the old one is Ruby). We have that choice because no app needs to care what it's written in. Having each microservice be its own app also forces you into a different and, in my opinion, healthier "shared nothing" mindset. You're not allowed to cheat by bypassing the API and tightly coupling yourself to the internals of the implementation, which in turn forces you to design good distributed APIs.
- home_boi 11y agoFrom a developer perspective, it's more fun to build an entirely new service
- therein 11y agoDefinitely this. It also allows the codebase to evolve as the languages, platforms and frameworks come and go.
- voodootrucker 11y agoAnd that's the problem I've had with large teams of developers. I was on a project with something like 10 scrum teams, and they all wanted to write their own isolated "microservices", so they didn't have to worry about integration. Of course integration had to happen either way, and it just kicked the can down the road and made it a "dev ops" problem. (Dev ops in quotes because real dev ops wouldn't have been a separate team in the first place) The point is, you have to integration test, you have to define an API, you have to not make breaking changes, and you have to do all these things regardless of deployment modality. Beware the disguised call for microservices which is really just a request "not to worry about integration testing".
- manigandham 11y agoMaybe... but fun shouldn't be playing a part in technical architecture decisions.
- gedrap 11y agoThat's assuming you are starting to develop the project from scratch. But that's not the case. Imagine, you join a company and their product is one, ugly monolith with a lot of technical debt. Now, you need to build some big and complicated features on top of this, and there are no similar features so far. Implementing it as a service can be much faster, have quicker iterations (especially if the deployment methods for the monolith are crap, which is often the case) and easier to build a high quality implementation. As long as you don't go crazy and ended up with ridiculous number of poorly separated services, this might be a good decision in long term (been there, done that). Based on anecdotal data (where n=3), that's very often the case.