Expand server-side sessions documentation to include DbContext pooling guidance, clarify migration steps, and improve formatting for consistency.

Author: khalidabuhakmeh

src/content/docs/bff/fundamentals/session/server-side-sessions.mdx

@@ -45,9 +45,39 @@ builder.Services.AddBff()
         options.UseSqlServer(cn);        
     });
 ```
+The method of `AddEntityFrameworkServerSideSessions` registers the `SessionDbContext` along with a `UserSessionStore` as transient dependencies.
 
-### Entity Framework Migrations 
-Most datastores that you might use with Entity Framework use a schema to define the structure of their data. *Duende.BFF.EntityFramework* doesn't make any assumptions about the underlying datastore, how (or indeed even if) it defines its schema, or how schema changes are managed by your organization. For these reasons, Duende does not directly support database creation, schema changes, or data migration by publishing database scripts. You are expected to manage your database in the way your organization sees fit. Using EF migrations is one possible approach to that, which Duende facilitates by publishing entity classes in each version of *Duende.BFF.EntityFramework*. An example project that uses those entities to create migrations is [here](https://github.com/DuendeSoftware/products/tree/main/bff/migrations/UserSessionDb).
+For developers looking to take advantage of DbContext pooling or have more fine-grained control over their DbContext creation registration and creation process, you can use the `AddEntityFrameworkServerSideSessionsServices` method instead. This method registers all the required services for server-side session except for the `SessionDbContext`, which will now be managed by the DbContext pooling mechanism.
+
+```csharp
+var cn = _configuration.GetConnectionString("db");
+
+builder.Services.AddDbContextPool<SessionDbContext>(opt =>
+{
+    // configure your db context pool options here
+
+    options.UseSqlServer(cn);
+});
+
+builder.Services.AddBff()
+    .AddEntityFrameworkServerSideSessionsServices<SessionDbContext>()
+```
+
+Note, you'll still need to let the server side session store know about the `SessionDbContext` by calling `AddEntityFrameworkServerSideSessions` with the `SessionDbContext` implementation as a generic argument.
+
+### Entity Framework Migrations
+
+Most data stores that you might use with Entity Framework use a schema to define the structure of their data. *Duende.BFF.EntityFramework* doesn't make any assumptions about the underlying datastore, how (or indeed even if) it defines its schema, or how schema changes are managed by your organization. For these reasons, Duende does not directly support database creation, schema changes, or data migration by publishing database scripts.
+
+You are expected to manage your database in the way your organization sees fit. Using EF migrations is one possible approach to that, which Duende facilitates by publishing entity classes in each version of *Duende.BFF.EntityFramework*. An example project that uses those entities to create migrations is [here](https://github.com/DuendeSoftware/products/tree/main/bff/migrations/UserSessionDb).
+
+To quickly create Entity Framework migrations, run the following command in the project directory that has access to Entity Framework Core's tools:
+
+```bash
+dotnet ef migrations add UserSessions -o Migrations
+```
+
+The project must also reference the `Duende.BFF.EntityFramework` NuGet package and the `Microsoft.EntityFrameworkCore.Design` NuGet package, along with a specific database provider and its corresponding configuration, including the connection string.
 
 ## Session Store Cleanup
 Added in v1.2.0.
@@ -85,16 +115,16 @@ builder.Services.AddBff()
         options.UseSqlServer(cn);        
     })
     .AddSessionCleanupBackgroundProcess();`}/>
-        
+
     :::note
     In V4, we changed how you enable session cleanup. We no longer automatically register the session cleanup hosted service. This has to be done manually.
     In a load-balanced environment, you can choose to run the cleanup job on all instances the BFF. However, you can also decide to
-    spin up a separate host that's responsible for background jobs such as this cleanup job. 
+    spin up a separate host that's responsible for background jobs such as this cleanup job.
     :::
 
   </TabItem>
   <TabItem label="V3">
-  
+
     If you wish to have such sessions cleaned up periodically, then you can configure the *EnableSessionCleanup* and *SessionCleanupInterval* options:
 
       <Code
@@ -126,5 +156,4 @@ builder.Services.AddBff(options =>
     });`}/>
 
   </TabItem>
-</Tabs>
-
+</Tabs>