Thank you so much for the informative video. Multitenancy, in general, is a bit challenging, especially when it comes to managing tenants and their subscriptions through a dedicated tenant administration portal. This is in conjunction with data isolation strategies such as a Shared Database for All Tenants and a Separate Database Per Tenant. We dedicated the past four years to analyzing and studying the best practices that should be considered when building a SaaS app using the Multitenancy approach.
As far as I have understood, a desktop is the building and users can access the same desktop using different resources (gym / water / electricity for example)?
This was super cool. As Albert Einstein rightly said, “If you can't explain it to a 6-year-old, you don't understand it yourself” I am sure a 6 y.o would understand multi-tenancy with this content, Cheers!
Got anyone an Idea how to support multiple Azure Tenants with a single ADFS for the MFA? Cause on the Adfs i have to set-adfsazuremfatenant -tenantId and can only configure one Tenant and not multiple tenants.
Hi there, Taruchit! Thanks for the question, we'll see if we can include an explanation in one of our future videos. In the meantime, you can have a look at this article that talks about scalability 👉 ibm.co/3HUFxa8 (Best practices for cloud computing multi-tenancy) Hope this helps! 🙂
Hi Paul! I do not believe there are any drawbacks. The main concern people mention is system overload. However, in the cloud environmen,t scalability can be achieved to ensure the shared systems are not overloaded. Thanks for watching. Hope this helps. --Bryan.
Hi SB! The decision making process for multi-tenancy usually comes down to the security requirements and the level of multi-tenancy being requested. Security is usually down to the isolation at the hardware level, or even storage level depending on your needs. If you need physical separation then single tenancy is the better route to proceed, if it is acceptable to share compute/storage using ACLS to isolate different users/customers then multi-tenancy is a better route. For the level of multi-tenancy, this can range from bare metal or to a software instance eg Share physical database server, but running development / testing intances. --Bryan
Thank you so much for the informative video. Multitenancy, in general, is a bit challenging, especially when it comes to managing tenants and their subscriptions through a dedicated tenant administration portal. This is in conjunction with data isolation strategies such as a Shared Database for All Tenants and a Separate Database Per Tenant. We dedicated the past four years to analyzing and studying the best practices that should be considered when building a SaaS app using the Multitenancy approach.
This guy is fantastic at writing in mirror script!
Or! - hear me out... _they inverted the video horizontally_ 🤣
@@hecdavid11 😂😂
Love the IBM videos. It’s great for the industry. They are short nice summary’s. Keep them coming!
Thanks Rick!
was that dude writing backwards? respect!
Nope, he didn't.
Very easy and crystal clear explanation for Multitenancy. Thanks, I can understand what Multitenancy means in a high level.
mujhe smjha de phir
As far as I have understood, a desktop is the building and users can access the same desktop using different resources (gym / water / electricity for example)?
This was super cool. As Albert Einstein rightly said, “If you can't explain it to a 6-year-old, you don't understand it yourself”
I am sure a 6 y.o would understand multi-tenancy with this content, Cheers!
go watch oppenheimer he also helped make atomic bomb that killed many 6 year old kids
so hats off to him
Thanks man! needed this for an exam at uni
from a 3 min video i hope the question was youtube video name!
OMG. This is extremely easy-understanding. Thank you so muchhh for your explain 😍😍
I'm confused. It looks like tenant 1 has compute, tenant 2 has network, and tenant 3 has storage ...
no, all the tenants can choose what they want and in what scale
thank you so much Brian! Very good and easy to follow explanation and well paced:) well done
Thank you for the feedback, Theodore! Glad you enjoyed it! 🙂
What an explanation really thank you, time to read a research paper on this, thanks for the great introduction
no way bruhh u got it can u explain it to me?
Does a tenant represent a desktop machine?
Got anyone an Idea how to support multiple Azure Tenants with a single ADFS for the MFA? Cause on the Adfs i have to set-adfsazuremfatenant -tenantId and can only configure one Tenant and not multiple tenants.
short and sweet loved it !
Well explained MultiTenancy
Wie machst du das?
Thank you for making simple.
so is it another word for cloud?
Thanks alot for this amazing short video
Hello Sir,
Thank you for the tutorial.
Can you please elaborate more on scalability in the benefits listed for multitenancy?
Hi there, Taruchit! Thanks for the question, we'll see if we can include an explanation in one of our future videos.
In the meantime, you can have a look at this article that talks about scalability 👉 ibm.co/3HUFxa8 (Best practices for cloud computing multi-tenancy)
Hope this helps! 🙂
What is a Saas application
Is there a drawback in multitenancy? Since you mentioned that they are sharing computing power and storage?
Hi Paul! I do not believe there are any drawbacks. The main concern people mention is system overload. However, in the cloud environmen,t scalability can be achieved to ensure the shared systems are not overloaded. Thanks for watching. Hope this helps. --Bryan.
Also throttling ensures that each tenant consumes only within their limit, without affecting others (noisy neighbor problem).
Great explanation! Thanks!
Thank you very much🙏🏻
thank you very much, it's very clear
Very nice and informative bulletin size video. Thank you for sharing! Could you share some insights into decision making for Single Vs Multi-tenancy?
Hi SB! The decision making process for multi-tenancy usually comes down to the security requirements and the level of multi-tenancy being requested. Security is usually down to the isolation at the hardware level, or even storage level depending on your needs. If you need physical separation then single tenancy is the better route to proceed, if it is acceptable to share compute/storage using ACLS to isolate different users/customers then multi-tenancy is a better route. For the level of multi-tenancy, this can range from bare metal or to a software instance eg Share physical database server, but running development / testing intances. --Bryan
bro are you writing mirrored?
You are amazing..
the diagram to the right is wrong
Was I the only one who notice that he's writing each letter backwards?
th-cam.com/video/wCOuu0-o5YI/w-d-xo.html
tentant?
Thanks a lot
Loved it
It’s isolated as senior developer in a wet paper bag.
Man looks miserable and tired. o-o