tenant application for multiple users

Navigation
1

Good my doubt and as long as the approach of creating a database in the following scenarios

  • Multiple Database, a database created by user
  • Multiple Schemas, well it would only have a single database, but each user would have their schema
  • A single table separated by user_id

    • Remembering that it would be an application that would have products registration and each user could have there from 4 thousand to 90 thousand products. It would also have many registered customers, many sales, anyway. It's kind of great per user.

    So I come here and ask you, in my scenario with many records in the database what do they indicate? With technologies

    Spring-Boot / Java / JPA / Hibernate / REST / PostgreSQL

    I've read topicals but nothing enlightening for my scenario. Some of them.

    Application and MultiTenancy Framework

    Multi-Client Web API

    How to work with multi tenancy architecture?

    Multiple web app

        
    asked by anonymous 24.10.2017 / 04:08

    1 answer

    0

    Simplest answer possible:

    1 - single schema: If you have many tenants (clients), thousands etc, this option is best for administration because it would not be very feasible to manage thousands of separate schemas. p>

    But in this option, if these tenants have too much data, performance may decline.

    2 - separate schemas: This option is best for many users accessing the system and making requests; possibility of customizing the application by tenant.

    This option is not very good for many tenants, imagine having to create thousands of schemas for each tenant and manage them.

        
    25.10.2017 / 15:51
    Calculating with JavaScript Error do not require_once