Logo
ScienceStack
Table of Contents
Fetching ...
Sign In

Pricing-driven Development and Operation of SaaS : Challenges and Opportunities

Alejandro García-Fernández, José Antonio Parejo, Antonio Ruiz-Cortés

TL;DR

The implications of a Pricing-driven Development and Operation approach of SaaS systems are explored, highlighting the delicate balance between business-driven decision-making and technical implementation challenges and shedding light on how pricing plans can shape software features and deployment.

Abstract

As the Software as a Service (SaaS) paradigm continues to reshape the software industry, a nuanced understanding of its operational dynamics becomes increasingly crucial. This paper delves into the intricate relationship between pricing strategies and software development within the SaaS model. Using PetClinic as a case study, we explore the implications of a Pricing-driven Development and Operation approach of SaaS systems, highlighting the delicate balance between business-driven decision-making and technical implementation challenges, shedding light on how pricing plans can shape software features and deployment. Our discussion aims to provide strategic insights for the community to navigate the complexities of this integrated approach, fostering a better alignment between business models and technological capabilities for effective cloud-based services.

Pricing-driven Development and Operation of SaaS : Challenges and Opportunities

TL;DR

The implications of a Pricing-driven Development and Operation approach of SaaS systems are explored, highlighting the delicate balance between business-driven decision-making and technical implementation challenges and shedding light on how pricing plans can shape software features and deployment.

Abstract

As the Software as a Service (SaaS) paradigm continues to reshape the software industry, a nuanced understanding of its operational dynamics becomes increasingly crucial. This paper delves into the intricate relationship between pricing strategies and software development within the SaaS model. Using PetClinic as a case study, we explore the implications of a Pricing-driven Development and Operation approach of SaaS systems, highlighting the delicate balance between business-driven decision-making and technical implementation challenges, shedding light on how pricing plans can shape software features and deployment. Our discussion aims to provide strategic insights for the community to navigate the complexities of this integrated approach, fostering a better alignment between business models and technological capabilities for effective cloud-based services.
Paper Structure (16 sections, 5 figures)

This paper contains 16 sections, 5 figures.

Table of Contents

  1. Introduction
  2. Background and related work
  3. Pricing plans.
  4. Feature toggling.
  5. Limitations of Traditional Approaches
  6. Challenges of Pricing-driven DevOp of SaaS
  7. Challenge 1: Pricing-driven feature toggling
  8. Challenge 2: Stateful and dynamic pricing-drive feature toggling
  9. Challenge 3: Secure, Unalterable, and efficient transference of subscription status.
  10. Challenge 4: Monitoring and enforcement of pricing plans usage constraints and guarantees (including QoS-based or SLA-related ones)
  11. Opportunities of Pricing-driven DevOp of SaaS
  12. Opportunity 1: Automated pricing-driven feature toggling
  13. Opportunity 2: An actual common language between business decision-makers and developers
  14. Opportunity 3: Improved alignment of deployment infrastructure and its usage based on subscription data
  15. Conclusions
  16. ...and 1 more sections

Figures (5)

  • Figure 1: A potential pricing for Petclinic with 3 plans, 8 features and two add-ons.
  • Figure 2: Feature point implementation inside a SaaS codebase
  • Figure 3: Manual effort required to modifying every affected toggle point versus a centralised pricing-driven toggle router
  • Figure 4: Retrieving data from toggle context and pricing on each toggle point (left) versus using a router for fetching the data needed to all evaluations once (right)
  • Figure 5: Insecure transmission of feature toggling status through Internet