Pretty good benefits/problem list, plus commentary on the “autonomy” angle.
When you can pay the sprinkler repair guy by using your finger to sign an iPad, things are looking up. Maybe it means we’ll have lots of microservices wrapped around government services, who knows. Also, we cover the strategy of choosing boring technologies, MongoDB, and The EMC Federation.
SPONSOR: Take our awesome, multi-cloud PaaS for a test-ride. Get two free months of Pivotal Web Services. Whether you want to deploy on-premises, in a dedicated public cloud, or just keep using our PaaS, Pivotal Cloud Foundry has everything you need for doing cloud-native applications. Go to cote.io/pivotal for the sign-up code!
- If you like video, see this episodes’ video recording.
- IBM’s all about Mac laptops – What about Lenovo?
- IBM Mobile Innovation Lab Examples.
- Software is awesome – Jobber.
- Whatever happened to the API Economy?
- Choose Boring Technology – “Adding technology is easy, living with it is hard.” – “Don’t chose tech because of testimonials on Hacker News. Hacker News is kind of like Fox News and not just because it’s dominated by libertarians.”
- What’s up with MongoDB?
- Will EMC spin-in VMware? – Not everyone’s familiar with the EMC Federation, I’m not familiar with anything like it in the industry. EMC, VMware, RSA, Pivotal, VCE
BONUS LINKS! Not covered in podcast
- Brandon: (Once again…) Wool
- Matt: Girl Talk videos one and two.
- Coté: Leading the Transformation, Applying Agile and DevOps Principals at Scale – good overview so far of what management at larger companies can do to introduce Agile and DevOps.
“For those not familiar with the concept, microservices is essentially a software architectural design pattern. The fundamental premise of microservices is that value can be unlocked through decomposing large, monolithic legacy applications into a set of small independent, composable services that each can be accessed via RESTful APIs.”
Nice talk from James Lewis on doing a microservices approach to solving a banking system problem.
“But microservices want to bring you into tomorrow,” says Winterberg. “Microservices add a bit to the category concept, defining a service over all application layers, including the UI. So people already doing SOA may gain a kind of new freedom by adopting microservice ideas.” That freedom includes technology independence and an alternative to aging technologies, because individual services within an application can be gradually swapped out for those based on more-modern technologies, without having to replace the entire application. “Classic SOA is more platform driven, so microservices offer more choices in all dimensions,” says Winterberg.
The picture that emerges is not of microservices as an alternative to SOA, but rather as a way to restore flexibility that may have been lost in SOAs that became too rigid and monolithic.
Microservices is a modern take on software architecture, in which complex applications are composed of small, independent processes communicating with each other using APIs. These services are small, highly decoupled and focus on doing a small task. The rise of Docker, the proliferation of third party developer tools and the increasing reliance on the cloud all play into the growth of microservices.