1
Thinking of a system that at first is small and there is a possibility of a large growth in the flow, what would be the most intelligent/appropriate way to store notifications (a la facebook)? In . txt (don’t scare me.), SQL, Nosql.. Thinking mainly about the performance of the application. I believe that it does not interfere, but in order to clarify, I would use Js on the front and back (Reactjs and Nodejs).
3
I believe you are concerned to scale your application in the future if there is expected growth.
The decision on this architecture should be thought of in relation to the maturity of the project itself and utilization growth. You should consider whether implementing a more robust standard initially is feasible for the business - the team for delivering a new product is paramount.
As I told you, each strategy adopted has a related cost. You can use Nosql with key/value for great performance, but you will have to pay for it.
With SQL (I believe your project should be based on it), you have minimal cost now and if there is scale, using design standards, you can easily turn the key to another more optimized model.
Today, we have various products, with varied performances (Redis, Mongo, Cosmos, etc), each Nosql solution still has a choice of model to use.
If you have a budget and don’t want to save, a key/value standard can be great for this. But if the project is an MVP and will make a market test, reuse the available resources but preparing your backend for change if there is a quick scale.
Don’t forget that in a project that will have high availability, you don’t only need storage technology to scale. Design standards are essential for this task.
Browser other questions tagged javascript sql performance nosql scalability
You are not signed in. Login or sign up in order to post.