of deploying new Are you scared of deploying new features? features? • Are you afraid of deploying changes? Are you afraid of deploying changes? • Does it take months to review changes Does it take months to review changes and confirm for deployment? and confirm for deployment? • Does it take ages to be comfortable about Does it take ages to be comfortable about new features to deploy? new features to deploy? • Is it a headache to recover broken service Is it a headache to recover broken service and your service is totally down? and your service is totally down?
your service How often it happens that your service was not accessible for hours because of was not accessible for hours because of simple hardware fault? simple hardware fault? • ٌٌWhat about software issues? What about software issues? • Did someone say storages? Did someone say storages? • Revenue loss? Revenue loss? • Unhappy management? Unhappy management?
Are you scalable? • Vertically? :-P Vertically? :-P • How often do you suspend your services How often do you suspend your services to upgrade your hardware? to upgrade your hardware? • What happens if in one week your service What happens if in one week your service grows by 50% or 100% or even more? grows by 50% or 100% or even more? • Expanding to new Geo-Location is a Expanding to new Geo-Location is a headache, isn't it? headache, isn't it?
any or all of the above is your problem or you can not tolerate them, problem or you can not tolerate them, Then I tell you what is missing in your Then I tell you what is missing in your infrastructure! infrastructure!
only one node with Deploy changes to only one node with least clients least clients • Deploy new feature to one node with Deploy new feature to one node with least clients and more testers. least clients and more testers. • Changes or Features that cause problem Changes or Features that cause problem to the system only affect very small group to the system only affect very small group of clients. of clients.
down? Take your Service on one server is down? Take your time to fix it while other handling the time to fix it while other handling the requests for you. requests for you. • Low on disks? Don't worry! You'll have Low on disks? Don't worry! You'll have enough time to buy an additional disk :) enough time to buy an additional disk :) • Hardware faults? It's OK! You'll have Hardware faults? It's OK! You'll have enough time to find and fix the problem. enough time to find and fix the problem.
service capacities Expanding or shrinking service capacities is no longer an issue. is no longer an issue. • If tomorrow requests grows by 100% If tomorrow requests grows by 100% simple double your servers and all would simple double your servers and all would be fine. be fine. • No more costumers at off pick time? Why No more costumers at off pick time? Why wasting money, shrink your service by wasting money, shrink your service by turning off extra servers. turning off extra servers.
boynux
kentarofujii
maf_0521
elmodev09
oomatomo
you
chanyou0311
seafay
takahiromatsui
bash0c7
nari_ex
fullkaiten
jukishiya
stephaniewalter
jonoalderson
skipperchong
katarinadahlin
chikuwait
skoyamalab
.jpg){kind=avatar}
cargoodrich
mlcsv
pwiseman
reverentgeek
sergeychernyshev
rabernat
