Today I'll show you how in I'm using MongoBD in web service part of Perfect Life application. I'll show how using good programming practices saves time.
I switch database to brand new instance of mongoDB. And I did it. And all that you'll see today was made within one hour. Interested? Keep reading...
As you know I tend to use interface to connect components in my application. It helps me to keep components loosely coupled.
For example I use dependency injection where controller uses IWeightRecord Repository.
Using interfaces this way makes it easy to switch my repository to something else.
In my case I'd like to create a new repository that depends on Mongo database instead of in-memory repository that uses Dictionary.
As the reault my data won't be deleted in case of web application restart. This is my target.
So first I'm adding a new Nuget package to my WebAPI application. The package is called MongoDB.Driver.
Next step is to create a new repository that I'm going ot use in my controller:
As you know my style of work I think the functionality is only halfway done without automated tests.
We need good integration test to make sure the application works fine:
The final step is to configure service provider in my ASP.NET Core MVC application in Startup.cs class.
I simply changed this line:
services.AddSingleton();
to this line:
services.AddSingleton();
This is what we managed to discover:
1) Using mongo in C# is really easy to configure - we operate on objects, not RDBMS using SQL - time savings when we don't need to create and maintain DB schema
2) When you use built-in Dependency Injection container in ASP.NET Core MVC, it's a matter of seconds to switch service. - Saving time!
3) When we keep in mind loosely coupling we can created a new repository and used it instead of the old one without a line of code in the controller class - saving time as we change only what we need.
4) With good suite of integration tests we can make significant changes in the logic of our application and be sure it's working without even running the app. Integration tests + Dependency Injection = huge time savings!
What is the summary thoughts? If we keep using good practices we can do amazing things in short time.
Not only maintenance is easy but with goot integration tests, you can be sure the app is working correctly always. There's need to run app and do manual tests while we use unit and integration tests.
I hope you'll use those techniques too and will create better applications in shorter time. Good luck?
I switch database to brand new instance of mongoDB. And I did it. And all that you'll see today was made within one hour. Interested? Keep reading...
As you know I tend to use interface to connect components in my application. It helps me to keep components loosely coupled.
For example I use dependency injection where controller uses IWeightRecord Repository.
Using interfaces this way makes it easy to switch my repository to something else.
In my case I'd like to create a new repository that depends on Mongo database instead of in-memory repository that uses Dictionary.
As the reault my data won't be deleted in case of web application restart. This is my target.
So first I'm adding a new Nuget package to my WebAPI application. The package is called MongoDB.Driver.
Next step is to create a new repository that I'm going ot use in my controller:
As you know my style of work I think the functionality is only halfway done without automated tests.
We need good integration test to make sure the application works fine:
The final step is to configure service provider in my ASP.NET Core MVC application in Startup.cs class.
I simply changed this line:
services.AddSingleton
to this line:
services.AddSingleton
This is what we managed to discover:
1) Using mongo in C# is really easy to configure - we operate on objects, not RDBMS using SQL - time savings when we don't need to create and maintain DB schema
2) When you use built-in Dependency Injection container in ASP.NET Core MVC, it's a matter of seconds to switch service. - Saving time!
3) When we keep in mind loosely coupling we can created a new repository and used it instead of the old one without a line of code in the controller class - saving time as we change only what we need.
4) With good suite of integration tests we can make significant changes in the logic of our application and be sure it's working without even running the app. Integration tests + Dependency Injection = huge time savings!
What is the summary thoughts? If we keep using good practices we can do amazing things in short time.
Not only maintenance is easy but with goot integration tests, you can be sure the app is working correctly always. There's need to run app and do manual tests while we use unit and integration tests.
I hope you'll use those techniques too and will create better applications in shorter time. Good luck?
Komentarze
Prześlij komentarz