Containers, the biggest innovation in the shipping industry, have standardized dimensions so that they can be loaded and unloaded, stacked, transported efficiently over long distances, and transferred from one mode of transport to another. Taking a cue from this, think of a server as a ship and an application as a crate. A couple of decades ago, only one app could be deployed on one operating system meaning, a single crate on a single ship.
With enterprises and ISVs adopting containers and Kubernetes (k8s) to increase the agility and scalability of their applications, they would want more applications to be deployed on k8s. Applications can be a mix of stateful and stateless. Until recently, only stateless applications were supported by k8s. However, with the advent of persistent storage on k8s, stateful applications will be supported. In the pet Vs cattle analogy of service, you would want to treat the storage as cattle.
Gartner defines edge computing as solutions that facilitate data processing at or near the source of data generation. In this context edge computing is a key consideration while planning your digital business roadmap. Many scenarios like autonomous driving cars and industrial equipment monitoring systems have very low latency tolerance. Large volumes of data are collected and analyzed instantaneously to take action. Even a delay of milliseconds renders the data stale and useless.
As enterprises slowly get out of the shock and awe of the effects of COVID19 on it’s IT operations, they are and will start exploring how to reduce CapEx and OpEx. Most enterprises are not going to let go of existing cash especially if it is a capital expenditure. Any new hardware or software purchase or refresh is out of the window (including Windows licenses). At the same time, they will also start looking for ways to reduce OpEx. For e.g.
Containerizing your age-old legacy applications is the way forward! Yes, it’s true that the benefits attached to containerization are quite rewarding for enterprise apps in the long run. It is also true that not all applications should be containerized. Assuming your application is ready for containerization, you may want to analyze the approach taken to containerize apps, is it a manual or an automated process? Manual process is time-consuming and prone to errors.
Applications deployed years ago may have undergone changes over the years, and there are strong possibilities of the changes not being documented or recorded. All the undocumented changes can bite back as a security breach or get NCs (non-compliance) during an audit exercise. Also, if there is a drive to modernize applications, the true picture of the application may not be documented after interviewing the right people. These applications could be on-premise or on the cloud.
AWS EKS has been supporting Linux containers for a while. However, without Windows container support some of the hybrid applications were not supported end to end. In addition, with the version of 1.14 of Kubernetes, AWS introduced Windows container support and with this feature, you would be able to run Linux and Windows containers in the same Kubernetes cluster namespaces thus enabling your hybrid applications to work on Kubernetes.
While cloud adoption in general has been on the rise, the migration of business-critical legacy application workloads to the cloud has been relatively cautious. Apart from financial risk, the primary reason for this precaution is the inherent risk to business operations. Customers who venture into application refactoring have broadly two options...
