Category: SaaS

The AWS SaaS Competency helps customers find top APN Consulting Partners with deep specialization and experience in designing and building SaaS solutions on AWS. Our Competency Partners follow AWS best practices for designing and building SaaS solutions through their professional services practices. To qualify for the AWS Competency designation, organizations have undergone rigorous technical validation by AWS Partner Solutions Architects and demonstrated proven customer success.

For SaaS companies responsible for data collection and processing on behalf of multiple organizations, privacy is a core requirement and a competitive differentiator. Knowing the answers to these questions is critical to meeting data management, security, and privacy requirements. WireWheel is a group of privacy experts, data scientists, and business leaders that have set out to help companies meet this challenge.

F5 Cloud Services is a set of enterprise-grade application delivery and security SaaS services that are optimized for cloud-native applications and microservice environments. The AWS SaaS Factory team sat down with Craig Kitterman, Sr. Director of Product Management at F5 Cloud Services, and Yaniv Shemesh, Chief Architect at F5 Cloud Services, to learn about what they’re launching and how it benefits customers.

With the introduction of Amazon Aurora Serverless (currently in preview), SaaS providers are now equipped with a model to bring the scale and cost efficiency of serverless computing directly to storage partitioning models of SaaS solutions. We take a closer look at how Aurora Serverless works and how it influences your approach to storage partitioning in SaaS environments. The goal here is to highlight the implications of the serverless storage model, identifying key areas that will be of particular interest to SaaS developers.

We are excited to introduce AWS SaaS Factory to help accelerate and guide the adoption of a Software-as-a-Service (SaaS) delivery model on AWS. The program offers a comprehensive set of business and technical best practices, as well as engagement opportunities that empower and support ISVs building SaaS offerings on AWS. The focus is on helping customers and APN Partners at all stages of the SaaS on AWS journey.

As SaaS organizations grow and begin to extend their global reach, they must consider how their larger geographic footprint will shape and influence the architecture of their systems. Operations, deployment, agility, security, and scale all can be impacted by the move to a geographically distributed SaaS model. The more complexity that is added to a system’s operational and deployment profile, the more challenging it becomes to maintain the agility goals that are often associated SaaS delivery models.

Networking is often viewed as a foundational element of a system’s architecture. The reality is there are plenty of scenarios where the networking footprint of a SaaS application can influence the functionality, extensibility, and management profile of your SaaS environment. While there are plenty of creative ways developers leverage AWS networking constructs to refine SaaS solutions, the introduction of AWS PrivateLink adds new opportunities in the SaaS networking landscape.

Identity is a fundamental design decision that software as a service (SaaS) architects must consider when developing a multi-tenant system. Developers who are building SaaS applications must be able to identify a user, the tenant associated with the user, the user’s permissions, and the relationship a tenant has with the provider, such as usage plan or tier. In this post for SaaS Technology Partners, I will explore how to architect a multi-tenant system and identify tenant context and role using Amazon Cognito.

SaaS solutions often present architects with a diverse mix of scaling and optimization requirements. With SaaS, your application’s architecture must accommodate a continually shifting landscape of customers and load profiles. The number of customers in the system and their usage patterns can change dramatically on a daily—or even hourly—basis. These dynamics make it challenging for SaaS architects to identify a model that can efficiently anticipate and respond to these variations.

In traditional single-tenant environments, calculating and aggregating infrastructure costs is a pretty straightforward exercise. Typically, each application or customer has its own collection of dedicated resources and tallying the costs is simply a matter of categorizing and summing those costs. However, in multi-tenant SaaS environments, this becomes a much more challenging problem. With SaaS, tenants often share some or all of a system’s infrastructure resources.