Skip to main content

AWS re:Invent 2015: Designing for SaaS

Next-Generation Software Delivery Models on AWS

Software delivery has been evolving. Not too many years ago most software lived on-premise. Then came the web-hosted app, and then robust Cloud solutions like those provided by various combinations of AWS services.
At this week’s re:Invent, Sajee Mathew – Solutions Architect at AWS – talked about the best approach to build SaaS (Software as a Solution) solutions. There are basically three possible approaches:

  • Isolated customer stacks, which offer independent resources for each customer.
  • Containerization on shared platforms which use EC2 Container Service and Docker to provide “slices” of AWS.
  • Pure SaaS shared architecture by means of on-demand resources.

The isolated customer stacks model means that, for every new customer, you simply replicate the stack. It makes billing and provisioning quite simple, but it comes with a catch: thousands of customers will translate into way too many stacks.
Containerization requires fewer resources, as a considerable part of your infrastructure can be shared among all your customers. Assuming you won’t face too many coding changes, it’s a good solution for new apps.
Pure SaaS shared architecture is definitely the best approach for a brand new app. Despite the need for all parts of the application to be multi-tenant-aware, you can benefit from economies of scale. Deployments serving new customers are automatically built on autoscaling single infrastructures.
Designing for SaaS

SaaS architecture

As part of his presentation, Sajee defined each component of a pure SaaS shared architecture (along with AWS services built to deliver it):

  • SaaS Ordering: the entry point for purchasing access to SaaS apps, for the orchestration of which AWS Simple Workflow might be useful.
  • SaaS Provisioning: this component manages the fully automated deployment of resources and represents the cornerstone of elasticity and scalability. CloudFormation is a used to define the stack, while OpsWorks, Beanstalk, and ECS are used to deploy components.
  • Application Lifecycle Management: the biggest challenge in traditional architectures. Operations need to be transparent and must function with zero downtime as automation layers for continuous integration. CodePipeline, CodeCommit, and CodeDeploy are all powerful management tools.
  • SaaS Billing: this component aggregates per-customer metering and rate information. You can use DynamoDB to store bills and aggregated data, and EMR for processing usage info and generate bills.
  • SaaS Analytics: the aggregation point for all data sources in the development of a data warehouse. Analytics can provide useful analysis about app performance and usage that drive decisions.
  • SaaS Authentication and Authorization: a single store for all users data, third party SSO, and corporate directories. You could use IAM for policy-based access, KMS for key management, Cognito for mobile and web authentication, Directory Service, and RDS.
  • SaaS Monitoring: real-time monitoring and awareness of application health requires the highest scale and availability. There are plenty of off-the-shelf solutions, if you don’t feel like using Kinesis and CloudWatch.
  • SaaS Metering: this component gives your system the ability to understand and track usage and activity, and support audit requirements for billing. You might use Lambda to feed a metering queue on SQS.
SaaS Components - Analytics

SaaS best practices

Sajee also provided some best practices for building SaaS solutions:

  • Separate the platform from the program. Avoid tight coupling. Applications will change a lot over time, but core services should remain reusable so they can support a whole fleet of SaaS applications.
  • Optimize for cost and performance. Go for horizontal scalability at every level and create small parallel resource units that scale more efficiently. Also, use scalable services such as DynamoDB and Aurora.
  • Design for multi-multi-tenancy.
  • Know your data lifecycle. Value and usage change over time, you should therefore leverage efficient storage options.
  • Collect everything and learn from it. Reliably collect as many metrics as possible and store them durably. The goal is to know your customers in order to learn and profit through analytics.

Written by

Alex is a Software Engineer with a great passion for music and web technologies. He's experienced in web development and software design, with a particular focus on frontend and UX.

Related Posts

— November 28, 2018

Two New EC2 Instance Types Announced at AWS re:Invent 2018 – Monday Night Live

Let’s look at what benefits these two new EC2 instance types offer and how these two new instances could be of benefit to you. Both of the new instance types are built on the AWS Nitro System. The AWS Nitro System improves the performance of processing in virtualized environments by...

Read more
  • AWS
  • EC2
  • re:Invent 2018
— November 21, 2018

Google Cloud Certification: Preparation and Prerequisites

Google Cloud Platform (GCP) has evolved from being a niche player to a serious competitor to Amazon Web Services and Microsoft Azure. In 2018, research firm Gartner placed Google in the Leaders quadrant in its Magic Quadrant for Cloud Infrastructure as a Service for the first time. In t...

Read more
  • AWS
  • Azure
  • Google Cloud
Khash Nakhostin
— November 13, 2018

Understanding AWS VPC Egress Filtering Methods

Security in AWS is governed by a shared responsibility model where both vendor and subscriber have various operational responsibilities. AWS assumes responsibility for the underlying infrastructure, hardware, virtualization layer, facilities, and staff while the subscriber organization ...

Read more
  • Aviatrix
  • AWS
  • VPC
— November 10, 2018

S3 FTP: Build a Reliable and Inexpensive FTP Server Using Amazon’s S3

Is it possible to create an S3 FTP file backup/transfer solution, minimizing associated file storage and capacity planning administration headache?FTP (File Transfer Protocol) is a fast and convenient way to transfer large files over the Internet. You might, at some point, have conf...

Read more
  • Amazon S3
  • AWS
— October 18, 2018

Microservices Architecture: Advantages and Drawbacks

Microservices are a way of breaking large software projects into loosely coupled modules, which communicate with each other through simple Application Programming Interfaces (APIs).Microservices have become increasingly popular over the past few years. The modular architectural style,...

Read more
  • AWS
  • Microservices
— October 2, 2018

What Are Best Practices for Tagging AWS Resources?

There are many use cases for tags, but what are the best practices for tagging AWS resources? In order for your organization to effectively manage resources (and your monthly AWS bill), you need to implement and adopt a thoughtful tagging strategy that makes sense for your business. The...

Read more
  • AWS
  • cost optimization
— September 26, 2018

How to Optimize Amazon S3 Performance

Amazon S3 is the most common storage options for many organizations, being object storage it is used for a wide variety of data types, from the smallest objects to huge datasets. All in all, Amazon S3 is a great service to store a wide scope of data types in a highly available and resil...

Read more
  • Amazon S3
  • AWS
— September 18, 2018

How to Optimize Cloud Costs with Spot Instances: New on Cloud Academy

One of the main promises of cloud computing is access to nearly endless capacity. However, it doesn’t come cheap. With the introduction of Spot Instances for Amazon Web Services’ Elastic Compute Cloud (AWS EC2) in 2009, spot instances have been a way for major cloud providers to sell sp...

Read more
  • AWS
  • Azure
  • Google Cloud
— August 23, 2018

What are the Benefits of Machine Learning in the Cloud?

A Comparison of Machine Learning Services on AWS, Azure, and Google CloudArtificial intelligence and machine learning are steadily making their way into enterprise applications in areas such as customer support, fraud detection, and business intelligence. There is every reason to beli...

Read more
  • AWS
  • Azure
  • Google Cloud
  • Machine Learning
— August 17, 2018

How to Use AWS CLI

The AWS Command Line Interface (CLI) is for managing your AWS services from a terminal session on your own client, allowing you to control and configure multiple AWS services.So you’ve been using AWS for awhile and finally feel comfortable clicking your way through all the services....

Read more
  • AWS
Albert Qian
— August 9, 2018

AWS Summit Chicago: New AWS Features Announced

Thousands of cloud practitioners descended on Chicago’s McCormick Place West last week to hear the latest updates around Amazon Web Services (AWS). While a typical hot and humid summer made its presence known outside, attendees inside basked in the comfort of air conditioning to hone th...

Read more
  • AWS
  • AWS Summits
— August 8, 2018

From Monolith to Serverless – The Evolving Cloudscape of Compute

Containers can help fragment monoliths into logical, easier to use workloads. The AWS Summit New York was held on July 17 and Cloud Academy sponsored my trip to the event. As someone who covers enterprise cloud technologies and services, the recent Amazon Web Services event was an insig...

Read more
  • AWS
  • AWS Summits
  • Containers
  • DevOps
  • serverless