Should I use a single or multiple database setup for a multi-client application? [closed]

by

I usually add ClientID to all tables and go with one database.
But since the database is usually hard to scale I will also make it possible to run on different database instances for some or all clients.

That way you can have a bunch of small clients in one database and the big ones on separate servers.

A key factor for maintainability though, is that you keep the schema identical in all databases. There will be headache enough to manage the versioning without introducing client specific schemas.

More Related Contents:

  1. How to design a product table for many kinds of product where each product has many parameters
  2. How to version control a record in a database [closed]
  3. What is the best database schema to support values that are only appropriate to specific rows?
  4. What is Normalisation (or Normalization)? [closed]
  5. Database design – articles, blog posts, photos, stories
  6. Schema for a multilanguage database
  7. Calendar Recurring/Repeating Events – Best Storage Method
  8. designing database to hold different metadata information
  9. Same data from different entities in Database – Best Practice – Phone numbers example
  10. What are the lengths of Location Coordinates, latitude and longitude? [closed]
  11. Are nulls in a relational database okay? [closed]
  12. Dynamic Database Schema [closed]
  13. How should I implement this schema in MongoDB?
  14. Why use multiple columns as primary keys (composite primary key)
  15. Microservices with shared database? using multiple ORM’s? [closed]
  16. Database schema which can support specialized properties
  17. Why use a 1-to-1 relationship in database design?
  18. Nullable Foreign Key bad practice?
  19. How to design a multi tenant mysql database
  20. Hash Collision – what are the chances? [closed]
  21. How to create a multi-tenant database with shared table structures?
  22. What are the advantages of using a single database for EACH client?
  23. How do you determine how far to normalize a database?
  24. Can we create multicolumn unique indexes on MS access databases?
  25. Database Design Best Practices [closed]
  26. A column as primary key or two foreign keys as primary key
  27. How to Store Historical Data [closed]
  28. uncertainty in developing a database model
  29. What are design patterns to support custom fields in an application?
  30. mongodb schema design for blogs

Leave a Comment