Everything I have done over the last 10+ years is embedded in these Linux services. There is way too much data embedded in my services-from learning Jiu-Jitsu to home projects to changing the differential in my 2005 Crossfire SRT 6. Now, you may be asking yourself, why don't you just move to Jira for ticketing, for your blogs, and some free service for your wiki? Well, I can't move for the same reasons most large enterprises businesses can't move. Now, let's dig into what I did specifically for my own services.įor my blogs, wiki, and ticketing system, rewriting and refactoring were completely out of the question. These skills will come naturally for Linux Systems Administrators and Architects. The vast majority of the software we use today was designed and written before Linux containers, so even when you write (or rewrite) software from scratch, you need the same skills. Also, here's a presentation I did covering the same topic: Containers for Grownups' Migrating Traditional and Existing Applications: Video and Slides.įor simplicity, I will briefly touch on the most essential parts of the above white paper and presentation. In fact, if you search for migrating to containers, the second article you'll find is one I wrote, delving into these three options and some techniques on how to analyze architecture, security, and performance: ( Best practices for migrating to containerized applications – 11 pages). Linux processes to containerized Linux processes – lift and shift, refactor, rewrite.Windows to Linux – lift and shift, refactor, rewrite.Virtual machines to cloud – mostly refactor, rewrite.Bare metal to virtual machines – mostly lift and shift.Unix to Linux – lift and shift, refactor, rewrite.Since the advent of operating systems and standardized programming languages, some permutation of the same three options has existed.

You had to rewrite your application from scratch for every different computer ( A Brief History in Code Portability). As an aside, before mainframes, there was no portability. To be clear, these are the same three options that people have had for many years. A quick look at five or ten of the results will lead you to the same three main options: If you search with Google, you will find pages and pages of blogs, white papers, and articles. These are only samples, but deep inspection of these containerized services should provide a foothold for your own work. You need senior Linux skills to containerize them well. These are very common Linux services, and they seem so deceptively simple at first glance. Here are the three services we are going to take a hard look at in this article: SERVICEĪpache, PHP, FastCGI Process Manager (FPM), MariaDB, WordPressĪpache, PHP, FastCGI Process Manager (FPM), MariaDB, Cron, MediaWikiĪpache, FastCGI, Perl, MariaDB, Postfix, Cron, Request Tracker The goal is to give you some solid, concise, and technical guidance. I hope it will help you move your own services into containers. I've finally done it, and I want to share my technical solution and break down my conscious design decisions. So don't feel bad if you are still staring, longingly, from afar, at other people's fancy containerized services, as I've only recently gotten over the hump myself. I've had hundreds or thousands of migration conversations with customers and community members, but I just couldn't find time to convert my personal Linux services. Sure, I've built tons of demos, done tons of experiments, and thought for hours and hours about how to migrate things. A practical introduction to container terminology.

Install xampp red hat linux