Note that there are some explanatory texts on larger screens.

plurals
  1. POScaling an Entity Framework Application / Multiple Apps hitting the same database?
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COFor performance: it depends where the bottleneck is. If you've got one query that's particularly expensive to run and it needs to run multiple times then spreading those executions across multiple DB instances might be the way to go. But if you have a lot of lightweight queries and most of time is spent inside your application then a DB cluster won't help. If you haven't done so, try profiling your application and seeing what % of time is spent in your code vs. external code vs. external resources (database, web service calls).
      singulars
    2. COBut at a more fundamental level, one of the complexities of dealing with multiple instances of an MVC application is state management. E.g. If you keep some information about the next page request in memory, but the user gets load balanced onto another server... How does that server know about what the first server's got in memory?
      singulars
    3. CO@te.speot.is - The problem is pretty much I/O related... The application isn't much more than a API... I have clients that send large requests containing a lot of data and my application has to process/sort/filter before storing in the back end DB... I need to support many more clients and just want to learn about EF scaling / I am worried what will happen when both front ends need to write to the same table.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload