About the Author
Luke Patterson

Luke Patterson

Notes From My Swarm to Kubernetes Migration

Luke Patterson Architecture, Development Technologies, Kubernetes Leave a Comment

In this post, I’ll discuss how I’m currently working to migrate a suite of apps from Docker Swarm to Kubernetes. The client chose this migration to align with more contemporary standards of container deployment and gain a more comprehensive feature set. Also, some products that they recently purchased were best supported as a Kube package. So you have a fuller …

VS Code’s Development Container: A Stepping Stone To IaC

Luke Patterson AWS, Cloud, Development Technologies, DevOps, Tutorial Leave a Comment

In this post, l explain how we used Visual Studio Code’s Development Container feature as a stepping stone in our long-term effort to achieve Collaborative Infrastructure as Code. This one step in the process gave a versioned, repeatable working environment and allowed us time to determine the next steps in the effort to achieve IaC.

Gaining Docker Image Size Efficiencies By Separating Application Layers

Luke Patterson Development Technologies, Docker, Java, Spring Boot Leave a Comment

Problem

I was pushing a new Docker image tag for each application code commit, and the admins of the private registry were getting annoyed at how much space I was using.

Solution Summary

Yes, I know there are strategies to clean up old tags but I first wanted to reduce the impact of the tags I was pushing. With the right layering strategy, I knew I could reduce the net registry size increase of consecutive tag pushes.

I wanted to only push what had actually changed in the application. In addition to reducing the impact on the registry, having smaller tag deltas could possibly speed up rolling deployments since nodes could potentially have less to download.

Shrinkwrap before (or after) it’s too late!

Luke Patterson Development Technologies, Docker, Programming 2 Comments

Attention: The following article was published over 9 years ago, and the information provided may be aged or outdated. Please keep that in mind as you read the post.This happened to me… Twas the night before beta launch… I installed a new node module for a last minute feature and everything went haywire when the change was deployed. I reverted …