Categorizing kinds of architectural patterns?

Question

Software design

Hello. I am trying for myself at this stage of my development to compile a classification of concepts from the world of OOP and software design. At the moment I am at such a crossroads: I

classified 2 general categories:
1) Architecture of the infrastructure level - we separate the actual application itself from the infrastructure. DBMS, Cache, all sorts of proxy servers, and other things that are not directly included in our application at the level of the internals of our application itself.
2) Application level architecture - the relationship of components within the application itself, that is, its levels. Here I now include, for example, a hexagonal and multilayer architecture.
2.1) Code level architecture - the relationship of entities within one layer in an application.

The question arose in connection with the complexity of the categorization of point 2.
At what level are the Microservice architecture and, for example, the Three (Multi)-layer architecture? Is it the same field of berries or are these different application levels? If the difference between a monolith and microservices is clear, this is the removal of different parts of the application into separate independent components that communicate with each other through, for example, REST, and the monolith itself, then the difference between a multilayer and three links and a monolith and a microservice is not very.

Question 2. Multi-layer architecture and for example MVC is it again the same field? At the moment I'm talking like this. MVC includes all we know what and we all know why and why 3 levels - view, model, controller. In this case, we can specifically divide them into layer M into DAL (for example, repositories) and services that contain business logic. That is, MVC is in some way a special case of a multi-layer architecture.

I ask you to help correct my mess in my head, if any. Thank you.