Hello folks, have couple of basic questions 1. How to think of actors in saas, especially in the enterprise setting? For ex. would infra saas treat typical cloud infra teams as their users looking to be more user friendly than public cloud admin consoles or is there more to it? 2. Infra saas seems cool, are we also going to see platform saas or s/w saas? what would that mean? Not sure if they makes sense, would like see how this model is approached, if m thinking along the right lines! Appreciate any pointers, thanks!

@sajid Is your question related more to teams' topologies? What would be the differences between saas infra, cloud infra and platform teams, in your view? I could try to provide my own potential definitions for those, but I'd like to understand what you're looking for 🙂 cheers!

Hi @Leo Gomes, thanks! No not exactly team topologies. I think infra, cloud and platform often gets used interchangeably, at least in my experience, but there is an implicit meaning attached to each. I have seen traditional infra teams typically manage only on-prem infrastructures but when applications move to a public cloud the same set of responsibilities get tagged under cloud infra, and now includes provisioning and ops for iaas, paas, or maybe even saas services, not 100% sure about the last one though. Platform teams I think should operate at a higher abstraction than these. Would like to know your take on this! My questions were more about the users/teams on the clients side actually. For a saas product I guess in most cases there are going to be some ops on both sides. So is this the space that infra saas products, like nile, looking to address? If yes then maybe there is more room there as one moves up the layers. Not sure if m able to articulate it well here but yes I realise I have a lot to go through on saas architectures 🙂 cheers!