May 31, 2020 03:17 PM|LetMeCode|LINK
I'm about to start an asp.net mvc project with Repositorty-Service pattern and I'm first gathering information.
Therefore I've got few questions that I need clarification before I start implementing.
In my company, most of the asp.net mvc projects developed by senior developers possess common features such as :
So my questions are :
1) Do I always need a caching mechanism and logging and Security(Encryption - AES...) in an asp.net mvc app?
2) When do I need them? I mean in what situation do I need caching and logging and Security(Encryption)? please give me detailed answer for each for clarification.
3) Is it fine/professional to use in a real-world asp.net project, the default ASP.Net MVC authentication code that gets generated when you create a new asp.net app? as I'm building a quite big asp.net (not very big) web app with Repositorty-Service
pattern and I just want to reuse the default MS ASP.Net authentication (to save me time) instead of writing a new one.
4) Do I need to use SQL Server or MongoDB as database? I know that MongoDB is best suited for scalability but I don't want to use a library which I'll be forced to dig in to its library DLL and modify some code in order to make it work, as I don't
want to waste my time as the project is timed.