If you've been to any tech conferences or read any tech blogs in the past few years, you've

almost certainly heard the term containers, as well as a load of other confusing words

with a few too many syllables.

So historically, when containers were first started to be used, they were aimed at very stateless applications.

That's Chris Ibbotson.

I'm Chris Ivittson. I'm a chief technologist focused on the financial services industry,

in particular helping organisations understand how to leverage hybrid cloud technologies such as containers, Kubernetes, etc.

Today, we're going to be exploring containers from the ground up to explain the what,

the where, the how and the why of the small but mighty innovation.

We're going to be asking what are containers and how on earth do they work?

How can organisations get to grips with this quickly evolving innovation?

And why are incumbent banks and Pokemon Go a lot more similar than we ever anticipated?

All this and much more.

I'm Michael Bird and this is Technology Untangled.

Containerization as a topic tends to be a bit overwhelming. There is a huge amount of information out there about something that is, at least on the face of it, pretty tiny.

Containers in essence are a way to package applications to abstract them away from the environment they actually run.

By decoupling the application in this manner, you can kind of deploy them easily and consistently,

no matter where you're looking to run them.

So whether that's in a data center on the public cloud or even on a developer's laptop as they're

developing.

It can get quite convoluted, but for me, it is that simple. It's just

your piece of software and whatever dependencies that software needs to actually run.

...