npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

loopback4-dynamic-datasource

v2.0.0

Published

An extension to connect to dynamic datasource in a loopback 4 application.

Downloads

282

Readme

loopback4-dynamic-datasource

LoopBack

This is a loopback 4 extension to connect dynamic datasources runtime. In todays world there can be a use case of multi tenant system in which we need the physical seperation of the databses so in loopback we need to connect to those datasources runtime and maintain and reuse those connection.

Image of Architecture

Install

npm install loopback4-dynamic-datasource

Usage

In order to use this component into your LoopBack application, please follow below steps.

  • Add component to application.
this.component(Loopback4DynamicDatasourceComponent);
  • Now add action provider to the action based sequence (This step is not required in case of middleware based sequence)
export class MySequence implements SequenceHandler {

    constructor(
        ...
        @inject(DynamicDatasourceBindings.DYNAMIC_DATASOURCE_ACTION)
        private readonly setupDatasource: SetupDatasourceFn,
        ...
    ) {}

    async handle(context: RequestContext) {
        const requestTime = Date.now();
        try {
            ...
            await this.setupDatasource(context);
            ...
        } catch (err) {
            this.reject(context, err);
        }
    }

}
  • Now write a datasource identifier provider that is used to identify runtime which source we need to connect. In below example getting the identifier from the tenantId coming in query of the request.
import {DatasourceIdentifierFn} from 'loopback4-dynamic-datasouce';

export class CustomDatasourceIdentifierProvider implements Provider<DatasourceIdentifierFn> {
    constructor() {
    }

    value(): DatasourceIdentifierFn {
        return async (requestCtx) => {
            const tenantId = requestCtx.request.query['tenantId'] as string;
            return tenantId == null ? null : {id: tenantId};
        };
    }
}

Now bind that provider in application.ts

this.bind(DynamicDatasourceBindings.DATASOURCE_IDENTIFIER_PROVIDER).toProvider(CustomDatasourceIdentifierProvider); 
  • Now write a datasource provider to get datasources runtime. these datasource will be created runtime on require basis
export class CustomDatasourceProvider implements Provider<DatasourceProviderFn> {
    constructor(
        @repository(TenantRepository)
        private tenantRepo: TenantRepository,
    ) {
    }

    value(): DatasourceProviderFn {
        return async (datasourceIdentifier) => {
            return {
                pgdb: async () => {
                    const tenantData = await this.tenantRepo.findById(datasourceIdentifier.id);
                    return new juggler.DataSource({
                        ...tenantData.dbConfig,
                    });
                }
            }
        }
    }
}

Now bind that provider in application.ts

this.bind(DynamicDatasourceBindings.DATASOURCE_PROVIDER).toProvider(CustomDatasourceProvider);

Note:- connector of following datasource should be present in package.json like in this example we are using loopback-connector-postgresql

Now return of this provider is an object where you can give as many keys you want but that should return juggler.Datasource This is used as the intention of connecting multiple datasource for tenant. pgdb this key is custom and it can be used as per your choice but your repository must use specified key in injection

export class UserRepository extends DefaultCrudRepository<User,
    typeof User.prototype.id,
    UserRelations> {
    constructor(
        @inject('datasources.pgdb') dataSource: JugglerDataSource,
    ) {
        super(User, dataSource);
    }
}

That's all.

Feedback

If you've noticed a bug or have a question or have a feature request, search the issue tracker to see if someone else in the community has already created a ticket. If not, go ahead and make one! All feature requests are welcome. Implementation time may vary. Feel free to contribute the same, if you can. If you think this extension is useful, please star it. Appreciation really helps in keeping this project alive.

Contributing

Please read CONTRIBUTING.md for details on the process for submitting pull requests to us.

Code of conduct

Code of conduct guidelines here.

License

MIT