1. MIGRATING APPLICATIONS
TO THE CLOUD WITH
CUMULOGIC PLATFORM
Multi- SQL &
Cache
Language NoSQL
aaS
PaaS DbaaS
Elastic Message Coming
Load Queue soon
Balancer aaS
2. Migrating Applications to the Cloud
Tools, Technologies and Processes
• Migrate virtualized environments
• Package applications and replicate environments in the cloud
• Pros: Quick, easy, no code changes required
• Cons: Short term solution, no application transformation, limited ROI
• Introspection and assembly tools
• Introspect existing environments and creates a “blueprint”
• Pros: Quick, easy, no code changes required
• Cons: Proprietary and vendor-specific tools, limited solution
• Platform-as-a-Service such as CumuLogic PaaS
• Abstracts applications from underlying infrastructure
• Pros: Portal applications, eliminates single vendor lock-in, better performance, high ROI
• Cons: Minor code changes required
3. Migrating Applications to the Cloud
Dependencies
• Infrastructure dependencies
• Container-specific dependencies
• Hardcoded JDBC strings jdbc:oracle:thin:@<host>:<port>:SID
• Connections to messaging, cache, SMTP, LDAP servers
• Applications tied to fixed IP addresses or hostnames
• Local file system dependencies
• Writing files to a local disk or directory structure
• Authentication and authorization systems
• LDAP / Active Directory / Identity Manager
• Application dependencies
• Applications or modules must be available at certain port numbers
4. Migrating Applications to the Cloud with CumuLogic PaaS
Eliminate Dependencies
• Infrastructure dependencies
• Only use JNDI names for connections. Specify them in cumulogic-app.xml
• Source environment variables for hostnames and IP addresses for database,
messaging, LDAP, cache or other servers
• Local file system dependencies
• Request a persistence volume when deploying apps
• Authentication and authorization systems
• Use available authentication system in the cloud
• Application dependencies
• Deploy all modules together using cumulogic-app.xml