Hi Muhammad, it can depend upon multiple factors. For example, any specific requirement for any particular client. How many users are expected to chat simultaneously. what kind of information (only text, links to images etc.) is required to be stored. which language is being selected for the backend/API etc.. How many recent messages would you like to display to the user in the chat window. I think both of these can be used for this use case (however, MongoDB can be a better choice as per my understanding). However, the cost needs to be reviewed for both as per the use case. The indexes should be reviewed as well. Accordingly a decision can be made. For example, For messages older than a timeframe (day/week/month), you may like to move those messages to another collection for quick load of chat ( as these messages may rarely be referred by the user). Hope, this helps.
As far as my knowledge is concern,DynamoDB will allow a maximum of just 400 KB, while MongoDB has a limit of 16 MB. Do you have any valid resources what you're saying related to Data fetch size?
Thanks Talha for your question. What you have written is absolutely correct. This relates to the individual document max size. However, I've talked about the size limit during the data fetch i.e. what a query can return in terms of size. It can be multiple documents in response to a query. Hope, this helps. However, I would be glad to discuss more on this. Thank you once again for watching this vide so closely.
Thank you Ashwath for sharing your views about DynamoDB. However, there could be many use cases and scenarios where DynamoDB may be a good option. There are a lot of best practices available to design and data model DynamoDB.
Can we configure AWS Glue to communicate with MongoDB via the VPC endpoint by using Terraform? Can you please guide me.
which to use for chat app?
Hi Muhammad, it can depend upon multiple factors. For example, any specific requirement for any particular client. How many users are expected to chat simultaneously. what kind of information (only text, links to images etc.) is required to be stored. which language is being selected for the backend/API etc.. How many recent messages would you like to display to the user in the chat window.
I think both of these can be used for this use case (however, MongoDB can be a better choice as per my understanding). However, the cost needs to be reviewed for both as per the use case. The indexes should be reviewed as well. Accordingly a decision can be made.
For example, For messages older than a timeframe (day/week/month), you may like to move those messages to another collection for quick load of chat ( as these messages may rarely be referred by the user).
Hope, this helps.
As far as my knowledge is concern,DynamoDB will allow a maximum of just 400 KB, while MongoDB has a limit of 16 MB. Do you have any valid resources what you're saying related to Data fetch size?
Thanks Talha for your question. What you have written is absolutely correct. This relates to the individual document max size. However, I've talked about the size limit during the data fetch i.e. what a query can return in terms of size. It can be multiple documents in response to a query. Hope, this helps. However, I would be glad to discuss more on this.
Thank you once again for watching this vide so closely.
@@NeerajGarg got it. Thanks for the clarification ❤️
Great going Neeraj sir...
Thanks a lot for positive feedback Amit bhai.. this has encouraged me to go one step further in this journey..
👍
thanks for sharing it was nice
Thanks Anish, I'm really glad that you enjoyed it. I'm sorry for delayed response
Dont use Dynamodb. It's a jugaad way of using database
Thank you Ashwath for sharing your views about DynamoDB. However, there could be many use cases and scenarios where DynamoDB may be a good option. There are a lot of best practices available to design and data model DynamoDB.