Multi-tenant architecture in 20 minutes

Carmel (Hinks) Saxby from Atlassian gives a presentation on multi-tenant architectures; what they are, why you would use them, and how Atlassian managed to make it work.

Please note - some technical difficulties were experienced at the beginning of the presentation, and approximately 20 seconds of footage has been cut out because of this.

[juniorbansal]

How is this video having only 200 likes? Very important architectural information given out for free.

[godwinyoh]

One of the best talks ever. So crisp, clear and packed.

[shayanchaudhary]

Awesome talk. Thank you for uploading this.
We're just about to re-platform our legacy product and this video has answered many questions and verified a lot of my thinking :)

[mohidk]

AWESOME! Brilliantly Explained 🎯Cheers Carmel 👍🏻

[paragmangal]

@Carmel Hinks : at @13:31, If we are still fine with eventual consistency for read then what was the need for single source of truth. I believe while writing data, you can set quorum and decide how many nodes should receive data before confirming write successful. Later all nodes will get sync data and have upto date information. In that way even write will also get performance improvement because write operation will also happen based on nearest datacenter. Please correct me if I have wrong understanding.

[stefc]

Fantastic video. Now I want to know how they structured there single-tenant architecture!!

[i-meta]

Excellent presentation! I must admit, though, the material reminded me of the excitement of Novell's Netware Directory Services back in 1995. Multi-tenancy is nothing new, but I am happy to hear how it has matured and remained relevant especially in cloud computing.

[soumakchongder]

In multi-tenant architecture how do we provide a certain feature to only a selected customer ? Acc. to me we can achieve this in single tenant by only upgrading a customer specific node..

[petersonmuchiri]

Fantastic Talk!!Kinesis is real love for multitenant applications!

[vinitjoshi]

Thanks for sharing. Found this useful for something I'm designing/architecting right now.

[ukazap]

Interesting approach to multi-tenancy.

[ChrisLow]

Literally the BEST video about multi-tenancy

[poshakmahe]

Thank you for such an amazing video !
One request, Can someone explain more about the client side caching ? Does it mean that client(say chrome browser accessing Jira) queries TCS and stores the DB info, and sends it in each request ? Or client refers to a microservices receiving the request from an app or web browser ?

[vijayvenkataraman]

Thanks for sharing. A good learning experience.

[scottamolinari]

Wait, wait, wait. I'm making an assumption here, but they talked about "stateless" nodes. Then they put caching (which is storage of state), on each of the EC2 nodes requesting information from the database? Why not have a separate caching server, where any node can invalidate/ update the cache centrally? That should have gotten rid of the need for the SNS service and leaves the nodes stateless. And, use Jira and it is slow. whatever.

[akdham]

Great presentation Carmel. I think you mentioned it, but wanted to verify that you are using TCS to obtain one which server a users data resides on. I know Altassian as I have used them before and know there are thousands and thousands of users. Were you setting up a different database per client or different schema per client within the database? I ask because at one time when I was using Altassian, I didn't use it as much only because I didn't have the time to learn it, great product though, and I know there are probably hundreds of users like me and dedicating a database per client seems a bit expensive to me. Perhaps I have it wrong, but curious to know how you managed this or did I miss this in the presentation. Like you said updating thousands of database if there is a change is time-consuming. Thanks...

[srsvg]

useful but in the middle you skipped couple of things... like where did catalogue service come all of a sudden with no background?

[wennwenn]

With reference at 12:49.
At 14:21, Why do we need to have a tool to sync data from single point of truth, write again and flush it back? Shouldn't Kinesis stream hold unread streams in its queue? and when Western EU is back online, start accepting messages inorder and save it?

[VishalPatel-hflg]

Thanks for sharing. very interesting. I am curious if anyway possible to only have cache at TCS side, no dynamo db. I.e (Catalog =dynamo+ec2) ——> stream ——> (Tcs=ec2 writing on cache)

[gamingbeast]

impressive deisnging and ingeneering <3