My Constraints Aren’t Your Constraints: A Lesson to Learn with Containers

After digging through the details of the hottest new technology, have you immediately thought “we need to start using this tomorrow!”? This a common pitfall I see often. Buzzwords get tossed around so frequently that you feel that you are doing things the wrong way.

 

Let’s take Netflix as an example. Netflix is ubiquitously known as the company that made micro-service architecture popular (or better yet, Adrian Cockroft). Netflix’s goal of bringing streaming content consisted of lot of different services but needed an adjunct way of increasing the speed at which services can be updated. Amazon’s Jeff Besos is quoted with the API mandate saying “All teams will henceforth expose their data and functionality through service interfaces.” This was done to allow any BU, from marketing to e-commerce, to communicate and collect data over these APIs and make that data externally available. However, take a step back and think about what these companies are doing. Yes, they are pinnacles of modern technology advancement and software application architecture, but one is a streaming movie service and the other is a shopping cart (2002 is when this mandate came out). If my bank has externally facing APIs that only use basic auth, I’m finding a new bank. That’s a constraint.

 

What about your business? Most enterprises have roots so deep it is difficult, if not impossible, to lift and shift.

Originally Posted on http://www.kendrickcoleman.com/


This post was originally published on this site
Comments are closed.