This is a continuation of an earlier post REST API with ASP.NET Core 7 and InMemory Store. In this tutorial I will extend the service to store data in a Microsoft SQL Server, I will be using Microsoft SQL Server - Ubuntu based images for this sample. I will use Docker to run SQL Server and use the same to run database migrations.
Setup Database Server
I will be using a docker-compose to run SQL Server in a docker container. This would allow us the add more services that our rest api is depenedent on e.g. redis server for distributed caching.
Let's start by adding a new file by right clicking on Solution name in Visual Studio and Add New File. I like to name file as docker-compose.dev-env.yml, feel free to name it as you like. Add following content to add a database instance for movies rest api.
version: '3.7'
services:
movies.db:
image: mcr.microsoft.com/mssql/server:2022-latest
environment:
- ACCEPT_EULA=Y
- MSSQL_SA_PASSWORD=Password123
- MSSQL_PID=Express
volumes:
- moviesdbdata:/var/opt/mssql/
ports:
- "1433:1433"
volumes:
moviesdbdata:
Open a terminal at the root of the solution where docker-compose file is location and execute following command to start database server.
docker-compose -f docker-compose.dev-env.yml up -d
Database Migrations
Before we can start using SQL Server we need to create a database and table to store our data. I will be using excellent roundhouse database deployment system to execute database migrations.
I usually create a container that has all database migrations and tool to execute those migrations. I name migrations as [yyyyMMdd-HHmm-migration-name.sql] but please feel free to use any naming scheme, keep in mind how the tool would order multiple files to run those migrations. I have also added a wait-for-db.csx file that I would use as the entry point for database migrations container. This is a dotnet-script file and would be run using dotnet-script. I have pinned the versions that are compatible with .net sdk 3.1 as this the version roundhouse is build against at the time of writing.
Dockerfile to run database migrations
FROM mcr.microsoft.com/dotnet/sdk:3.1-alpine
ENV PATH="$PATH:/root/.dotnet/tools"
RUN dotnet tool install -g dotnet-script --version 1.1.0
RUN dotnet tool install -g dotnet-roundhouse --version 1.3.1
WORKDIR /db
# Copy all db files
COPY . .
ENTRYPOINT ["dotnet-script", "wait-for-db.csx", "--", "rh", "--createdatabasescript", "database_movies_create.sql", "--silent", "-cs"]
CMD ["Server=movies.db;Database=master;User ID=sa;Password=Password123;"]
I have added a script to create a custom database under db folder.
-
database_movies_create.sql
USE Movies
GO
IF NOT EXISTS (SELECT * FROM sysobjects WHERE name='Movies' and xtype='U')
BEGIN
CREATE TABLE Movies (
Id UNIQUEIDENTIFIER NOT NULL PRIMARY KEY,
Title VARCHAR(100) NOT NULL,
Director VARCHAR(100) NOT NULL,
ReleaseDate DateTimeOffset NOT NULL,
TicketPrice DECIMAL(12, 4) NOT NULL,
CreatedAt DateTimeOffset NOT NULL,
UpdatedAt DateTimeOffset NOT NULL
)
END
Add following in docker-compose.dev-env.yml file to add migrations container and run migrations on startup. Please remember if you add new migrations, you would need to delete container and movies.db.migrations image to add new migration files in the container.
movies.db.migrations:
depends_on:
- movies.db
image: movies.db.migrations
build:
context: ./db/
dockerfile: Dockerfile
command: '"Server=movies.db;Database=master;User ID=sa;Password=Password123;"'
Open a terminal at the root of the solution where docker-compose file is location and execute following command to start database server and apply migrations to create schema and movies table.
docker-compose -f docker-compose.dev-env.yml up -d
SqlServer Movies Store
I will be using Dapper - a simple object mapper for .Net along with Microsoft.Data.Sql.
Setup
- Lets start by adding nuget packages
dotnet add package Microsoft.Data.SqlClient --version 5.1.1
dotnet add package Dapper --version 2.0.123
- Update
IMovieStoreand make all methodsasync. - Update
Controllerto make methodsasyncandawaitcalls to store methods - Update
InMemoryMoviesStoreto make methodsasync
SqlHelper
I have added a helper class under Store folder named SqlHelper. It loads embedded resources under the Sql folder with extension .sql where the class containing the instance of thhe helper is. Reason for this is I like to have each SQL query in its own file. Feel free to put the query directly in the methods.
Class and Constructor
Add a new folder under Store, I named it as SqlServer and add a file named SqlServerMoviesStore.cs. This class would accept an IConfiguration as parameter that we would use to load SQL Server connection string from .NET configuration. We would initialize connectionString and sqlHelper member variables in constructor.
public SqlServerMoviesStore(IConfiguration configuration)
{
var connectionString = configuration.GetConnectionString("MoviesDb");
if (connectionString == null)
{
throw new InvalidOperationException("Missing [MoviesDb] connection string.");
}
this.connectionString = connectionString;
sqlHelper = new SqlHelper<SqlServerMoviesStore>();
}
I have specified this in appsettings.json configuration file. This is acceptable for development but NEVER put a production/stagging connection string in a configuration file. This can be put in secure vault e.g. AWS Parameter Store or Azure KeyVault and can be accessed from the application. CD pipeline can also be configured to load this value from a secure location and set as an environment variable for the container running the application.
Create
We create a new instance of SqlConnection, setup parameters for create and execute the query using Dapper to insert a new record, we are handling a SqlException and throw our custom DuplicateKeyException if Number of exception is 2627.
Create function looks like
public async Task Create(CreateMovieParams createMovieParams)
{
await using var connection = new SqlConnection(this.connectionString);
{
var parameters = new
{
createMovieParams.Id,
createMovieParams.Title,
createMovieParams.Director,
createMovieParams.ReleaseDate,
createMovieParams.TicketPrice,
CreatedAt = DateTime.UtcNow,
UpdatedAt = DateTime.UtcNow,
};
try
{
await connection.ExecuteAsync(
this.sqlHelper.GetSqlFromEmbeddedResource("Create"),
parameters,
commandType: CommandType.Text);
}
catch (SqlException ex)
{
if (ex.Number == 2627)
{
throw new DuplicateKeyException();
}
throw;
}
}
}
And corresponding sql query from Create.sql file
INSERT INTO Movies(
Id,
Title,
Director,
ReleaseDate,
TicketPrice,
CreatedAt,
UpdatedAt
)
VALUES (
@Id,
@Title,
@Director,
@ReleaseDate,
@TicketPrice,
@CreatedAt,
@UpdatedAt
)
Please note the column names and parameter names should match casing as defined in database up scripts.
GetAll
We create a new instance of SqlConnection, use Dapper to execute query, dapper would map the columns to properties.
public async Task<IEnumerable<Movie>> GetAll()
{
await using var connection = new SqlConnection(this.connectionString);
return await connection.QueryAsync<Movie>(
sqlHelper.GetSqlFromEmbeddedResource("GetAll"),
commandType: CommandType.Text
);
}
And corresponding sql query from GetAll.sql file
SELECT
Id,
Title,
Director,
ReleaseDate,
TicketPrice,
CreatedAt,
UpdatedAt
FROM Movies
GetById
We create a new instance of SqlConnection, use Dapper to execute query by passing the id, dapper would map the columns to properties.
public async Task<Movie?> GetById(Guid id)
{
await using var connection = new SqlConnection(this.connectionString);
return await connection.QueryFirstOrDefaultAsync<Movie?>(
sqlHelper.GetSqlFromEmbeddedResource("GetById"),
new { id },
commandType: System.Data.CommandType.Text
);
}
And coresponding sql from GetById.sql file
SELECT
Id,
Title,
Director,
ReleaseDate,
TicketPrice,
CreatedAt,
UpdatedAt
FROM Movies
WHERE Id = @Id
Update
We create a new instance of SqlConnection, setup parameters for query and execute the query using Dapper to update an existing record.
Update function looks like
public async Task Update(Guid id, UpdateMovieParams updateMovieParams)
{
await using var connection = new SqlConnection(this.connectionString);
{
var parameters = new
{
Id = id,
updateMovieParams.Title,
updateMovieParams.Director,
updateMovieParams.ReleaseDate,
updateMovieParams.TicketPrice,
UpdatedAt = DateTime.UtcNow,
};
await connection.ExecuteAsync(
this.sqlHelper.GetSqlFromEmbeddedResource("Update"),
parameters,
commandType: CommandType.Text);
}
}
And corresponding sql query from Update.sql file
UPDATE Movies
SET
Title = @Title,
Director = @Director,
ReleaseDate = @ReleaseDate,
TicketPrice = @TicketPrice,
UpdatedAt = @UpdatedAt
WHERE id = @id
Delete
We create a new instance of SqlConnection, use Dapper to execute query by passing the id.
public async Task Delete(Guid id)
{
await using var connection = new SqlConnection(this.connectionString);
await connection.ExecuteAsync(
sqlHelper.GetSqlFromEmbeddedResource("Delete"),
new { id },
commandType: CommandType.Text
);
}
And corresponding sql query from Delete.sql file
DELETE
FROM Movies
WHERE Id = @Id
Please note we don't throw RecordNotFoundException exception as we were doing in InMemoryMoviesStore, reason for that is trying to delete a record with a non existent key is not considered an error in Postgres.
Setup Dependency Injection
Final step is to setup the Dependency Injection container to wireup the new created store. Update Program.cs as shown below
// builder.Services.AddSingleton<IMoviesStore, InMemoryMoviesStore>();
builder.Services.AddScoped<IMoviesStore, SqlServerMoviesStore>();
For simplicity I have disabled InMemoryMoviesStore, we can add a configuration and based on that decide which service to use at runtime. That can be a good exercise however we don't do that practically. However for traffic heavy services InMemory or Distributed Cache is used to cache results to improve performance.
Test
I am not adding any unit or integration tests for this tutorial, perhaps a following tutorial. But all the endpoints can be tested either by the Swagger UI by running the application or using Postman.
Source
Source code for the demo application is hosted on GitHub in blog-code-samples repository.
References
In no particular order
Top comments (1)
Great Thank You