Should I keep my session management on postgresql or an external cache mechanism like redis or memcached?

Question

0.00/5 (No votes)

See more:

, +

With long and painful researches i decided to use session based authentication. I am developing an Web application with .Net core as backend and React js as frontend. I recently swap Node js backend to .Net Core. I am using PostgreSQL as my database. I heard PostgreSQL is bad for keeping sessions in it because it will be slow after like 10.000 session because it doesn't use cache and queries will be problem. Then i read How to Boost PostgreSQL Cache Performance and learn PostgreSQL also has a caching mechanism and it's managable. I can't decide which way to go. Also i read using Redis in production is not allowed, so its not free i guess? Can you help me decide? Thank you.

What I have tried:

I researched about this topic a lot on articles and posts in internet.

Posted 25-Oct-20 6:10am

2 7182818

Add a Solution

Comments

[no name] 25-Oct-20 12:39pm

"I am developing" ... "10,000 sessions" ... overly optimistic and premature optimization. No one gets anything "perfect" the first go.

2 7182818 25-Oct-20 14:45pm

do you think postgres can handle session management with like 5000 user connecting at the same time? sorry if you find this questions silly i just want to start with solid basis and i'm not planning to go massive and if i do, ofcourse i will change my way if there is any performance issue.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)