My point is that this definition has nothing to do with software, and in fact would mean that the last monolithic system was a Burroughs mainframe ca. 1960. This either invalidates the definition reductio ad absurdum, or confirms it but renders the term basically unusable.
This has everything to do with software and is not about any deployment architecture.
A monolith approach means a single program. This is a software architecture approach and implies by definition that the whole app runs as one in a single box.
Aside from my desktop calculator there is no computing device or application in operation today that meets the definition of a single program on a single box.
It is quite clear what a monolith approach means. It is well defined. If you build a webapp as, e.g. a Ruby on Rails app you have for practical purposes the whole of your app in a single program. You cannot have a few functions running here and other functions running there. It's all or nothing in the same place.
This is not a judgement on the merits of different approach, just a simple statement of fact and I am surprised that this should trigger so much nitpicking and sarcastic put-downs.
