Software architecture is nothing without correct algorithms and data structure to solve business problem.
What you need first is not software architecture, it's your algorithm.
Then comes your data structure.
Then you might need a SQL database to keep your data consistent.
The last one you need "might" be a simple software architecture, like MVC. Most of framework out there can help you with that.
To me, principle is more important than software architecture. Use what best to your use case.
The problem with that approach lies is what is often seen as the succinct definition of architecture: that which is hard to change afterwards. That doesn't mean that you need to think about architecture from the very beginning, but as soon as you have a serious project, that project will need an architecture.
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.
Software architecture is nothing without correct algorithms and data structure to solve business problem.
What you need first is not software architecture, it's your algorithm.
Then comes your data structure.
Then you might need a SQL database to keep your data consistent.
The last one you need "might" be a simple software architecture, like MVC. Most of framework out there can help you with that.
To me, principle is more important than software architecture. Use what best to your use case.
The problem with that approach lies is what is often seen as the succinct definition of architecture: that which is hard to change afterwards. That doesn't mean that you need to think about architecture from the very beginning, but as soon as you have a serious project, that project will need an architecture.