News for hackers. Stuff that matters.
Re:Microservices by throwaway13337 on Thursday September 15, 2016 @03:36PM (#12509129)
Microservices, like nosql databases, and complex deployment systems (docker) are very important solutions to problems a very small percentage of the development community has.

It just so happens that the portion of the community is the one most looked up to by the rest of the community so a sort of cargo cult mentality forms around them.

A differentiator in your productivity as a non-huge-company could well be in not using these tools. There are exceptions, of course, where the problem does call for huge-company solutions, but they're rarer than most people expect.

Re:Microservices by pbreit on Thursday September 15, 2016 @04:16PM (#12509467)
My company built from the ground up with micro-architecture and it is an unmitigated disaster. Totally unnecessary, mind-numbing problems unrelated to end-user features, unpredictability at every step, huge coordination tax, overly-complex deployments, borderline impossible to re-create, >50% energy devoted to "infrastructure", dozens of repos, etc.

The whole thing could be trivially built as a monolith on Rails/Django/Express. But that's not exciting.

Re:Microservices by blowski on Thursday September 15, 2016 @05:40PM (#12510059)
Interestingly, the Sam Newman book about Microservices specifically says it's easier to succeed by starting with a monolith that you then break up. That advice does seem to be ignored by people who want a microservice architecture because it looks good on their CV, or because they think it will magically solve a bunch of hard problems they don't know how to solve.
Re:Microservices by bunderbunder on Thursday September 15, 2016 @10:05PM (#12511430)
I believe it.

The best place to place a module boundary - and the best format for communication across that boundary - is rarely completely transparent from the outset. With a monolith it's relatively easy (if not actually easy) to fiddle with those details until you get them right. With a service it can be very difficult to iterate on this stuff, so unless you're very confident you'll get it right on the first try, it's best to get a bit of experience in the problem domain first.

Re:Microservices by matwood on Thursday September 15, 2016 @10:45PM (#12511528)
I think microservices can work well, but also agree that it's easier to start with a monolith. It's hard to go out and create perfect microservices. In my experience they emerge from the problem much like how an amoeba gets big and breaks off at natural points.
Re:Microservices by johns on Thursday September 15, 2016 @04:49PM (#12509702)
We were also built from the ground up with microservices and had the exact opposite experience. Faster shipping (more value to end users), more predictability (APIs designed/behaved similarly across functions despite polyglot tech), much less coordination overhead (deployed dozens of times per day with a < 10 dev team, pre-release backends well in advance of the user-facing parts), etc. We had to invest a lot in infrastructure, but that was worth it for many other reasons as well. Dozens of repos is annoying, but not for a technical reason (a lot of SaaS like Bugsnag and GitHub used to charge by project).

The biggest downside is it makes shipping an on-prem version nearly impossible. The infrastructure and the software are so inextricably linked that it is not portable in the least bit.

Re:Microservices by dragonne on Thursday September 15, 2016 @05:29PM (#12509967)
We ship a microservices-based product on-premises. You can do it, but it's a heck of a lot of work. Plus you don't get any of the benefits microservices might bring in a CD scenario: you can't do CD over an airgap.
Re:Microservices by parasubvert on Friday September 16, 2016 @07:54PM (#12518261)
One of the ways we managed to get a microservices system on prem (vSphere or Openstack) is to configure it with a system that can handle the whole provision/build/configure/deploy as a single unit: http://bosh.io .. though the learning curve was steep.
Re:Microservices by ukoki on Saturday September 17, 2016 @05:20PM (#12522515)
BOSH has a famously steep learning curve: http://i.imgur.com/4UpbgJm.png
Re:Microservices by twic on Saturday September 17, 2016 @05:49AM (#12519870)
What was the system? Was this at or involving Pivotal? If not, this would be the first non-Pivotal use of BOSH I've heard of, which would be very exciting!
Re:Microservices by wstrange on Thursday September 15, 2016 @09:33PM (#12511317)
I think this is where Kubernetes has potential.

You can bundle up those complex dependencies into deployment manifests, or use helm.

It's like a SAAS in a box

Re:Microservices by romanovcode on Friday September 16, 2016 @03:57AM (#12512544)
Tell me about it. Exactly same situation here. You forgot the fact that they're paying 1k+ for AWS for all these services where if it was a normal application it would've cost around 100 bucks.
Re:Microservices by XorNot on Friday September 16, 2016 @06:20AM (#12512972)
If you're doing this then you don't know what you're doing infrastructure wise anyway.
Re:Microservices by ryan-allen on Friday September 16, 2016 @01:03AM (#12511956)
The app I'm working on is an ASP.NET MVC monolith, and it's fantastic.

Yeah it's not new fun tooling, but boy does it feel good to ship features without it being a total pain in the arse.

Also C# is pretty nice.

Re:Microservices by romanovcode on Friday September 16, 2016 @03:58AM (#12512550)
Well if you migrate to .NET Core (MVC) aka MVC6 it will be new fun tooling.
Re:Microservices by technion on Friday September 16, 2016 @06:16AM (#12512958)
I suppose there's a difference between the "from the ground up micro-architecture" and "using a micro service or two" that should really differentiate the various "should we use microservices?" discussions.

Several sites I'm aware of have an Facebook-style chat service, which is basically an off the shelf node app on its own. This makes far more sense than trying to build such a thing into their legacy app. It also perfectly describes a very useful micro service, in a very different environment to yours.

Re:Microservices by TheHydroImpulse on Thursday September 15, 2016 @11:01PM (#12511560)
> dozens of repos

ha. I wish I had this many repos. We have 1000+ git repos. To be fair, a ton are open sourced and there are reasons why it's done this way, but still.

Re:Microservices by joneholland on Thursday September 15, 2016 @11:46PM (#12511681)
Sounds like your company built a distributed monolith when they thought they were building microservices.
Re:Microservices by kwonstant on Friday September 16, 2016 @09:07AM (#12513685)
Similar situation here. Architect's desire: exposing usage and load metrics to autoscale the services.

Reality: Everything runs on two EC2 instances, regardless of load.

Re:Microservices by txutxu on Thursday September 15, 2016 @04:13PM (#12509445)
I see microservices as responsibility deduplication in a organization-traversal-wide.

De-duplication is a very old concept (differentiates good "sysadmins" from bad ones, since the 90's, and good programmers from bad ones).

Thinking organization-traversal-wide is what is hard for some persons.

Currently working at consulting in a big corp... you get to this problem:

Resource: name FooBar, type int (organization view point)

    app1 name: FooBar  type: int
    app2 name: foo_bar type: int32
    app3 name: Foobar  type: Meta::Foo::Bar
    app4 name: foobar  type: string
    app5 name: fooBar  type: int64
... etc until app 35 and script 192679

Microservices, thinking transversely, solve that. See AWS, GoogleCloud, Azure, etc "resource names" (ARNs, etc), for an example of a simple and great microservice.

Note also, that microservices experts (and I'm not one of those) recommend a monolithic and transactional core architecture, for microservices infrastructure.

Re:Microservices by ceslami on Thursday September 15, 2016 @07:50PM (#12510840)
> Note also, that microservices experts (and I'm not one of those) recommend a monolithic and transactional core architecture, for microservices infrastructure.

This is a pithy encapsulation of something I've been thinking a lot about recently: bud off a microservice from your transactional core if it is higher leverage to do so. Any good readings you've found on this perspective?

An example that comes to mind is: I might write my core application in Ruby on Rails, but need to perform a specialized, CPU-intensive function (PDF generation). I can delegate that to a microservice, invert a CPU-bound problem into an I/O bound one (from the perspective of the Rails core), and get the job done with less hardware.

Re:Microservices by aikah on Thursday September 15, 2016 @05:40PM (#12510054)
> I see microservices as responsibility deduplication in a organization-traversal-wide.

AKA SOA. Why call it microservice ?

Re:Microservices by cmdkeen on Friday September 16, 2016 @04:46AM (#12512685)
The Newman book is worth a read - I'm going through it at the moment and a lot is applicable to SOA as well. Microservices is partially a re-branding exercise to take the massive space SOA covers and talk about a more specific definition.

The main thing is the size of the services, the clue being in the name. Also there's a clearer emphasis on the services being more business related concepts, SOA can often described in more techy service splits rather than business concepts.

Re:Microservices by xorcist on Thursday September 15, 2016 @06:52PM (#12510532)
In many ways it's just like micro kernels again.

If micro services are the bee's knees, why are you writing them in Eclipse or Emacs? Wouldn't interconnected processes make up a "better" environment? An why are you deploying on something as monolithic as Linux? Shouldn't you out-compete all of these obviously inferior solutions, as there are probably more money in that than whatever web app you are currently building?

Re:Microservices by jsmith0295 on Thursday September 15, 2016 @08:09PM (#12510962)
That's one thing I've always thought when people claimed microservices followed "the UNIX philosophy". UNIX doesn't even follow that philosophy, it's a monolith! Yet it's also a modular system, which is possible without being either a microkernel or microservices.
Re:Microservices by jamesblonde on Friday September 16, 2016 @04:56AM (#12512720)
Yes. For me, shared state in the Linux kernel is like a shared database between microservices. It makes life way easier, is faster, but you need to be careful you don't introduce subtle bugs.
Re:Microservices by mej10 on Friday September 16, 2016 @08:38AM (#12513559)
The kernel is only one piece of a *NIX system. The userland tools are (mostly) a good example of small focused applications that can be combined in interesting ways.
Re:Microservices by jsmith0295 on Friday September 16, 2016 @10:34AM (#12514267)
Yeah, that is definitely true. I was looking at it as effectively being a monolith that existed to facilitate that, but that does only apply to the kernel.
Re:Microservices by aikah on Thursday September 15, 2016 @05:38PM (#12510035)
The problem with Micro-service is the notion of Micro. Services shouldn't be micro or macro but the right size. "Monolithic app" isn't a bad word, unfortunately some influential people tried hard to make it sound like it was.
Re:Microservices by eric_h on Thursday September 15, 2016 @04:06PM (#12509376)
Indeed. It's easier to change a monolithic stack while you're still discovering the actual architectural requirements of the particular problem you're solving.

As you get a better understanding of how you need to handle things, where the performance bottlenecks are, etc., you can start breaking out pieces that would benefit from being isolated.

It's extremely unlikely that in the short term (first year(s)) of the application being used that the engineering would benefit from a micro services architecture.

Re:Microservices by collyw on Thursday September 15, 2016 @04:48PM (#12509693)
That sounds like the obvious approach. Premature optimization and all that.
Re:Microservices by _pmf_ on Friday September 16, 2016 @02:28AM (#12512242)
> It just so happens that the portion of the community is the one most looked up to by the rest of the community

It certainly is the most vocal.