[timruffles]

Does this feel like backtracking to anyone else? Compare to Fowler's previous discussions [1].

Maybe it's just hard to write about a new, interesting thing without most people getting the impression you think it's the way (especially developers, who seem eager to declare any new tool the One True Way® and everything else 'legacy').

[1] http://martinfowler.com/articles/microservices.html#AreMicro...

[trustfundbaby]

No?

> So we write this with cautious optimism. So far, we've seen enough about the microservice style to feel that it can be a worthwhile road to tread. We can't say for sure where we'll end up, but one of the challenges of software development is that you can only make decisions based on the imperfect information that you currently have to hand

[timruffles]

I think I linked to the most balanced bit of that article :)

"We've seen many projects use this style in the last few years, and results so far have been positive, so much so that for many of our colleagues this is becoming the default style for building enterprise applications"

"Monolithic applications can be successful, but increasingly people are feeling frustrations with them "

[cam-]

Integrating lots of points is a pain in the ass. Integrating a new service was a 13 in a sprint. Adding a field to an existing service is 3. Often the aggregation gets pushed into the front end layer as well so the customer workflows get mixed with the service logic. Which is not pretty.

[twotwotwo]

> Maybe it's just hard to write about a new, interesting thing without most people getting the impression you think it's the way

Man, kind of resonates. Things like SOAP arguably trace back to a reasonable impulse followed with too much zeal.