While most web facing, modern workloads are primarily running on Linux, 67% Linux vs. 33% Windows¹, many mission-critical business applications are still running on a Microsoft technology stack. Many of these Microsoft workloads are legacy, and, by nature closely coupled with corporate networks and aging hardware. So, one might ask the logical question of whether they can move their legacy Microsoft workloads to the AWS like their newer, cloud-ready, workloads.
The short answer is, yes. You have many choices to make along the migration journey but, yes, you can gain the same redundancy, automation, security, and even cost controls as you can with your cloud native applications. The first decision to make is which partner to work with. As self-serving as this advice sounds, the right partner can help you make the right decisions on day one to guide you away from any pitfalls that could have cascading effects.
Author: Nitheesh Poojary, Cloud Architect - Six Nines IT
Editors: Vinny Carpenter, Justin Alan Ryan
Introduction
When a user uses web pages in a given browser, a user session is created by the server and the session ID is managed internally during the web session of the user. For example, when a user viewed three pages and logs out, this is termed as one web session. The HTTP protocol is stateless, so the server and the browser should have a way of storing the identity of each user session.