All geek questions in one place

Sharing ASP.NET state databases between multiple applications

Is it better to use the same session database for a collection of ASP.NET web applications or each one has its own?

If there are no significant differences, it is preferable to have one database due to simplified maintenance.

Background

My team has many ASP.NET web applications written either in Monorail 1.1 or in ASP.NET MVC 1.0. Each application currently uses a dedicated session state database. I am working on adding a new site to this list, and I am discussing whether I need to create a new session database or just use an existing one in another application.

+4
source share
2 answers

I would vote for sharing here.

I don’t think that you will definitely find that this will “simplify the maintenance” in the end, so that you can put everything in one database. If each application uses the same instance of a table and database, you cannot separate one application from the pool without duplicating the entire database. What if one application becomes viral and needs to be transferred to its own server cluster?

For the amount of work required to copy the database to a new instance, you will separate application problems, simplifying their debugging separately, more scalable and much more portable.

+2
source

Initial question: "Split the same session database." I see that this is different from the application database. ASP Session for all applications will be the same. You would not modify the schema for any of the session tables, SP, etc. We accept several applications, each of which has its own database for application data and one common database for the session.

+3
source

Source: https://habr.com/ru/post/1306248/

More articles:


All Articles