I used to work with ASP.NET. I used the MS SQL server to store and retrieve data for display on some dynamic pages in one project. I started to learn a bit of ASP.NET. Now I'm going to start a new project, but this time I would like to save the data in a file-based database, for example, an access file. This project is also a hobby project, and I'm not afraid of the problem of scaling, because maybe only 3 users will use the application at a time and will not expect data traffic.
Now, about my question: using the MS SQL database there is no problem with multiple reads in read mode in Db at the same time, because the database engine will take care of this, but using a file database with ADO.NET will be a problem in this case, right?
What do I mean, do I need to take care of multi-user synchronization myself (using some kind of synchronization mechanism, lock, mutex, whatever) to guarantee the safety of threads when working with the database or does ADO.NET do this?
Should one layer be used for a data layer?
source
share