![]() ![]() What’s more, our client wanted the app to suggest existing social networks to users based on information in their profiles.Īnd this is a very hard task for a relational database. The increased complexity was another reason to look into non-relational databases (also useful for the live chat functionality). Now, the need to have different access rights to individual entities like social networks meant creating even more relationships between the database entities. Creating additional connecting tables would’ve complicated the application’s architecture and slowed down the queries. It’s possible to use dynamic field attributes in a regular SQL database but sharing field values between different social networks is a big problem. Now, choosing a database that would satisfy all of these requirements was quite a challenge.
0 Comments
Leave a Reply. |