Today we will look at a very common question that comes up in the minds of all application designers and developers. This question is when to use the standard N-Tier architecture as opposed to the much-hyped microservices architecture for building our applications.
I am not a database expert nor am I conversant with database design, but I have had a couple of run-ins with databases that are either badly designed or use a platform that doesn’t meet the needs of the end-user. I would like to think this is a "lessons-learned" synopsis.
Today we will look at a very common debate while developing the data access layer. This is to decide if we want to use stored procedures and keep our logic in the database or do we want to use an ORM like Entity Framework and keep all logic in our middle tier C# code and use the database as a store.
Does the idea of dealing with bits scare or confuse you? Does it seem like a waste of time in an age where we all have terabytes of storage? If so, you're missing out on one of the core tools in every professional programmer's toolbox. Learn how to do amazing, modern things with bits!
Databases are organized collections of data, most commonly accessed through management systems including schemas, tables, queries and processes that allow users to enter and manipulate the information or utilize it in other fashions, such as with web applications or for reporting purposes.