Whenever a new technology trend takes off, a funny problem arises the problem of prefixes. I have covered prefixes for different Kubernetes distributions in an internal document a few months back and I will make it public soon. Today I am going to have a funny take on different flavors of As-a-Service offerings and is they are enough to make a periodic table-like structure.
Shameless plug: We are revolutionizing the As-a-Service landscape with Roost.ai which provides an Environments-as-a-Service platform for modern applications. Do check it out.
Periodic table containers over 100 elements so that may be slight overkill for now. Let's start with 26 alphabets as prefixes and let's see how far we can go:
AaaS = Analytics as a Service
BaaS = Backend as a Service
CaaS = Containers as a Service | Content as a Service
DaaS | DBass = Data as a Service | Database as a Service
EaaS = Environments as a Service | roost.ai
FaaS = Functions as a Service | AWS Lambda | Azure Functions
GaaS = Games as a Service
HaaS = Hardware as a Service
IaaS = Infrastructure as a Service
JaaS = Vacant spot (there are some vendor acronyms which I am ignoring)
KaaS = Knowledge as a Service
LaaS = Logging as a Service | Location as a Service
MaaS = Monitoring as a Service
NaaS = Network as a Service
OaaS = Operations as a Service
PaaS =Platform as a Service
QaaS | QAaas = Quality as a Service
RaaS = Recovery as a Service
SaaS = Software as a Service
TaaS = Testing as a Service
UaaS | UCass = Unified Communications as a Service
VaaS = Video as a Service
WaaS = Vacant spot (there are some vendor acronyms which I am ignoring)
XaaS = Everything as a Service
YaaS = Vacant spot (there are some vendor acronyms which I am ignoring)
ZaaS = Vacant spot (there are some vendor acronyms which I am ignoring)