Your channel has been a godsend, even though most of the topics you've been covering are at least somewhat familiar to me, it's still awesome to have these concise information packages at hand. Little something to learn every day! Thanks for the consistency, hope you stay motivated and at it!
Here’s another industry: libraries and archives. Their catalog database is shared by library staff and patrons alike. The cataloguers need a bibliographic database in which to record the books, CDs, maps, etc. The circulation staff need an item database to record which copy is assigned to which branch; and which copy is checked out to which patron and when the copy is supposed to be returned. The patrons and reference staff need access to the bibliographic database to see what’s owned and subscribed to by library, what’s in which library branch and collection. The library needs to know who the patrons are and how to contact them. A multi-tenant database is ideal for this type of operation.
Wonderful explanation! Could you also make one explanation a bit more about how it's implemented at DB level? Like postgresql offers a schema based multi tenancy.
Thanks for the video, I haven't commented much recently. As another commenter said, godsend! I have a minor question just to consolidate my understanding if correct, so basically multi tenant architecture means a single software that has logic to support multiple customers who could have different users. And these customers have the ability to configure and modify stuff to, for example, match their brand identity and the perceived result for their direct customers through the software. Correct?
great work! your knowledge is really valuable and it shows in your vids :)
can’t wait for the next one!
Your channel has been a godsend, even though most of the topics you've been covering are at least somewhat familiar to me, it's still awesome to have these concise information packages at hand. Little something to learn every day! Thanks for the consistency, hope you stay motivated and at it!
Hey, I appreciate the kind words. Gave me the much needed push to stay consistent with the daily uploads. Cheers 🥂
Here’s another industry: libraries and archives. Their catalog database is shared by library staff and patrons alike. The cataloguers need a bibliographic database in which to record the books, CDs, maps, etc. The circulation staff need an item database to record which copy is assigned to which branch; and which copy is checked out to which patron and when the copy is supposed to be returned. The patrons and reference staff need access to the bibliographic database to see what’s owned and subscribed to by library, what’s in which library branch and collection. The library needs to know who the patrons are and how to contact them.
A multi-tenant database is ideal for this type of operation.
Wonderful explanation!
Could you also make one explanation a bit more about how it's implemented at DB level? Like postgresql offers a schema based multi tenancy.
Thanks for the video, I haven't commented much recently. As another commenter said, godsend!
I have a minor question just to consolidate my understanding if correct, so basically multi tenant architecture means a single software that has logic to support multiple customers who could have different users. And these customers have the ability to configure and modify stuff to, for example, match their brand identity and the perceived result for their direct customers through the software. Correct?
This is nice explanation but can do better..