Skip to main content

Enterprise Architecture

Cloud Smart Proinciple​

Cloud smart is a long term, high-level strategy to drive cloud adoption and be smart about 5 key pillars

  • Operational Excellence
  • Security
  • Reliability
  • Performance Efficiency
  • Cost Optimization

Cloud Smart does not mean "Cloud Always"

Why do we move to the cloud?​

  • Cost?
  • Scalability
  • Redundancy
  • Cloud Native, take advantage from PAAS platform
  • Operational Efficiency (e.g Patching, Backup etc)

A cloud smart mindset is highly resource consious looks to preserve and leverage exisitng application code and supporting platform technologies that are already cost effectively working whenever and whereever possible.

Before any platform migrartion decicison is made, EnterpriseArchitect team carefully analyze the risk involved and lost access time of an application, testing time against potential benefits to be gained from re-platforming/migrating to cloud. If the former outweighs the latter, the decision to move is a questionable one.

Cloud Migration Rationale:​

Typical drivers for undertaking the effort of migrating an application to the cloud, which can also affect the migration strategy

  • User Agility and control
    • Today most of the application teams depend heavily on IT teams to get them required environment to develop, test and integrate workloads. It may take IT teams days or even weeks to make the environment available to teams
  • Scalability when needed
    • IT teams typically find it difficult to keep pace with the demands os sacle in their infrastructure, particularly when there is a sudden increase in demand for application load
  • Innovative trends such as bigdata
    • Trends like high performance computing, big data, complex event procesing, machine learning and mobile services are hard to configure.
  • Operational Cost
    • Increase running costs of your infrastructure that include the unit price of infrastructure, matching supply and demand, invest risk of new applications, markets, and building transparency into the IT operating model.

What are the benefits of Cloud Migration​

  • Increased agility and flexibility
    • Reduce Time(With in hours or even minutes) to provision/de-provision of environment which increases application teams ability to focus on the business need and deliver faster business results.
  • Ability to innovate faster
    • Try out new ideas, new approaches and experiments with little upfront commitment. provide the option of pay-as-you-go so organizations can test , develop, and experiement with these innovative technologies
  • Elastically Scalable
    • Easing of increasing resources demad levels, growing and shrinking as required
  • Reduction in costs
    • We only pay for the services we consume and once we stop using them there are no additional costs or termination fees and no long-term contracts or up-front commitments
  • Security
    • Provides end-to-end security and hrden cloud environemnt (includes data centers, hardware, software and network infrastructure etc) with industry recognized certificates, regulatory complaince and audit
  • Resilent to failure
    • Provides highly avavilable environment(Regions, Availability Zones, Edge locations etc) to operate business continuity normally
  • Ease of Automation
    • Provides the services to automate the repeatable processes for DevOps

Traditional IT Vs Cloud Models​

Cloud Models

The 6 R's : 6 Application Migration Strategies​

  1. Re-Host (lift & Shift): Move applications without changes
  2. Re-Platform(lift, tinker and shift): Make a few cloud optimizations to achieve a tangible benefit. You will not change the core architecture of the application
  3. Re-Factor/Re-Architect: Re-imagine how application architected and developed using cloud native features. This is driven by strong business need to add features, scale or performance that would otherwise be difficult to achieve in the application's existing environment.
  4. Re-Purchase: Move from perpetual licenses to a software-as-a-service model
  5. Retire: Remove application that are no longer needed. Once you completed discovery for your environment
  6. Retain: Keep applications that are critical for 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.