Ahh I think I understand you a bit more.
I also think there are different aspects and levels of an architecture.
A whole software has an architecture.
A single service has an architecture.
Packaging is part of an architecture but not the whole architecture itself.
When speaking of a monolith I think the whole software (not a single service) is meant. How the packaging is handled is somehow unrelated to this meaning (but is still part of the architecture). This is my opinion and I don't think that there is one right answer for this.
I still disagree. Packaging relationship to architecture is similar to relationship of technology stack - language/framework/platform/DB/cloud/etc. It has influence on architecture (for example, it might be necessary to add Circuit Breakers at some points), but architecture in general remains unchanged.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Ahh I think I understand you a bit more.
I also think there are different aspects and levels of an architecture.
A whole software has an architecture.
A single service has an architecture.
Packaging is part of an architecture but not the whole architecture itself.
When speaking of a monolith I think the whole software (not a single service) is meant. How the packaging is handled is somehow unrelated to this meaning (but is still part of the architecture). This is my opinion and I don't think that there is one right answer for this.
I still disagree. Packaging relationship to architecture is similar to relationship of technology stack - language/framework/platform/DB/cloud/etc. It has influence on architecture (for example, it might be necessary to add Circuit Breakers at some points), but architecture in general remains unchanged.