Software-as-a-service: Difference between revisions

Software-as-a-service (view source)

Revision as of 14:34, 17 January 2022

106 bytes added , 17 January 2022

no edit summary

Amwelladmin

Bureaucrats, Interface administrators, Administrators

81,841

edits

@@ Line 13: / Line 13: @@
 ===“SaaS” is short for “software ''development'' as a service”===
-“Software as a service” (latterly, “SaaS”) entered the lexicon some time in the 1980s, but really took off as a term of vogueness in the mid 2000s<ref>[https://books.google.com/ngrams/graph?content=SaaS%2C+software+as+a+service&year_start=1975&year_end=2019&corpus=26&smoothing= Let me Google that for you]</ref> when it dawned on software providers that, since they were permanently connected to their customers via the internet, they could lock in revenue that comes from product updates without the messy business of marketing them persuading clients into subscription arrangements rather than one-off licences.
+“Software as a service” (latterly, “SaaS”) entered the lexicon some time in the 1980s, but really entered the vogue in the mid 2000s<ref>[https://books.google.com/ngrams/graph?content=SaaS%2C+software+as+a+service&year_start=1975&year_end=2019&corpus=26&smoothing= Let me Google that for you]</ref> when it dawned on software providers that, since they were permanently connected to their customers via the internet, they could lock in revenue that comes from product updates without the messy business of persuading existing clients to upgrade — involving as it does having a revised product that is materially ''better'' than the one they already have — into subscription arrangements rather than one-off licences.
 But for that quid, there was a quo: the annual subscription was typically smaller than an outright licence, and you did have to upgrade the software: patching, enhancing, and updating.