Regardless you can either parse the text into a relational model or store it as a single text field just the same as your entity currently is modeled as, if you wanted to use a relational database system for all of your data.
#MONGODB AND POSTGRESQL SOFTWARE#
By not having to worry about maintaining an object structure both in the data layer in addition to the application layer, NoSQL databases allowed developers with specific development needs to release software changes faster when managing a highly changing schema.įrom what I can see, your messages entity is structured but perhaps the content of the message text is not (an example of the text would be helpful). NoSQL was not invented to be more performant with reading, writing, or querying data, rather it was originally created to be a tool to improve developer speed especially with a highly changing or variable schema. The same is true for reading data as well. MongoDB is not any more performant with writing data than any other mainstream relational database (PostgreSQL, SQL Server, etc). This hopefully indirectly answers your question and points you in the right direction, it's too much to discuss in comments: NoSQL Use Case History What problems do i face if i use both together?Įnum: These events include remove_message block_user, etc. i just keep chat_ids and creation time of the events in PostgreSQL and the data of events in MongoDB. There is a table called events in both databases. Some part of the schema is relational i decided to use both PostgreSQL and MongoDB together.Ĭhats and members are stored in PostgreSQL and messages are stored in MongoDB. I had problems with NoSQL databases such as MongoDB and Cassandra. I'm designing a schema for a very large chat app.
0 kommentar(er)
