Archive

The Dulin Report

Browsable archive from the WordPress export.

Results (27)

Strategic activity mapping for software architects May 25, 2025 On the role of Distinguished Engineer and CTO Mindset Apr 27, 2025 My giant follows me wherever I go Sep 20, 2024 The day I became an architect Sep 11, 2024 Form follows fiasco Mar 31, 2024 On Amazon Prime Video’s move to a monolith May 14, 2023 One size does not fit all: neither cloud nor on-prem Apr 10, 2023 Comparing AWS SQS, SNS, and Kinesis: A Technical Breakdown for Enterprise Developers Feb 11, 2023 Why you should question the “database per service” pattern Oct 5, 2022 Monolithic repository vs a monolith Aug 23, 2022 All developers should know UNIX Jun 30, 2022 There is no such thing as one grand unified full-stack programming language May 27, 2022 Most terrifying professional artifact May 14, 2022 Best practices for building a microservice architecture Apr 25, 2022 TypeScript is a productivity problem in and of itself Apr 20, 2022 Tools of the craft Dec 18, 2021 TDWI 2019: Architecting Modern Big Data API Ecosystems May 30, 2019 Which AWS messaging and queuing service to use? Jan 25, 2019 Let’s talk cloud neutrality Sep 17, 2018 What does a Chief Software Architect do? Jun 23, 2018 Singletons in TypeScript Jul 16, 2017 Online grocers have an additional burden to be reliable Jan 5, 2017 What can we learn from the last week's salesforce.com outage ? May 15, 2016 IT departments must transform in the face of the cloud revolution Nov 9, 2015 Top Ten Differences Between ActiveMQ and Amazon SQS Sep 5, 2015 What can Evernote Teach Us About Enterprise App Architecture Apr 2, 2015 Docker can fundamentally change how you think of server deployments Aug 26, 2014

Docker can fundamentally change how you think of server deployments

August 26, 2014

I got a chance to evaluate Docker over the past few days. This is a type of a toolkit that is going to fundamentally change how you think of application deployments, in the cloud or on-premises.

What Docker boils down to is this. Rather than deploying your application in a dedicated VM or hardware, and manually installing all the components you might need, you specify a descriptor file (Dockerfile). This Dockerfile describes everything your application needs, including operating system, additional packages, storage volumes, and the entry point.

Your application then runs in a light-weight run time that includes everything it needs. Because Docker is lighter weight than VM, and provides less isolation, you can run more Docker containers on a single host than you can VMs. It is a much more efficient use of resources than VMs. Furthermore, because your Docker container remains unchanged between development, qa and production environments you are assured that your application will behave the exact same way in all of your environments.

Docker reminds me of Solaris Containers. In fact, it is based on Linux containers, a very similar technology. The concept predates Solaris, even. For those of us who had to work with IBM MVS years ago Dockerfile format is strikingly similar to JCL. Docker has the potential to fundamentally change how we approach software architecture, and do to cross-platform server platforms what Java never could.