Viaje a la nube,estrategias, modelos operativos, aspectos a tener en cuenta... y tendencias

1. Víctor M. Fernández Gómez
@vfernandezg
In the journey to cloud:
Strategies, possible operating models
(and aspects to be considered…)

2. Agenda:
- Systems evolution (and applications too)
- Different adoption strategies
- Possible operating models
- Aspects to be considered

3. Agenda:
- Systems evolution (and applications too)
- Different adoption strategies
- Possible operating models
- Aspects to be considered

4. Systems evolution (and applications too)
Mainframe
Web
Cloud
IaaS
PaaS
SaaS
¿Serverless?
Scalability + Self service + Pay per use

5. Responsibility model

6. Agenda:
- Systems evolution (and applications too)
- Different adoption strategies
- Possible operating models
- Aspects to be considered

7. AWS 6rs Strategy
https://aws.amazon.com/es/blogs/enterprise-strategy/6-strategies-for-migrating-applications-to-the-cloud/

8. AWS 6rs Strategy
Description of each option
- Rehosting— Otherwise known as “lift-and-shift.”
- Replatforming— I sometimes call this “lift-tinker-and-shift.”
- Repurchasing— Moving to a different product.
- Refactoring / Re-architecting— Re-imagining how the application is architected and
developed, typically using cloud-native features.
- Retire— Get rid of.
- Retain— Usually this means “revisit” or do nothing (for now).

9. Strategy seen by Gartner
Weighting effort benefit

10. Maturity levels
From “Cloud-Ready” to “Cloud-Native”…

11. AWS 6rs Strategy and maturity Levels
Cloud-Ready & Cloud-Native
Migration
Transformation

12. AWS 6rs Strategy and maturity Levels
Cloud-Ready & Cloud-Native
Migration
Transformation

13. Migration versus Transformation
Cloud-Ready & Cloud-Native considerations
Migration
Transformation
- Less number of changes in the systems with some adjustment in its
technological stack
- It relies (mostly) on the migration of virtual machines, together with
the integration with new cloud provider services (eg storage,
databases ...)
- Some new cloud provider services are deployed (eg
Interconnection, DNS, etc.)
- Important changes in the technological stack of systems
(infrastructure, platform and application)
- Compatible as standard with the infrastructure services of the cloud
provider, using its own capabilities (via API) of self-scaling,
automation, etc.
- Take advantage of the cloud platform managed platform services by
default (eg databases, integration services, etc.)

14. Migration versus Transformation
Cloud-Ready solutions and services
- Azure Site Recovery
- Azure Migrate
* Latest version
compatible with App
Service
- Azure Database Migration
- Azure Databox
- Etc.
- Google Velostrata
- Etc.
- AWS Server Migration
- AWS Cloudendure
- AWS Database Migration
- AWS S3 Transfer
Acceleration
- AWS Snowball
- AWS Snowmobile
- Etc.
Migration

15. Agenda:
- Systems evolution (and applications too)
- Different adoption strategies
- Possible operating models
- Aspects to be considered

16. Cloud operating Models
https://medium.com/swlh/cloud-operating-model-413cd5bb4147 (Autor: Sreenivasa Setty)

17. Cloud operating Models
https://medium.com/swlh/cloud-operating-model-413cd5bb4147 (Autor: Sreenivasa Setty)
Sustained Optimized Increased

18. Cloud operating Models
Sustain, optimize and grow considerations
Sustained
Optimized
Increased
- Traditional IT Organization Model
- Starting point of the “Migration” option
- Compatible with Rehosting strategies
- Model oriented to improvement and optimization
- Intermediate point between "Migration" and "Transformation“
- Compatible with Replatforming and Repurchasing strategies
- Quick growth oriented model
- Destination point of the “Transformation” option
- Compatible with Refactoring and Re-architecting strategies
All three models do not imply maturity levels. It is possible to observe these
three operating models present in most organizations.

19. AWS 6Rs Strategy and cloud operating Models
Sustain, optimize and grow

20. AWS 6Rs Strategy and cloud operating Models
Sustain, optimize and grow
Sustained
Optimized
Increased

21. Agenda:
- Systems evolution (and applications too)
- Different adoption strategies
- Possible operating models
- Aspects to be considered

22. Relevant aspects to keep in mind
Systems qualities and their guarantees
Cloud-Ready
• New interconnection services
• Latency reduction and data localization principle
• Coexistence with on premise systems
• Integration with master databases (operations)
• New security models (CSA, etc.)
• Identity governance etc.
• New regulatory framework (GDPR, etc.)
• New solutions, tools and secure services
• Especially identification, prevention, detection and response
• New LAN and WAN networks
• New automation solutions
• New monitoring solutions
• New storage services
• New backup / restore services
• New disaster recovery solutions
• New governance tools

23. Relevant aspects to keep in mind
Systems qualities and their guarantees
Cloud-Native
• New way to develop applications
• New segmented data models
• Oriented to microservices
• New way to package applications (and their dependencies)
• New way to deploy applications (and their services)
• New way of publishing application services
• New way to integrate application services
• New form of application service governance
• New solutions and application runtime services
• PaaS/CaaS platforms
• Native PaaS (incl. Runtimes, Databases, Datalakes, etc.)
• New observability solutions for the application execution (and their services)
• New traffic management, security and telemetry solutions for the application execution
(and their services)
• E.g. Service Mesh

24. “New” Hybrid model
And multicloud trend too
Cloud-Hybrid
Beyond the CMP (Cloud Management Platform) type solutions, most of the main CSPs
(Cloud Service Providers) are launching their own hybrid solutions in the last year that allow
cloud services to be brought closer to organizations and also they are compatible with
multicloud models:
Hybridization

25. Possible use cases
https://architectelevator.com/cloud/hybrid-cloud/ (Autor: Gregor Hohpe)
Hybridization

26. Víctor M. Fernández Gómez
@vfernandezg
¡ Thank you very much !