News for hackers. Stuff that matters.
Re:The End of Microservices by carterehsmith on Thursday July 21, 2016 @02:50AM (#12135208)
You are not getting more reusability from a bunch of microservices, compared to one big service, I don't see where you got that?
Re:The End of Microservices by vog on Thursday July 21, 2016 @03:06AM (#12135254)
I also don't see how microservices are more reusable.

However, the replacability is usually much better due to being forced to define sharp boundaries with clear interfaces.

Re:The End of Microservices by pjmlp on Thursday July 21, 2016 @05:21AM (#12135696)
But that is the thing.

It just means that instead of using the language features and creating clean interfaces across modules, they were witting spaghetti code.

With microservices they get to write spaghetti REST calls with the added fun of distributed computing failures.

Re:The End of Microservices by IshKebab on Thursday July 21, 2016 @07:47AM (#12136180)
Normal software libraries also have sharp boundaries with clear interfaces. Why use shitty RPC-over-HTTP? At the very least you can use something sane like Thrift.
Re:The End of Microservices by sanmon3186 on Thursday July 21, 2016 @05:31AM (#12135738)
> the replacability is usually much better due to being forced to define sharp boundaries with clear interfaces

If by "sharp boundaries with clear interfaces", you mean API specification, how is it a microservice thing? I thought the benefits of microservices lie in behind-the-scenes details.

Re:The End of Microservices by _pmf_ on Thursday July 21, 2016 @03:12AM (#12135267)
I think it's the old loose coupling vs. late binding discussion. Some people confuse the former with the latter.

You can very mechanically achieve late binding with microservices, but it takes extra effort to actually achieve loose coupling; and guess what, the effort might or might not be less than doing loose coupling within the components of a monolith.

Re:The End of Microservices by kevinr on Thursday July 21, 2016 @03:37AM (#12135349)
I was just reading the other day this article about the Backend for Frontend pattern (BFF) which suggests the best way to avoid tight coupling is for services you don't want tightly coupled to be owned by different teams, and to allow reasonable duplication of functionality between them. Everybody knows how hard it is to get another team to implement functionality for you.

This is where I got the BFF pattern from:

http://samnewman.io/patterns/architectural/bff/

Re:The End of Microservices by _pmf_ on Thursday July 21, 2016 @05:25AM (#12135714)
I fully agree with this. If a system cannot be extended by some external team using only external extension points, all claims of modularity and architecture are idle talk.

I tend to use MEF (on .NET) and OSGi (on the JVM) not because I actually need extensibility, but because I want to enforce certain architectural constraints.

Re:The End of Microservices by lobster_johnson on Thursday July 21, 2016 @11:37AM (#12137554)
You missed my point. I did not say reusability is the only factor that dictates the use of microservices.

If we wrote everything as one big service, we'd lose the dozen-or-so benefits of microservices.

Hypothetically, if we rewrote what we have today as one big monolith:

* We couldn't selectively open-source parts of it.

* It'd really all have to be a single language, as opposed to the three we use right now.

* ...and if we decided to change the language (like we're in the process of doing with a transition from Ruby to Go + Node.js), we'd have to rewrite all of it.

* Deployment would be potentially more brittle since you're deploying a single codebase. Our apps are designed to gracefully tolerate partial unavailability.

* We'd have to be careful to control individual services' resource footprint. We have some services which are super light and have very few dependencies — they don't carry a monolith on their back.

* We'd have to jam in product-specific stuff for N different products into a single codebase. Some of our microservices aren't reusable; they're completely product-specific. Squishing lots of unrelated concerns into a single codebase is not feasible.

* Developers would be trying to tightly couple services and violate separation of concerns faster than you can spell "technical debt".

...and so forth.

Maybe I didn't articulate it well enough, but my original point was that microservices are great for all sorts of reasons, but also a too-often missed point is the benefits of reusability if you just design thing right.

Put differently, microservices are a lot less powerful if you don't design them for reusability (and, as a prerequisite, multi-tenancy)

Re:The End of Microservices by onion2k on Thursday July 21, 2016 @03:17AM (#12135287)
You are if you care about whether you're deploying things that aren't necessary. With microservices you can take a single specific service that two projects share and reuse it. With a monolith you can't unless you deploy everything else as well. That can easily fail a requirements check (say, hardware requirements are too costly) and force you to redevelop the service for the second project.
Re:The End of Microservices by weego on Thursday July 21, 2016 @03:33AM (#12135339)
I'm not trying to be facetious, but isn't that just called a library?
Re:The End of Microservices by onion2k on Thursday July 21, 2016 @03:57AM (#12135421)
Not as I understand microservices. A library would be something that's compiled or included in to your application code. A microservice is a separate process that the application communicates with over a protocol (eg http).
Re:The End of Microservices by sbov on Thursday July 21, 2016 @04:11AM (#12135466)
I think the point is you can achieve the same result by just using a library.

There are potential benefits and downsides to services over libraries of course, but unless there are specific requirements that make a library unsuitable, all else equal I would rather just use a library.

Re:The End of Microservices by jcrites on Thursday July 21, 2016 @05:11AM (#12135670)
There are a number of downsides of libraries that make services attractive by comparison. Of course, it's not as if one or the other is better in all circumstances.

First, libraries don't encapsulate very well. A storage service hides its representation from users. A storage service can change its implementation at any time without users having to know or care. Perhaps you migrate from Cloud Provider X to Y. A shared storage library, on the other hand, can't just change its implementation on a whim. Libraries vend functionality, and they encapsulate functionality at a coding level, but they don't encapsulate much at a systems level, especially in distributed systems. For example, if this function would talk to a data store like a database or another remote service, then under the service approach, only one application talks to the database, while with the library approach, a ton of applications using the library do -- and now they all need network access to that DB and credentials to talk to it. They care about the details of how to reach it. Every library consumer needs that configuration.

With a service, you can implement security features like input sanitization and access control on the service-side. With a library, you're reliant entirely on trusting its users. (A library can have these functions too, but a malicious user or attacker can bypass them if they compromise the machine it's running on. A service implementation runs in a different security context.)

When a library changes, you need to tackle the problem of distributing the new version to every application that uses it. When a service changes, you just deploy the new version, and all systems using it immediately experience the new version. When a service changes, you can completely coordinate the way in which the new functionality rolls out. You can pass 1% of requests through a new version of the code, if you want. You can pass requests through both versions of the code, and compare one to the other. You can in principle do these things with a library, but few organizations have the ability to roll out updates to all usages of a library nearly as effectively as they can change and redeploy a service. Services allow the service owner to centrally control the behavior of the functionality in all circumstances where it's used.

Libraries don't help you scale different parts of your system differently. For example, let's say that the storage service needs to cache a lot of content for good response times. If that's a library, then all of the applications using it need to have adequate RAM or disk for the cache. With a storage service, that can be hidden behind the service interface, and only the machines running the service need the extra RAM/disk.

Services are portable in a way that libraries are not. A library needs to be implemented in a way that can be consumed within many platforms. For example, it might not be easy to vend the same function for applications on Windows, Ubuntu, MacOS. With a service, I might vend only an interface description, or lightweight clients for the platforms I target.

A service separates the consumption of the functionality entirely from its operation. If there's a defect in the service, like it's returning the wrong result, then that's the service owner's problem to fix and roll out an update. If the library everyone is using in their applications is returning the wrong result, then that's now everyone's problem.

With a service, I can measure anything and everything I might want to know about the behavior of an operation. I can record metrics and log files and anything I want. With a library, there isn't always an easy way to get the information out of applications that use it. Services make applications easier to understand and troubleshoot, because you can reduce the amount of code running on any given machine (VM) to the smallest reasonable amount, compared to applications that embed potentially many libraries. Debugging a library is tricky because you need to debug the application too. I can debug or instrument a service all on its own, without affecting its clients.

The right answer to this question might depend on the scale of the component's usage, the scale of the functionality, and how much you care about these properties, and encapsulation, and coordinated update, etc. Services start to become compelling at a sort of inflection point where you have a lot of usage, enough that updating all applications using a library would be problematic, and you want to decouple things (both components within software and the organizations that develop and run them). I probably have more to say about this, but I'll leave it here. There are plenty of reasons why you'd choose to make something a library, but there are also good reasons why to choose a service.

Re:The End of Microservices by onion2k on Thursday July 21, 2016 @05:11AM (#12135669)
Microservices also enable you to scale individual parts of your application. If you need better performance for, say, image compression then it's much easier to add resources to a service that lives in its own process space (or its own server, or rack of servers, or data centre..) than it is to improve the performance of a specific library in a larger application.
Re:The End of Microservices by zby on Thursday July 21, 2016 @04:37AM (#12135553)
With some work you can have the some behaviour - but the microservice is also about the data (like user ids and passwords for a login microservice).
Re:The End of Microservices by jbverschoor on Thursday July 21, 2016 @04:34AM (#12135547)
So you deploy your easy to manage monolith, and expose your library through an rpc service. rest, thrift or whatever is hip these days.
Re:The End of Microservices by rodgerd on Thursday July 21, 2016 @03:20AM (#12135298)
From experience at the classic ball o' mud web servicey end of the spectrum, because it gets to hard to manage and deploy and test services that you end up standing up new services to do "the same thing only slightly different" because reusing existing services is too hard.
Re:The End of Microservices by fleitz on Thursday July 21, 2016 @03:05AM (#12135243)
It's especially fun when you get to write the monolith 3 times over for web, ios and android.
Re:The End of Microservices by carterehsmith on Thursday July 21, 2016 @06:58PM (#12140636)
Why would you write it three times?

You write it once, have it expose an API. Have your Web, IOS and Adroid client use the said API. Easy pease. Optional: allow your customers to use the API, too.

Re:The End of Microservices by fleitz on Saturday July 23, 2016 @02:38AM (#12148613)
That's not 'microservices'