The document discusses SaaS-ification and using AWS for software as a service models. It describes single tenant and multi tenant SaaS options. For single tenant SaaS, each customer gets their own isolated environment including dedicated compute and database resources. For multi tenant SaaS, resources are shared across customers requiring scalable architecture and automation for onboarding. Example architectures are provided for each approach using various AWS services.

1. AWS
Use Cases
Samuel Vijaykumar M

2. SaaS-ification

3. SaaS-ification
Whats that?

4. SaaS-ification
Motivation
Deployment Automation
Harness Elasticity
Multi Region Support
Many Service Options
Pay as you Run

5. SaaS-ification
Models
Single Tenant SaaS
Multi Tenant SaaS

6. SaaS-ification
Single Tenant SaaS
Compute Not Shared
What is it?
Databases Not Shared
Close to Fork lifting
Scaling a possibility
Offboard easily

7. SaaS-ification
Single Tenant SaaS
Build base AMI
How to do it?
Automate Deployments
Automate Graceful Destructions
Automate Monitoring
Automate Graceful failovers

8. SaaS-ification
Single Tenant SaaS
Architecture?
Cloud Provisioning Portal Mountable
(EC2) Persistent
Storage
(EBS)
Resource
Compute Resources
Repository Database
(EC2 Fabric)
(S3) Fabric
(RDS)
Central Log Store(Flume/Scribe)
CloudWatch
(EC2 Cluster)
Monitoring Server
(EC2)

9. SaaS-ification
Multi Tenant SaaS
Compute is Shared
What is it?
Databases are Shared(schema)
Not your traditional model
Scaling a must
Onboard easily

10. SaaS-ification
Multi Tenant SaaS
Design a Scalable Architecture
How to do it?
Good use of AWS services
Design a DR Strategy
Monitor all Services
Automate quick onboarding

11. SaaS-ification
Multi Tenant SaaS
Load Balancer CDN
Architecture?
(Elasctic Load Balancing) (CloudFront)
Object
Web Servers
AutoScale Store
(EC2)
(S3)
Cache Layer DNS Management Mountable
(ElastiCache) (Route53) Persistent
Storage
(EBS)
Database With Replication
Database With Replication
(RDS)
(RDS) NoSQL
(SimpleDB)
Index Cluster Service Monitoring
(EC2 Cluster) (EC2)

12. Digital Marketing

13. Digital Marketing
Whats that?

14. Digital Marketing
Motivation
Content Delivery Network
Bulk mailing
AutoScale for Spikes
Many Service Options
Pay as you Run

15. Digital Marketing
What Challenges?
Manage Multiple Brands
Heterogeneous Environments
Frequent Updates
Unpredictable Spikes
Handle Multiple media types

16. Digital Marketing
How to do it?
Capacity Planning
Effective monitoring
Log data analysis
Identify standard configurations
Automated scripts for deployments

17. Digital Marketing
Architecture
Cloud Provisioning Portal CDN
(EC2) (CloudFront)
Mountable
Stardardized AMI Store Persistent
Storage
Resource (EBS)
Repository
(S3) Campaign Database
AutoScale
Servers(EC2) Fabric
(RDS)
Central Log Store(Flume/Scribe)
(EC2 Cluster) CloudWatch
Campaign Data Analysis Bulk Mailing
(EC2 Cluster) (SES)
Monitoring Server
(EC2)

18. Email Archival

19. Email Archival
Whats that?

20. Email Archival
Motivation
Availability of a large storage
Spawn servers quickly
Secure data in transit
Map Reduce for Data Analysis

21. Email Archival
What Challenges?
Data at rest security
Indexing Large Volumes
Ease of access
Monitoring cluster nodes

22. Email Archival
How to do it?
Choose an Indexing Service
Use effective Data Encryption
Manage Encryption Keys
Plan for Failures

23. Email Archival
Architecture
Archive View Portal Authentication Server
(EC2) (EC2)
Data Encryption Server Archive Store
(EC2) (S3)
Distributed Index Cluster(Lucandra)
Distributed Index Cluster(Lucandra)
Distributed(EC2) Cluster(Lucandra)
Index
(EC2)
(EC2)
Database Server Persistent Index Store
(RDS) (EBS Volumes)
Services Monitoring Server
(EC2)

24. Thank you!?!
Scan now!!!