Lets SAASify that Desktop Application
0 likes207 views
The document discusses strategies to convert traditional desktop applications to Software as a Service (SaaS) models, outlining the differences between Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and SaaS. It highlights the advantages of using these cloud services, including scalability and reduced infrastructure concerns, as well as real-life challenges developers may face during the transition. The document also provides insights on utilizing Amazon Web Services (AWS) for effective deployment and scaling of applications.
Lets SAASify that Desktop Application
- 1. Lets SAAS-ify that Desktop Application Chirag Jog Clogeny 1
- 2. About me o Chirag Jog o Computer Science Passout, PICT o Currently CTO at Clogeny Technologies. o Working on some cutting-edge Products in Cloud Computing. o [email protected] 2
- 3. Agenda o Traditional Web Setup o Difference between IaaS, PaaS and SaaS o Different ways to SaaS’ify o Advantages of PaaS o Real life Scenario o Advantages of IaaS o Using IaaS to SaaS’ify o Using Amazon Web Services as an example for deployment o Improving Business Logic o Conclusion 3
- 4. Traditional Web 1.0 setup Source : http://onsaas.net/wp-content/uploads/2008/06/iaas-paas- saas.png 4
- 6. PaaS 6
- 7. SaaS 7
- 8. Different ways to ‘SaaS’ify SaaS SaaS SaaS Shared Platform As A Infrastructure Infrastructure Service As A Service Hosting companies AppEngine, Amazon’s AWS, and solutions. Force.com Rackspace 8
- 9. Different ways to ‘SaaS’ify SaaS SaaS SaaS Shared Platform As A Infrastructure Infrastructure Service As A Service Hosting companies AppEngine, Amazon’s AWS, and solutions. Force.com Rackspace 9
- 10. Advantages of PaaS o Developers can focus on development and innovation without worrying about the infrastructure. o No up-front investment in hardware and software means lower risk. o Developers only need a PC and an Internet connection to start building applications. o The PaaS provider manages upgrades, patches, and other routine system maintenance. o PaaS upgrades will not break the applications running on it. o Obvious Advantages of Cloud i.e scalability, reliability etc 10
- 11. Real Life!! o Application already developed in pre-Cloud days. o Developed for Desktop Environments . o Depend on specific libraries that PaaS solutions do not provide. o Using PaaS would require re-writing major chunks of code. o Problems with re-write: o Existing Code has been stabilized over months and years. o Extensive testing needs to be done. o Time to Market takes a drastic hit. o Specific library support might been missing. 11
- 12. Real Example of Application o Code written entirely in C/C++ Language. o Using math libraries for doing complex calculations. o Results generated in terms of Graphs and Charts. o Desire to have wider customer reach. o Want to hook up this application to a portal. 12
- 13. Different ways to ‘SaaS’ify SaaS SaaS SaaS Shared Platform As A Infrastructure Infrastructure Service As A Service Hosting companies AppEngine, Amazon’s AWS, and solutions. Force.com Rackspace 13
- 14. Advantages of IaaS o Well-tested environment available. o Directly deploy the existing application onto the Cloud Server with no modifications. o All required dependencies can be resolved easily by installing required libraries. o Minimal modifications to convert the existing solution to Client-Server model. o Easily provide a front-end from web portal or such. 14
- 15. Using IaaS to SaaS’ify the App o Scenario : Stand-alone Desktop Application o Steps involved are: o Convert stand-alone application to server- application model. o Introduce Cloud Element. o Add business logic via Cloud o Link Portal /outside world interface to this system. o Test!! 15
- 16. Client-Server Architecture LAMP Stack 16
- 17. Cloud Component Amazon EC2 Cloud Web Server Amazon Web Services: 1. Elastic Computing. 2. Simple Queue Service (SQS) 3. Simple Storage Service. (S3) 4. Automatic Scaling. (AS) 17
- 18. Using Amazon Web Services o Elastic Compute (EC2) o Simple Queue Service (SQS) o Simple Storage Service (S3) o Automatic Scaling (AS) 18
- 19. Amazon Simple Queue Service(SQS) o Distributed Queue System enabling web services applications to communicate. o Queue acts as an unlimited buffer – No Producer- Consumer Problem. o Multiple writers and readers o Variable message size o Unlimited queues and messages o Access control o Redundant infrastructure 19
- 20. Amazon Simple Queue Service(SQS) API o CreateQueue – Creates a queue with specific QueueName. o SendMessage – send message (PUSH) o ReceiveMessage – receive message from queue (PULL) o DeleteQueue – Delete a queue (All messages in the queue lost) 20
- 21. Amazon Simple Storage Service(S3) o Useful for file serving (multimedia, documents) reducing load on compute servers. o Storage for the internet. o Makes web-scale computing easier. o Data is stored in buckets. o Data is stored or retrieved using a key, value pair. o Simple REST/SOAP Apis to retrieve and store data. o Access Control. 21
- 22. Amazon Simple Storage Service(S3) basic APIs o PUT Bucket – Creates a new bucket o Creates sampleBucket.s3.amazonaws.com o GET Bucket – Lists information about bucket. o PUT object – put object into the bucket o GET object – retrieve object o DELETE object – Deletes the object o DELETE bucket – delete associated attributes or the buckets themselves 22
- 23. Web Server Simple Cloud Design Queue request Store result Blob in to Server using S3 SQS Queue response EC2 Server instance back to client runs the using SQS software/application 23
- 24. Improving Business Logic o Auto – scalability to load balance . o Multiple classes of users. o Top Class user does not have to wait. o Lower class users’ request is queued. o Extension : Multiple queues to service multiple classes 24
- 25. Amazon Automatic Scaling(AS) o Automatically add compute capacity when application usage rises and remove it when usage drops. o Predefined triggers and thresholds. o Triggers are based on parameters like bandwidth usage or CPU Utilization. o Triggers are based on data collected from Amazon’s CloudWatch Monitoring Tool. o Works across multiple Availability zones. 25
- 26. Amazon Automatic Scaling(AS) API o as-create-launch-config– Create a group of EC2 instances of which the application will run. o as-create-auto-scaling-group - This call sets the parameters that governs when and how to scale up and down an Auto Scaling group. o as-create-or-update-trigger – Create the triggers to indicate when to scale up or down. 26
- 27. Improving Business Logic Support Multiple Classes of Users. Use Amazon’s Automatic Scaling (AS) 27
- 28. Costs! o Cheapest EC2 Linux Instance - $0.085/hour o Amazon’s Auto scaling is free. Charges only for using Amazon’s CloudWatch. o Amazon ‘s SQS – o No charges for the first 100,000 Amazon SQS Requests. o $0.01 per 10,000 Amazon SQS Requests o Amazon’s S3 – o Storage Used: $0.15 per GB-Month of storage. o Network Data Transferred: $0.20 per GB of data transferred. 28
- 29. Reducing Vendor Tie-in o Reduce dependency on vendor specific services. o Replace SQS with Apache ActiveMQ o Replace CloudWatch with Hyperic o Implement your own Auto Scaling Logic. 29
- 30. Conclusion Effectively deploy your application without major modifications. Run the application is original environment itself. Add some more useful business logic to service different class of users. Obvious Advantages of Cloud Computing applicable Pay only for what you use. Scale up/down based on load Design to make system more robust 30
- 31. Questions and Comments 31