Building SaaS Enabled Applications

1,701 views

Published on

Ezhil, Director CSS Corp Labs presented at Silicon India event on Building SaaS Enabled Applications

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,701
On SlideShare
0
From Embeds
0
Number of Embeds
13
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • Open Web Application Security Project
  • Building SaaS Enabled Applications

    1. 1. “Building SaaS Enabled Applications”Ezhil Arasan Babaraj Director of R&D LabsCSS Corp
    2. 2. INDUSTRY TRENDS
    3. 3. IT Evolution 2012 2000 1990 Social Networking Web 1.0 Smart Devices1980 ASP Web 2.0 & 3.0 Web Services SOA© 2012 CSS Corp 3
    4. 4. Network Evolution 2012 2000 19901980 4© 2012 CSS Corp
    5. 5. Application Evolution 2012 2000 1995 19901980© 2012 CSS Corp 5
    6. 6. Application Delivery Model 2012 2000 19901980© 2012 CSS Corp 6
    7. 7. =INTRODUCTION TO SaaS
    8. 8. Definition“Software that is owned, delivered andmanaged remotely by one or more providers.The provider delivers an application based on asingle set of common code and datadefinitions, which is consumed in a one-to-many model by all contracted customersanytime on a pay-for-use basis, or as asubscription based on use metrics” 8
    9. 9. Characteristics© 2012 CSS Corp 9
    10. 10. Myths© 2012 CSS Corp 10
    11. 11. Taxonomy Sourced from open cloud manifesto 11
    12. 12. =SaaS ESSENTIALS
    13. 13. Types of SaaS Single Tenant Multi Tenant • Quick Time • Consumes to Market more time • Usage of • Usage of IaaS is must PaaS • Automation • Scales by Required itself • Higher Opex • Lower Opex© 2012 CSS Corp 13
    14. 14. Key NFRs • Shared Infrastructure – Multi Tenant • Data Privacy/Protection • Automated Billing & Invoice • Robust Messaging • Customizable – User Interface, Business Logic, Data Model, payment Gateway & Messages • Auditing • Open Authentication with Classic Model Support© 2012 CSS Corp 14
    15. 15. Conceptual Architecture 15
    16. 16. Case Study • A CRM for Support Business – Subscription Management – Ticketing System – Consumer Products Packager – Payment Gateway Support • Single Tenant • Single WEB, APP & DB • Built on .NET & SQL Server© 2012 CSS Corp 16
    17. 17. CRM - Single Tenant Architecture© 2012 CSS Corp 17
    18. 18. CRM - Multi Tenant Architecture© 2012 CSS Corp 18
    19. 19. Key Techniques to Consider • Data escrow • Database sharding • Soft/Hard Deletion© 2012 CSS Corp 19
    20. 20. Technologies to consider • Oauth (http://oauth.net/) • Hibernate Shards (http://www.hibernate.org/subprojects/shards.html) • Athena Framework (http://athenasource.org/java/) • Heroku (http://heroku.com) • Microsoft Azure (http://www.windowsazure.com/en-us/)© 2012 CSS Corp 20
    21. 21. Best Practices • Use a PaaS platform • Implement Database Sharding • Use Soft Deletion where ever possible • Always be stateless • Built with Security at all the layers • Ensure OWASP rules are satisfied© 2012 CSS Corp 21
    22. 22. Recommendations • Start experimenting with a PaaS platform • Unlearn and Learn • Ensure Proper Tenant Partitioning across the system • Public PaaS - Verify the SLA’s carefully • Understand the Limitations • Choose the right Database Deployment Model© 2012 CSS Corp 22
    23. 23. References • http://labs.csscorp.com • http://athenasource.org • http://www.opencloudmanifesto.org/Cloud_Computing_Use_ Cases_Whitepaper-2_0.pdf • http://aws.amazon.com/solutions/case-studies/css-corp/ • http://cloudofinnovation.com/2011/07/01/big-data-and- hadoop-a-cloud-use-case/ • http://ezhil.sys-con.com/ • http://megam.info/ • http://www.microsoft.com/windowsazure/ • http://simplicable.com/new/6-reasons-you-need-a-SaaS- data-escrow-service • http://horicky.blogspot.in/2010/01/roadmap-to-saas.html© 2012 CSS Corp 23
    24. 24. Thank You! © 2012 CSS Corp – Copyright Notice: This presentation contains proprietary information of CSS Corp. No part of this presentation may be reproduced, stored, copied, or transmitted in any form or by means of electronic, mechanical, photocopying or otherwise, without the express consent of CSS Corp. This presentation is for a specific intended audience circulation only and not meant for external distribution. Information is classified into 4 levels: Confidential: This is specifically restricted to the Senior Management and specific professional advisers. Restricted: This is restricted to Senior Management (PA’s and assistants an also access subject to respective reporting head’s approval). Private: This covers all information assets that have value but which do not need to fall within either of the other categories. Public: This is information which can be released outside the Organization.© 2010 CSS Corp 24

    ×