Can I use Containers
Needs imagery, checklist, diagrams, sectioning
Choosing to containerize your app as a modernization pattern is a holistic process. We want to make sure containers are the right solution. This involves identifying: what we want to do, what we need, our effort level and what is available.
Wanting and deciding to modernize your app is not the same as can. You might want to modernize your app, and subsequently find it’s not possible. Necessary hardware might be out of circulation. What if you can’t find someone who can read that particular code? Within the next decade many on premise solutions of the past will become obsolete, and we will not be able to find coders with the skill set to fix your hardware.
Made with Visme
Sometimes older applications have outdated technologies, and or licensing agreements that limit it’s re-architecture and still you need to move it to the cloud to take advantage of some of the cloud capabilities, like scaling. What about your applications usership. How many people need your app? If you have very limited users for your app it might cost less to retire the app and replace it with a SAAS product. We want to check if there is a SAAS out there that can meet your needs.
Containers make it easy to package your entire application and move it to the cloud without needing to make any code changes. If you want to keep your app, there isn’t a prebuilt solution and you don’t have the resources, or reasons to rebuild it. This would be a good solution.
| What Containers can do for you | What Containers cannot do |
|---|---|
| can move your app to the cloud | does not pay your technical debt |
| give you portability | does not fix an underlying poor infrastructure |
| allow your app to use cloud elasticity scalability | doesn’t make app cloud native |
| allows your developers to innovate | if your app is broken it will still be broken |
| achieve greater efficiency | liscence dependencies - might prevent use |
| allow you to attract innovative developers | hardward dependencies - might prevent use |
| more efficient development technologies | technology dependencies - some tech is too old |
| can still sit on prem | tech managed by gui excel, ms axis |
| reduce tools your dev teams need |