A presenentation describing what is cloud with a restaurant analogy and life with cloud services.

1. Recipes For the Cloud
Bekir Dogan & Roy Buyuksimkesyan
07.03.2012 Kartaca

2. Outline
• Who Are We?
• What is Cloud?
• Why is it depicted as cloud?
• Restaurant Analogy
• What Are The Key Features of Cloud
• Some Tidbits About Security
• Why You Should Not Move to The Cloud
• A Life Without Cloud Services
• Why Are They Cloud Services?
07.03.2012 Kartaca

3. Before All!
Don’t be afraid of the outline,
we got a break :)
07.03.2012 Kartaca

4. Who Are We?
• Mobile Services
• E-Commerce
• End User Portals
• Consultancy
• Open Source
Software
• Parkyeri
07.03.2012 Kartaca

5. What is Cloud?
Cloud computing is the delivery of computing as a service rather than a product,
whereby shared resources, software, and information are provided to computers
and other devices as a utility (like the electricity grid) over a network (typically the
Internet).
http://en.wikipedia.org/wiki/Cloud_computing
07.03.2012 Kartaca

6. What is Cloud?
• A new kind of SaaS platform
• For end users
• Shared resources
• Reallocate these resources easily
• No knowledge on where or how
• Allows you to focus on your strengths
07.03.2012 Kartaca

7. Why is it depicted as Cloud
The term "cloud" is used as a metaphor for the Internet, based on the cloud
drawing used in the past to represent the telephone network, and later to
depict the Internet in computer network diagrams as an abstraction of the
underlying infrastructure it represents
http://en.wikipedia.org/wiki/Cloud_computing
07.03.2012 Kartaca

8. Why is it depicted as Cloud
• Borrowed from Telephony
• Distinctive Responsibilities
• You don’t know what happens inside
• Looks and sounds better than black
box :)
07.03.2012 Kartaca

9. Restaurant Analogy
Did you get what cloud is?
07.03.2012 Kartaca

10. Restaurant Analogy
• You have your own kitchen and place
• You cook for 3 persons
• Yourself
• Your roommate
• Your roommate’s girlfriend/boyfriend
07.03.2012 Kartaca

11. Restaurant Analogy
• You should spent time for:
• Deciding what to do?
• Selecting ingredients
• Cooking them
• Preparing the table
• Eating it
• Dishwashing
• Desserts?
07.03.2012 Kartaca

12. Restaurant Analogy
• You should pay for:
• Ingredients
• Gas
• Heating (Dishwashing)
• Water (Dishwashing)
07.03.2012 Kartaca

13. Restaurant Analogy
I hated cooking already...
07.03.2012 Kartaca

14. Restaurant Analogy
Consider you are throwing a party!
07.03.2012 Kartaca

15. Restaurant Analogy
• The time you will spend on the previous
tasks will be exponentially increased
• Money too
• You gotta invite these people,...
• Don’t forget the drinks(!) and snacks,...
• But that’s a party, right...
07.03.2012 Kartaca

16. Restaurant Analogy
What if no one comes?
What will happen then?
07.03.2012 Kartaca

17. Restaurant Analogy
Consider you are going to a restaurant.
07.03.2012 Kartaca

18. Restaurant Analogy
• You should spent time for:
• Dressing (?!)
• Choosing where to go
• Choosing what to eat
• Choosing what to drink
• Considering if the dessert will be OK
• Calculating calories (ladies only)
07.03.2012 Kartaca

19. Restaurant Analogy
• You should pay for:
• Things you have ordered
07.03.2012 Kartaca

20. Restaurant Analogy
I liked that,... A lot...
And I will spent similar time and money for 100
people
07.03.2012 Kartaca

21. Restaurant Analogy
Cloud is very similar to going a restaurant.
07.03.2012 Kartaca

22. Restaurant Analogy
• Shared kitchen/storage
• Shared waiters/service providers
• Pay what you order/use
• Focus on the food/product
07.03.2012 Kartaca

23. Key Features
• Empowerment of End users
• You select from the menu and they bring it to
you
• Agility to change your infrastructure
• Order as much you want for breakfast or dinner
• API Accessibility
• Take Away, Order home, go there...
07.03.2012 Kartaca

24. Key Features (Contd.)
• Accessibility and Location Independence
• Order from anywhere to home or office
• Cost Reduction
• Pay what you eat, spend less time
• Reliability
• You know that you will be “fed”
07.03.2012 Kartaca

25. Key Features (Contd.)
• Scalability
• Be it 1 or 100,it will be handled
• Easy Maintenance
• Don’t worry about dishwashing
• Security
• No poison, no cheating
07.03.2012 Kartaca

26. About Security
• Software is buggy
• Trust issues between user and provider
• We all cracked (still?) software
• How security is measured
07.03.2012 Kartaca

27. About Security (Contd.)
What if Sony had moved to the cloud?
07.03.2012 Kartaca

28. Don’t Move!
You should reconsider, moving to the cloud
07.03.2012 Kartaca

29. Don’t Move!
• If you
• Have bought your own hardware
• Are Making your own administration
• Are scaling on your own
• Are deploying automatically
07.03.2012 Kartaca

30. Don’t Move!
• If you don’t want to
• Migrate existing systems
• Be limited to provider’s features
07.03.2012 Kartaca

31. Don’t Move!
• If you have
• Already optimized systems
• mature policies
• have sufficient personnel
• solved too many complex problems
07.03.2012 Kartaca

32. Don’t Move!
• And also consider:
• Provider problems affects you
• Many customized products
• Contracts with old customers
• Analyzing your actual resource needs
• What will happen if you get attacked
07.03.2012 Kartaca

33. Don’t Move!
No, you don’t pay less for moving.
It’s way more expensive
07.03.2012 Kartaca

34. A Life Without Cloud
• Heroku is an application server provider
• Allows you to manage server resources
• Deploy easily.
07.03.2012 Kartaca

35. A Life Without Cloud
Life Before Heroku
07.03.2012 Kartaca

36. A Life Without Cloud
• Write your web application
• Buy servers
• Build a room for them
• Ethernet cables, power cables, coolers,...
07.03.2012 Kartaca

37. A Life Without Cloud
• Create your network
• Firewalls for security
• Internet Connection and Bandwith
• LDAP for central user authentication
07.03.2012 Kartaca

38. A Life Without Cloud
• Install OS to servers
• Make them work like a cluster
• Install monitoring tools
• Buy UPS and connect it to the servers
• Install backup tools for disaster recovery
07.03.2012 Kartaca

39. A Life Without Cloud
Finally, somethings about application itself
07.03.2012 Kartaca

40. A Life Without Cloud
• Install Application dependencies
• Install Database server
• Domain name, static IP, DNS
• Deploy the application
07.03.2012 Kartaca

41. A Life Without Cloud
Life After Heroku
07.03.2012 Kartaca

42. A Life Without Cloud
• Write your web application
• Register and Configure your Heroku
Account
• Install Heroku Deployment Tools To
ease management
• Git Push (Commit) to Deploy
07.03.2012 Kartaca

43. A Life Without Cloud
• Start improving your application
• Add/remove resources on your fancy
• Spend time with your girlfriend
• Go to vacation
07.03.2012 Kartaca

44. A Life Without Cloud
Live a good life...
07.03.2012 Kartaca

45. Cloud Services
Why and How some cloud services are cloud?
07.03.2012 Kartaca

46. Cloud Services
• Spotify
• Accessibility
• Reliability
• Cost Reduction
• Easy Maintenance
• Empowerment
07.03.2012 Kartaca

47. Cloud Services
• Heroku
• Empowerment
• Agility
• Accessibility
• Cost Reduction
• Scalability
• Easy Maintenance
• Reliability
• Security
07.03.2012 Kartaca

48. Cloud Services
• Windows Azure
• Empowerment
• Agility
• Accessibility
• Cost Reduction
• Scalability
• Easy Maintenance
• Reliability
• Security
07.03.2012 Kartaca

49. Cloud Services
• DropBox
• Empowerment
• API Accessibility
• Accessibility
• Easy Maintenance
• Reliability
• Security
07.03.2012 Kartaca

50. Cloud Services
• Amazon
• Empowerment
• Agility
• API Accessibility
• Accessibility
• Cost Reduction
• Scalability
• Easy Maintenance
• Reliability
• Security
07.03.2012 Kartaca

51. Thanks
Bekir Dogan
You have questions, Roy Buyuksimkesyan
right?
bekir.dogan@kartaca.com
roy.buyuksimkesyan@kartaca.
com
07.03.2012 Kartaca