A monolithic architecture describes an architecture where all of the following components are bunched into one codebase:
Views (i.e. HTML, CSS, Javascript)
Application/Business Logic (i.e. ExpressJS)
Data Access/Database (i.e. MongoDB)
Although this architecture may seem ineffective, not all industry professionals believe it is useless. For example, Martin Fowler advocates for the use of monolithic architectures when starting a new application. He notes that those who start their applications as microservice architectures usually end up wasting time and energy because you don't start seeing the benefits of this architecture until the application becomes complex.
He suggests starting with a monolithic architecture and refactoring it later into a layered or microservice architecture when it becomes too large to handle all in one piece.
Performance - how long do you have to wait before that spinning "loading" icon goes away?
Availability - what percentage of the time is the system running?
Usability - can the users easily figure out the interface of the system?
Modifiability - if the developers want to add a feature to the system, is it easy to do?
Interoperability - does the system play nicely with other systems?
Security - does the system have a secure fortress around it?
Portability - can the system run on many different platforms (i.e. Windows vs. Mac vs. Linux)?
Scalability - if you grow your userbase rapidly, can the system easily scale to meet the new traffic?
Deployability - is it easy to put a new feature in production?
Safety - if the software controls physical things, is it a hazard to real people?