Snippet

Dynamic Database Routing with AbstractRoutingDataSource

AbstractRoutingDataSource allows for switching between multiple physical DataSources at runtime based on a lookup key, typically stored in a ThreadLocal context. This is essential for multi-tenant architectures where each customer has their own database.

snippet.java

java

public class TenantRoutingDataSource extends AbstractRoutingDataSource {
    @Override
    protected Object determineCurrentLookupKey() {
        return TenantContext.getCurrentTenant();
    }
}
 
@Configuration
public class DataSourceConfig {
    @Bean
    public DataSource dataSource() {
        Map<Object, Object> targetDataSources = new HashMap<>();
        targetDataSources.put("TENANT_A", dataSourceA());
        targetDataSources.put("TENANT_B", dataSourceB());
        
        TenantRoutingDataSource routingDataSource = new TenantRoutingDataSource();
        routingDataSource.setTargetDataSources(targetDataSources);
        routingDataSource.setDefaultTargetDataSource(dataSourceA());
        return routingDataSource;
    }
}

spring

Breakdown

protected Object determineCurrentLookupKey()

Determines the key used to look up the actual DataSource for the current thread.

routingDataSource.setTargetDataSources(targetDataSources)

Registers the map of available DataSources linked to their respective keys.

Previous snippet Next snippet

More Expert Java exercises →

Dynamic Database Routing with AbstractRoutingDataSource

Related