Repository: github.com/rahul-s-bhatt/multi-tenant-springboot-starter
“How would Spring itself have approached this challenge?”
I aimed to allow developers to easily switch between DATABASE, SCHEMA, and SHARED isolation strategies for different tenants. Instead of the usual approach using the application.yml file in Spring Boot:
Stay tuned for more transparent development logs ✨
On the third day of developing the multi-tenant-springboot-starter, the focus shifted away from coding towards a new mindset.
While that method was functional, I pondered a different perspective:
Maximize the screen
This led me to devise a custom solution:
Looking ahead, tomorrow’s plan involves incorporating schema-per-tenant Hibernate integration.
💡 By utilizing this annotation, which leverages ImportBeanDefinitionRegistrar and EnvironmentAware, the tenant.strategy key is seamlessly integrated into the Spring Environment before any other configuration occurs.
The main lesson learned was that the quality of developer experience at the framework level is not just about using Spring, but also about aligning one’s thought process with it.
Maximize the screen
The revelation emerged that while Boot auto-config was reliable, it struggled to grasp custom annotations without connecting them through @import(…).
- Integrating the BEAN_CONTAINER tactic in JPA became imperative when manually configuring multiple EntityManagerFactoryBeans
- failure to do so may disrupt entity scanning.
