Many legacy applications are built out as a monolith, but cloud infrastructure, especially AWS, is built around the assumption that different pieces of an application can be separated out. This talk is a look at how we updated a legacy monolith to be able to take advantage of cloud infrastructure.
Keanan Koppenhaver is CTO at Alpha Particle, a digital consultancy that helps plan and execute digital projects that serve anywhere from a few users a month to a few hundred thousand. He enjoys helping clients build out their developer teams and setting them up for success. He believes that more technology isn't always the answer, but when it is, it's important to get it right.
@WouterDeKort
Duly noted. The abstract was limited to 300 characters, which made this one a bit tough. But here was what was included in the expanded description:
Cloud technology can give applications greater flexibility, but it can be more complicated to maintain, especially if you’re working with a legacy, monolithic application. However, with a few tweaks, even older codebases can be converted to be able to run in the cloud.
This is a look at how we moved a WordPress installation serving nearly 1 million hits per day into the cloud on AWS and dealt with challenges such as managing uploads, sticky sessions across load balanced servers, implementing memcached and managing the transition with minimal downtime.