Multi-Tenancy with Spring Boot
Download as PPTX, PDF•4 likes•4,601 views
The document outlines a presentation on multi-tenancy using Spring Boot, featuring a discussion led by Claire Hunsaker and Micah Silverman. It covers the challenges of customer identity management, the features of Stormpath's user management system, and various multi-tenancy approaches. Additionally, resources for further exploration and examples of multi-tenant applications are provided.
Multi-Tenancy with Spring Boot
- 1. Multi-Tenancy with Spring Boot
- 2. Welcome! • Agenda • Stormpath 101 (5 mins) • Multi-Tenancy with Spring Boot (25 mins) • Q&A (30 mins) • Claire Hunsaker VP of Marketing & Customer Success • Micah Silverman Java Developer Evangelist
- 3. Customer Identity Poses Major Challenges
- 4. Speed to Market & Cost Reduction • Complete Identity solution out-of-the-box • Security best practices and updates by default • Clean & elegant API/SDKs • Little to code, no maintenance Focus on Your Core Competency
- 5. Stormpath User Management User Data User Workflows Google ID Your Applications Application SDK Application SDK Application SDK ID Integrations Facebook Active Directory SAML
- 6. Features • Secure, flexible Authentication (Password, Token, OAuth, API) • Deep Authorization Groups, Roles Customer Organizations Permissions • Customer Profile Data • Single Sign-On Across Your Apps • Hosted User Screens
- 7. Multi-Tenancy 101 • Models Customer Organizations • Multiple Implementations in Stormpath • New “Organizations” Object = Super Easy
- 12. Different Multi-Tenant Approaches • Manual Selection Before Authentication • Manual Selection After Authentication • Automatic Selection by Subdomain
- 16. Different Multi-Tenant Approaches • Manual Selection Before Authentication • Manual Selection After Authentication
- 19. Stormpath
- 20. Stormpath
- 21. Stormpath
- 22. Stormpath
- 23. Stormpath
- 24. Stormpath
- 25. Stormpath
- 26. Stormpath
- 27. LET’S LOOK AT STORMPATH ADMIN!
- 28. LET’S LOOK AT SOME CODE!
- 29. Java Resources • Multi-Tenancy with Subdomains + Spring Boot https://stormpath.com/blog/idsite-multi-tenancy/ • Multi-Tenancy Code Example https://github.com/stormpath/stormpath-java-idsite-multi-tenant-example • Stormpath Java SDK https://github.com/stormpath/stormpath-sdk-java • Stormpath Java All The Integrations http://docs.stormpath.com/java/
- 30. QUESTIONS?
- 31. THANK YOU
Editor's Notes
- #10: Imagine you are building a self-storage business. You by a big building.
- #11: You build one storage unit and you rent it out. This one storage unit in your big building is probably not going to be profitable. But the great thing about storage units…
- #12: …is that they are easily replicated. You don’t need a new building – you already have that. Each storage unit has a lock on it granting access only to the set of people that know the combination.
- #18: So, you’re building your super sweet new app. It’ll probably be in the cloud (but, it doesn’t have to be)
- #19: You’ve got a Spring Boot application…
- #20: …and you’re going to use Stormpath to secure your Users’ identities….
- #21: You’ll create a Stormpath Application in the admin console (we’ll see this in action later)…
- #22: That Application is backed by a Directory – an Account Store
- #23: Here’s a user…
- #24: They can now securely authenticate to your application
- #25: Now, you want to support a totally different group of users – we call them Organizations. It’s the same application, just a different – separate – organization of users. Without Multi-tenancy, you’d need to replicate all this architecture.
- #26: With Stormpath, all we need to do is map your Stormpath application to Stormpath Organizations instead of directly to the Directory. In Stormpath, Organizations are just a different type of Account Store. They are a container for other Account Stores. Most importantly, the unique Organization name key is setup to match the subdomain that users use to access your application.
- #27: Now, we can keep our disparate user communities separated WITHOUT having to replicate our Spring Boot Application. We can add another Organization – with a name key that matches a subdomain – and just like that, we’ve got a whole new tenant.
- #28: Recap of presentation and Stormpath. Final pitch on how all these pieces fit together with Stormpath being an incredibly easy solution.
- #29: Recap of presentation and Stormpath. Final pitch on how all these pieces fit together with Stormpath being an incredibly easy solution.