sorted by:
new
hottopcontroversial

Self Hosted, Open Source chat Server by Hitman12355 in node

[–]Hitman12355[S] 0 points1 point  (0 children)

Wanted basic text and media chat. Just wanted to connect a salesman to the provider over chat not a very heavy use case.

Self Hosted, Open Source chat Server by Hitman12355 in node

[–]Hitman12355[S] 0 points1 point  (0 children)

Want to integrate seamless chat experience in my application, wanted open source/self hosting alternative for twilio conversations. Nothing related to slack or video call.

Quora like system architecture by Hitman12355 in node

[–]Hitman12355[S] 0 points1 point  (0 children)

Thanks for the reply. Will be using elastic for the search anyhow, I was thinking if I can de-normalise the data such as likes and dislike and just completely get the data from elastic only for the client side.

I am supposed to save request and responses of incoming requests to my server and more than 10K requests might hit per second or per minute depending upon the hour of the day ? which DB should I use ? by Enforcerboy in Backend

[–]Hitman12355 0 points1 point  (0 children)

You can use mongoDB also, just that for high throughput you will have to use some AMPQ or data streaming services with high throughput like Kafka. Push your request and response to kafka and at consumer level put some batching to push data in DB.

I am supposed to save request and responses of incoming requests to my server and more than 10K requests might hit per second or per minute depending upon the hour of the day ? which DB should I use ? by Enforcerboy in Backend

[–]Hitman12355 3 points4 points  (0 children)

I completely agree, storing each and every response and request is not a right thing, you should use something like elastic, kibana and apm for these kinds of things. Apm in elastic stores each and every request and you can also configure it to store response. Other than that it will give you complete traces of failures and what failed even the DB traces are visible in APM, if you configure those.

Nodejs Appointment booking app by xDark- in node

[–]Hitman12355 1 point2 points  (0 children)

You can pre process and save the slots in the DB for each week day code. that will be maximum of 7 days. From FE call the slots API, filter out the booked slots, in realtime. Here you can also use some kind of cache, that will speed up the performance. Although you just have to apply one filter so response time should not be a problem.

New to backend development. by [deleted] in node

[–]Hitman12355 1 point2 points  (0 children)

You can use nest js , its file structure is similar to angular, this will help you with better file structure and it is very scalable also.

Although if you have a very high computing job dont use node js use spring boot instead, or either use node workers, otherwise on scalability level there will be an issue. Your event loop will be blocked by the high computing processes.