There are generally three recognized layers to any stack: IaaS, PaaS and SaaS.
There are glue pieces in between that facilitate interactions and/or try to smooth out implementation differences at layer that can accommodate this (IaaS and PaaS): Infrastructure as code, CNCF interfaces.
The SaaS layer is unique though because thats where a unique, end user consumable is provided. This layer needs to be multi-deployment capable. That is to say, a given generation of the offering must be capable of being deployed at multiple CSPs, on prem and edge locations and must also be able to interoperate as a single unit/mesh if designed with that intention.
This may require iPaaS offerings that can abstract the underlying offerings of the various deployment targets to present the expected resource to the SaaS entity or it may require the SaaS offering to be capable of doing this itself.
Leave a Reply