3 Cloud Service Delivery Model,
You Should Definitely Know as a Programmer (SaaS, PaaS and IaaS):
🧵👇
You Should Definitely Know as a Programmer (SaaS, PaaS and IaaS):
🧵👇
1. SaaS
- Known as Software as a Service.
- In this model, the user uses the software over the internet without having to worry about its maintenance, production, deployment, etc.
- Known as Software as a Service.
- In this model, the user uses the software over the internet without having to worry about its maintenance, production, deployment, etc.
- It provides the most layers of abstraction, as the end user does not need to worry about anything happening in the backend.
- Eg: Netflix, GitHub, Gmail, Typefully, etc.
- Eg: Netflix, GitHub, Gmail, Typefully, etc.
2. PaaS
- Known as Platform as a Service.
- It provides less abstraction than SaaS, here the user has the choice to add additional apps on the platform.
- User can use predefined settings to change system configurations, but still can't change most of the OS-level stuff.
- Known as Platform as a Service.
- It provides less abstraction than SaaS, here the user has the choice to add additional apps on the platform.
- User can use predefined settings to change system configurations, but still can't change most of the OS-level stuff.
- Common users of these systems can be a developer
- Eg: Heroku, AWS Elasticbean, etc.
- Eg: Heroku, AWS Elasticbean, etc.
3. IaaS
- Known as Infrastructure as a Service
- It provides the least abstraction and users can choose the entire Infrastructure like OS, CPU Power, Memory, etc. for their system.
- Mostly, admin level users are the main users of IaaS.
Eg: GCP, AWS, etc.
- Known as Infrastructure as a Service
- It provides the least abstraction and users can choose the entire Infrastructure like OS, CPU Power, Memory, etc. for their system.
- Mostly, admin level users are the main users of IaaS.
Eg: GCP, AWS, etc.
4. Similarity
- They all share a common idea where a service can be used by the end users via the internet without them having to actually manage them on their own.
- These are normally used through a subscription-based model.
- They all share a common idea where a service can be used by the end users via the internet without them having to actually manage them on their own.
- These are normally used through a subscription-based model.
That's a wrap!
If you liked this then you might also like reading my previous thread on DevOps:
If you liked this then you might also like reading my previous thread on DevOps:
Namaste, I'm Vikas!
Trying to diversify Tech Twitter with content on Backend Development.
Every Mon, Wed & Fri - I write a thread,
follow @vikasrajputin to read all my future threads.
Trying to diversify Tech Twitter with content on Backend Development.
Every Mon, Wed & Fri - I write a thread,
follow @vikasrajputin to read all my future threads.
جاري تحميل الاقتراحات...