Anything is possible without architecture! The sky's the limit!
You can build a bridge out of spaghetti! Use ramen noodles instead of rebar! Pour the foundation with asphalt instead of concrete! Hang sheet rock before installing the sprinkler system! Order 400 yards of 10" copper pipe for sewage!
These examples may seem silly and unrealistic, but you have not seen the shit that I have seen.
The purpose of architecture is to save time, money and sanity by constraining a particular solution space to fit the needs of a project's stakeholders. A family wants a 3 bedroom craftsman home with a fireplace in a residential neighborhood. An architect takes those stakeholder concerns and codifies them as constraints. If fireplaces are not allowed on new homes in the area, it is the architect's duty to communicate those risks to the stakeholder. Architects work directly with stakeholders to interpret and clarify their desires and translate those into engineering requirements.
Whether you're building a bridge or a house or a microservice or a software platform, there are a core set of principles that translate across disciplines and industries. Software architects concern themselves largely with diagrams, components, connectors and modeling languages but those are all just artifacts of the rigorous application of principled contextual domain knowledge; a practice common to all forms of architecture.
Some aspects of software architecture are standardized by the IEEE in:
These standards use architecture diagrams to communicate relationships between architectural concepts. Definitely worth a read if you can find a copy. The tools we use as architects may not always be the same and the decisions we make may not always be in agreement, but standards like these provide us a shared language to communicate effectively.
The books below provide excellent foundational knowledge in alignment with these standards and I'd recommend anyone interested in software architecture study at least one of them.