Is software architecture more than just monolith vs microservices vs serverless?

Hello guys,

I've just started writing my thesis about an internship project in which I designed and developed some backend microservices for a web app.

I was searching on the internet some good articles about software architecture and I've found a really interesting article that talks about the definition of software architecture. In short it says that a software architecture is a shared understanding (between the developers) of the high level concepts and components of the system. Another given definition is " Architecture is about the important stuff. Whatever that is ".

The author argue about these definitions and even if it may be useless (or not) to reply to my question I suggest you this reading.

Until I've read this article I've always tought that software architecture is just about monolith and microservice "architecture" but right now i think it is more than this because the important stuff the author of the article talks about can't be only choosing between a monolith and a microservice based application. Tell me if I'm wrong.

I think that choosing between monolith / microservices / serverless belongs to the software architecture design phase of course but they are not the same concept.

So my question is: why I usually read microservices architecure vs monolith architecture? I'm tryin to find some terms to disambiguate two paragraphs of my thesis; the first one talking about software architecture (already written following also that article) and the second one talking about monolith "architecture" vs microservices "architecture". Practically I don't want to start the second paragraph saying that we can choose between two architectures because in the previous one I've said that software architecture is much more.

I hope I've written clearly my doubt and thank you in advance!