So you're a dotnet developer and you've heard the hype surrounding graphql, and you think "oh yeah, I just HAVE to try this!". Well prepared to be deeply underwhelmed.

Health check are important, both of our selves, but also of ourrrrr micro-services. This is something I came across lately – a health check of your connection to a database via EF Core context. Let’s check this out!

Often you might be interested in knowing how your LINQ Queries are translated to SQL Database in behind. The best way to profile ASP.NET Core, Entity Framework LINQ queries running on Azure SQL/ On-Premise SQL is to use Azure Data Studio.

LINQ is a powerful querying tool for .NET applications. There are certain techniques to follow when writing queries to make sure they run quickly and effectively. The following are a few things to consider when aiming to improve the performance of LINQ to Entities.

Basic and advanced samples - simple 'Hello GraphQL!' example based on console version from GraphQL for .NET on GitHub, but using ASP.NET Core, Entity Framework Core and some best practices, patterns and principles. Advanced - GraphQL queries and mutations with full 'Star Wars' database

In this post, we will see one awesome EF Core 2.1 feature which is DBContext pooling.

how we can leverage the various multitenancy configurations inside EF Core by leveraging a new EF Core 3 feature called Interception of Database operations.

Lets talk about configuring your Entity Framework Core DbContext for a moment. There are several options you might want to consider turning on.

We are going to learn about actions that modify the database content (Create, Update, Delete).

We are going to learn how to access the database via EF Core and how to read the data from it by using different query approaches.