Entity Framework Core Plus Query Future
Description
Every time an immediate method like ToList or FirstOrDefault is invoked on a query, a database round trip is made to retrieve data. While most applications don't have performance issues with making multiple round trips, batching multiple queries into one can be critical for some heavy traffic applications for scalability. Major ORM like NHibernate had this feature for a long time but, unfortunately for Entity Framework Core users, batching queries is only available through third party libraries.
EF+ Query Future opens up all batching future queries features for Entity Framework Core users.
To batch multiple queries, simply append Future or FutureValue method to the query. All future queries will be stored in a pending list, and when the first future query requires a database round trip, all queries will be resolved in the same SQL command.
// using Z.EntityFramework.Plus; // Don't forget to include this. var ctx = new EntitiesContext(); // CREATE a pending list of future queries var futureCountries = ctx.Countries.Where(x => x.IsActive).Future(); var futureStates = ctx.States.Where(x => x.IsActive).Future(); // TRIGGER all pending queries in one database round trip // SELECT * FROM Country WHERE IsActive = true; // SELECT * FROM State WHERE IsActive = true var countries = futureCountries.ToList(); // futureStates is already resolved and contains the result var states = futureStates.ToList();
EF+ Query Future
Query Future delays the execution of a query returning an IEnumerable.
// using Z.EntityFramework.Plus; // Don't forget to include this. var ctx = new EntitiesContext(); // CREATE a pending list of future queries var futureCountries = ctx.Countries.Where(x => x.IsActive).Future(); var futureStates = ctx.States.Where(x => x.IsActive).Future(); // TRIGGER all pending queries in one database round trip // SELECT * FROM Country WHERE IsActive = true; // SELECT * FROM State WHERE IsActive = true var countries = futureCountries.ToList(); // futureStates is already resolved and contains the result var states = futureStates.ToList();
Options
FutureValue
Query FutureValue delays the execution of the query returning a result.
// using Z.EntityFramework.Plus; // Don't forget to include this. var ctx = new EntitiesContext(); // GET the minimum and maximum product prices var futureMaxPrice = ctx.Products.DeferredMax(x => x.Prices).FutureValue<int>(); var futureMinPrice = ctx.Products.DeferredMin(x => x.Prices).FutureValue<int>(); // TRIGGER all pending queries int maxPrice = futureMaxPrice.Value; // The future query is already resolved and contains the result int minPrice = futureMinPrice.Value;
FutureValue Deferred
Immediate resolution methods like Count() and FirstOrDefault() cannot use future methods since it executes the query immediately.
// Oops! The query is already executed, we cannot delay the execution. var count = ctx.Customers.Count(); // Oops! All customers will be retrieved instead of customer count var count = ctx.Customers.Future().Count();
EF+ Query Deferred has been created to resolve this issue. The resolution is now deferred instead of being immediate which lets you use FutureValue and get the expected result.
// using Z.EntityFramework.Plus; // Don't forget to include this. var ctx = new EntitiesContext(); // GET the first active customer and the number of active customers var futureFirstCustomer = ctx.Customers.DeferredFirstOrDefault().FutureValue(); var futureCustomerCount = ctx.Customers.DeferredCount().FutureValue(); // TRIGGER all pending queries Customer firstCustomer = futureFirstCustomer.Value; // The future query is already resolved and contains the result var count = futureCustomerCount.Value;
Real Life Scenarios
Multi Tables Information
Client and all related information (order, invoice, etc.) must be loaded.
// using Z.EntityFramework.Plus; // Don't forget to include this. var ctx = new EntitiesContext(); var futureClient = ctx.Clients.DeferredFirst(x => x.ClientID == myClientID) .FutureValue(); var futureOrders = ctx.Orders.Where(x => x.ClientID == myClientID).Future(); var futureOrderDetails = ctx.OrderDetails.Where(x => x.ClientID == myClientID).Future(); var futureInvoices = ctx.Invoices.Where(x => x.ClientID == myClientID).Future(); // ONE database round trip is required var client = futureClient.Value; var orders = futureOrders.ToList();
Paging
The first ten posts must be returned but you also need to know the total numbers of posts
// using Z.EntityFramework.Plus; // Don't forget to include this. var ctx = new EntitiesContext(); var futurePost = ctx.Posts.OrderBy(x => x.CreatedDate).Take(10).Future() var futurePostCount = ctx.Posts.DeferredCount().FutureValue(); // ONE database round trip is required var post = futurePost.ToList(); var postCount = futurePostCount.Value;
Behind the code
- All queries from a context using query future are added to a batch list.
- When the first database round trip is required:
- All sql commands are combined into one sql command.
- The sql command is executed and a data reader is returned.
- For every result in the data reader, the result is set to the corresponding query future.
Limitations
- Provider:
- Provider not supported are added on demand
- Provider which doesn't support multiple statements like SQL Compact cannot be supported
Conclusion
As we saw, EF+ Query Future follows a good architecture principle:
- Flexible: Future, FutureValue and FutureValue deferred make it possible to use it in any kind of scenario.
- Maintainable: The easy to use API, documentation and available source code allows new developers to quickly understand this feature.
- Scalable: Query Future only gets better as the number of user/traffic grows by drastically reducing database round trips.
Need help getting started? info@zzzprojects.com
We welcome all comments, ideas and suggestions to improve our library.