Web services and Microservices: The effect on vendor lock-in

22
Web Services and Microservices: The effect on vendor lock-in Adrian Cockcroft @adrianco Technology Fellow - Battery Ventures August 2015 See www.battery.com for a list of portfolio investments

Transcript of Web services and Microservices: The effect on vendor lock-in

Page 1: Web services and Microservices: The effect on vendor lock-in

Web Services and Microservices: The effect on vendor lock-in

Adrian Cockcroft @adriancoTechnology Fellow - Battery Ventures

August 2015

See www.battery.com for a list of portfolio investments

Page 2: Web services and Microservices: The effect on vendor lock-in

Who here doesn’t like lock-in?

Page 3: Web services and Microservices: The effect on vendor lock-in

Most IT Ops people will try to avoid lock-in

Page 4: Web services and Microservices: The effect on vendor lock-in

Most product developers will pick the

best of breed option

Page 5: Web services and Microservices: The effect on vendor lock-in

DevOps to the rescue!

Page 6: Web services and Microservices: The effect on vendor lock-in

https://www.youtube.com/watch?v=7g3uqSzWVZs

Page 7: Web services and Microservices: The effect on vendor lock-in

"End the practice of awarding business on the basis of a price tag. Instead, minimize total cost. Move toward a single supplier for any one item, on a long-term relationship of loyalty and trust.”

W. Edwards Deming - 4th Point

Page 8: Web services and Microservices: The effect on vendor lock-in

"End the practice of awarding business on the basis of a price tag. Instead, minimize total cost. Move toward a single supplier for any one item, on a long-term relationship of loyalty and trust.”

How did we end up here?

dysfunctional exploitation and abuse

Page 9: Web services and Microservices: The effect on vendor lock-in

Project vs. ProductLeads to lock-in Evolves to follow

best of breed

Page 10: Web services and Microservices: The effect on vendor lock-in

Evolution Technology Refresh Move to open Source

On-prem -> as a Service

Page 11: Web services and Microservices: The effect on vendor lock-in

Best of breed is now OSS and as a Service

Less inherent lock-in

Page 12: Web services and Microservices: The effect on vendor lock-in

What kinds of lock-in are there?

Page 13: Web services and Microservices: The effect on vendor lock-in

Business lock-inHardest to escape…

Page 14: Web services and Microservices: The effect on vendor lock-in

e.g. compliance with laws that exclude alternatives based on jurisdiction or certification

Contractual lock-ine.g. partnership or investment deal with one vendor prevents using alternatives

Financial lock-ine.g. budget spent in advance on long term

deal with a vendor

Legal lock-in

Page 15: Web services and Microservices: The effect on vendor lock-in

Technology lock-inPossible to escape given time and work…

Page 16: Web services and Microservices: The effect on vendor lock-in

e.g. quorum based availability (C*, Riak) needs three zones/datacenters per region

Topology lock-in

Proximity lock-ine.g. chatty clients don’t work unless they

are co-located with their server

Implementatione.g. interface is the same but behavior is different

Page 17: Web services and Microservices: The effect on vendor lock-in

Soft lock-inRelatively easy to escape…

Page 18: Web services and Microservices: The effect on vendor lock-in

Data gravity lock-ine.g. lots of data to move or duplicate

Query syntax lock-ine.g. SQL variants for different databases

Interface lock-ine.g. different APIs that get the same result,

easy to hide behind an abstraction layer

Web service lock-inInterface lock-in, but remote access

unlocks ability to migrate applications

Page 19: Web services and Microservices: The effect on vendor lock-in

Cloud native microservices

Page 20: Web services and Microservices: The effect on vendor lock-in

AWS Aurora

Example for discussion

Page 21: Web services and Microservices: The effect on vendor lock-in

Q&AAdrian Cockcroft @adrianco

http://slideshare.com/adriancockcrofthttp://github.com/adrianco/spigo

Technology Fellow - Battery VenturesAugust 2015

See www.battery.com for a list of portfolio investments

Page 22: Web services and Microservices: The effect on vendor lock-in

Security

Visit http://www.battery.com/our-companies/ for a full list of all portfolio companies in which all Battery Funds have invested.

Palo Alto Networks

Enterprise IT

Operations & Management

Big DataCompute

Networking

Storage