Cloud Computing
- Posted by optimalsolutions
- On December 25, 2016
- 0 Comments
Cloud Computing
OSI is a SDB leader and Amazon Consulting partner in the adoption of CI/CD deployments using open source technologies to drive Fedcivil and DoD workload migrations to cloud platforms. Focused on outcomes and driving DevSecOps based deployments, OSI has helped its commercial and federal customers drive innovation within their organizations. Our modernization approach (AI/ML based automation) is a key differentiator for us in our solutioning and scaling methodology and we bring the best talent to solve customer challenges.
Cloud Strategy
Re-host (Referred to as a “lift and shift.”): Move applications without changes. In large-scale, legacy migrations, organizations are looking to move quickly to meet business objectives. Applications are easier to optimize/re-architect once they’re already running in the cloud. Partly because your organization will have developed the skills to do so, and partly because the hard part — migrating the application, data, and traffic — has already been done.
Re-platform (Referred to as “lift, tinker, and shift.”) : Make a few cloud optimizations to achieve a tangible benefit. You will not change the core architecture of the application. For example, reduce the amount of time you spend managing database instances by migrating to a database-as-a-service platform. OSI brings proficiency using Amazon Relational Database Service (Amazon RDS), or other fully managed platform like AWS Elastic Beanstalk.
Re-factor / Re-architect: Re-imagine how the application is architected and developed using cloud-native features. This is driven by a strong business need to add features, scale, or performance that would otherwise be difficult to achieve in the application’s existing environment. OSI has experience to migrate from a monolithic architecture to a service-oriented (or server-less) architecture to boost agility or improve business continuity.
Re-purchase: Move from perpetual licenses to a software-as-a-service model.
Retire: Remove applications that are no longer needed. Once you have completed discovery for your environment, ask who owns each application. As much as 10%-20% of an enterprise IT portfolio is no longer useful and can be turned off.
Retain (Referred to as re-visit.): Keep applications that are critical for the business but that require major refactoring before they can be migrated. You can revisit all applications that fall in this category at a later point in time.