Architecting ASP.NET Core Applications: Best Practices

Question 1

What is dependency inversion in soliD design principles?

Answer 1

Means that objects depends on interfaces instead of real implementations.

Question 2

What is the two main benefits of dependency inversion?

Answer 2

loosely-coupled applications and testable software.

Question 3

What is separation of concerns in Solid design principles?

Answer 3

Means separating software in different sections or modules which each one addresses a specific concern.

Question 4

What is the term “concern” in software architecture?

Answer 4

is a larger computational problem that can’t be solved by a single class.

Question 5

What is the DRY software dev principle?

Answer 5

don’t repeat yourself… meaning less code repetition.

Question 6

How is persistence ignorance is achieved?

Answer 6

Via POCOs - domain classes shouldn’t be impacted by how they’re persisted.

Question 7

What is the all-in-one architecture? What is an example of that?

Answer 7

All files, controllers, views (and everything else) are in the same (large) project. A MVC project.

Question 8

Can an all-in-one project be difficult to maintain?

Answer 8

Yes, can get very difficult since it is too easy to tight couple stuff.

Question 9

What are the 4 benefits of layered architecture?

Answer 9

1 - Is split according to concerns (modules);
2 - Promote reuse
3 - Easier to maintain
4 - Is pluggable.

Question 10

What are the 3 layers of a typical layered architecture?

Answer 10

Presentation, Business logic and data access layers.

Question 11

What is the 2 main disadvantages of layered architecture ?

Answer 11

Still coupling between layers and behaves as a single application.

Question 12

What is clean architecture (architecture style)? Was it created in 2012?

Answer 12

Is a variation of hexagonal and onion architectures styles. yes

Question 13

What is clean architecture based on?

Answer 13

In design principles (including SOLID)

Question 14

What is the 2 main benefit of clean architecture?

Answer 14

create maintainable and testable applications.

Question 15

What are the 3 circular layers of clean architecture?

Answer 15

Interface Entities, application core, Infrastructure/Presentation

Question 16

Which kind of code goes to the core project?

Answer 16

Entities, Interfaces (implemented later on in the Core and in the Infrastructure, Services and Exceptions).

Question 17

What is ultimately not permitted in the core project?

Answer 17

ef core or any presentation dependency (aka installed packages)

Question 18

Which kind of code goes to the infrastructure project?

Answer 18

Data access (ef core), logging, identity (auth), file access

Question 19

Which kind of code goes to the UI project? Can API go here?

Answer 19

MVC, Razor, middleware, filters. Yes, API also goes here.

Question 20

What are the main 3 benefits of clean architecture?

Answer 20

Independent UI, no knowledge of used DB, testable and maintainable.