2. Dev Problem
10:15 Install OS
11:20 Configure the system
12:05 Coffee Break
13:05 Configure security
14:15 Configure Web server
15:40 Configure Database
16:20 Couple of sandwiches
16:50 Configure firewall
17:20 Deploy application
17:45 Call wife and apologize for the late return
18:00 Identify library dependencies
20:30 Upgrade packages
22:15 Fix dependencies
23:50 Couple cans of Red Bull
01:30 Run!!!
02:05 The end of the working day
12. Complex apps are composed of small, independent processes
Microservices = Decomposition
13. Monolithic Application
‒ Very often we redeploy everything
‒ Mutual dependencies slow down
development
‒ Long QA cycle leads to less often updates
‒ High risk of failure or VM overload
‒ Very hard to scale
Modular and polyglot
Deployed and updated independently
Much easier to scale and maintain
Flexibility is the key
Microservices
Microservices vs. Monolithic
One monolithicVM
Multiple Containers
17. Application level
load balancing, session replication, clustering
Hardware level
software defined storage, live migration, smart
distribution
High Availability
38. Jelastic Multi-Cloud Orchestrator
Your Bridge to Cloud Union
17 DCs in
8 Countries
11 DCs and 23 AZs in
8 Countries
3 DCs and 10 AZs in
3 Countries
25 DCs in
11 Countries
36 DCs in
25 Countries
39. Hybrid and Multi-Cloud
Features
Smooth migration across multiple cloud providers
Live migration between Azure or AWS regions
High availability across multiple clouds
Disaster recovery of workloads from AWS to Azure
Automatic scaling for load spikes and temporary burst
Unification of DevOps workloads deployment
Benefits
Autonomy – no vendor lock-in
Hybridity – better performance with lower costs
HA and DR – reduced downtime risk