In a monolith they may be modules within a single application/binary instead of different services.
Nobody said a monolith can't be split in modules :)
IMHO, a well-written monolith is like a microservice architecture but without the network layer in between boundaries.
I've been developing for 8+ years and have seen this model at every company where I've worked. I really thought this was just the "standard" way that everybody used to develop. I've also worked on a couple of CQRS architectures but the "layering" is still very similar to what you described.
I'm curious now, how do other monolith architectures look like if not like this?