News for hackers. Stuff that matters.
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