If you were going to build a brand new application today, your approach would probably be fundamentally different than five or ten years ago. And I do mean fundamentally, as in the fundaments of the architecture would be different. In the last ten years we have moved rapidly from traditional three-tier applications to 12-factor apps using microservices, and now things are shifting again to serverless. That’s all well and good for any business looking to build a new application, but what about organizations that have traditional applications? I’ve also heard them called legacy or heritage applications. These applications are deeply ingrained in the business and are often what is actually generating the bulk of a company’s revenue. The company cannot survive without these applications, and modernizing them will be costly and fraught with risk. Due to the inherent risk, most companies opt to either keep these applications running on-premises or move them as-is to the public cloud, aka life and shift. That’s the reality we’re living with today, but tomorrow is knocking on the door and promising hybrid cloud to fix all this. What’s the reality and what’s the hype? And what is the most likely journey for most companies?
The end of 2016 is here, and I think many of us are breathing a sigh of relief. The year has not been kind to some, and has been described as a “dumpster fire” by others. On the whole, I actually think that 2016 was a pretty decent year, or at least no worse than most previous years. But I am a bit biased since my second daughter was born in June, and she is awesome! That’ll tip the scales regardless of what else happened. Anyhow, I digress. The tech industry has seen a lot of change, with new technologies emerging and companies innovating at a rapid pace. I’d like to use this post to take a look at a few of those trends, and which ones I will be keeping an eye on in the coming year.