Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 days ago.
Improve this question
I am building an inventory management system with Cassandra and Django, and I'm trying to implement multi-tenant data modeling.
I have the following tables in my system:
Product
Product by ID
Required Item
Product Builds
Order
Complete Order
The above tables are for a single company. But now I need to support multiple companies in my system.
I'm trying to decide between two options:
Create separate tables for each company
Add a company ID column in every table to distinguish between data belonging to different companies.
I have searched for information on multi-tenant data modeling in Cassandra, but I couldn't find any concrete information that could help me make a decision.
Can anyone provide me with guidance on how to implement multi-tenant data modeling in Cassandra for my use case? What are the trade-offs and considerations of each approach, and what are the best practices for implementing multi-tenancy in Cassandra?
Any help would be greatly appreciated. Thank you!
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I created 2 database designs (External & Internal Database). But I'm not sure if that fits in terms of relationship, normalization, logic, redundancy, ....
I also created 2 versions of the database design (The first one without mapping table and the second with). It's in German, I hope that's okay for you.
Do these designs meet typical relational database criteria such as 3NF, and do they specify the entity relationships in a clear and maintainable fashion?
database design 1
database design 2
Edit:
current database design
The ER diagram is OK of both internal and external because it is normalized, no redundancy, no many to many relationships and there is no functional dependency between fields except on the key.
I have a couple of comments about the diagram linked as "current database design":
The BM_Mapping table should use M-ID as its foreign key rather than Meeting_ID. The current design prevents any change to a value in the column Meeting.Meeting_ID.
I would keep the same primary-key naming convention in the Visitor table as used in the other tables. So V-ID rather than Visitor_ID
Apart from these comments, the rest of the design meets the standard RDBMS 3NF and entity relationship standards.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I worked on WPF project and connection to MySQL database.
My application is a host and can connect to multi equipment (Equipment1, Equipment2). After connecting to Equipment, all message between host (my app) and equipment need to store to database. Because data for logging is very large, I need to create logs_eqp_[eqmID] table for each equipment (example: logs_eqp_001 for equipment 1, log_eqp_002 for equipment 2).
So, could I use entity framework for this architecture? How could I do?
Regards,
I do not see why would you want to create tables dynamically. It would be much easier to have a single table with an indexed column for equipment name, so you could group, sort or filter your logs by equipment; with this approach you could avoid creating tables in runtime and can just use Entity Framework by the book by manipulating a single collection.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
For a small start-up mobile app/website what options are there for storing its data? I.e. Physical server or cloud hosted data base such as azure.
Any other options or insight would be helpful thank you!
Edit:
For some background I'm looking at something that users could regularly upload data to and consumers could query to find results through an app or website.
I guess it depends on your work load and also on the your choice of data store. Generally, SQL based storage are costlier on cloud based solution due to the fact that those can be only vertically upgraded whereas no-sql ones are cheaper.
So according to me you should first decide on your choice of data-store, which depends on following factors:
The type of data; is your data structured or it falls under non-structured category?
Operations that you will perform on the data. Do you have any transactional use-cases?
Write/Read pattern; is it a read heavy use case or a write heavy one ?
These factors should help you decide on an appropriate data-store. Each database has its own set of advantages and disadvantages. The trick is to choose one based on your use cases and above mentioned factors.
Hope it helps.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
How I can come up with an effective BodyBuilding database, what entities are most important?
From which I should be able to come up with an ER diagram. I'm still a novice to databases, but I have read quite enough, most difficult I'm finding a problem with differentiating between a Gym database and BodyBuilding Club database.
Have you tried listing everything you think relates to the database, then removing the ones you don't like, then grouping them in a way that makes sense to you or users of the database?
Certification types, access to bodybuilding books, bodybuilding trainers, ease of super sets, free weight ratios, ratings from heavy lifters, etc.
Try everything, make a list, narrow it down to the items needed for proper function and your business perspective (safety, legal, etc).
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I was at a .NET development group meeting a couple weeks ago and the speaker was extolling the virtues of NoSQL and how even relational data doesn't have to be stored relationally if you just index lots of data. So, my questions are: was he blowing smoke? How does one craft an index to be more efficient than the last? Does indexing just logically store the information in a table in a logical format i.e. alphabetically?
Well relational data is needed more for data integrity than indexing. Speed is not the only consideration when choosing a database. SQL Server and other enterpise databases can perform very well if they are designed by people who know what they are doing. Unforuntately most relational databases are designed by data amateurs and their performance reflects that.
NoSQL databases and relational database are used for different things. I would never consider putting a financial application in noSQL for instance because of the need for data integrity and internal controls to prevent fraud and ensure records are consistent and correct. However a website where data quality doesnt matter so much (think Google - who would notice if they failed to serve up every single website that mentions Bill Gates in a query) then yes it is a good choice.