Clean Architecture: A Craftsman's Guide to Software Structure and Design
By Robert C. Martin
The basic book. You will learn the rules, how to identify architectural smells and lean why the ARCHITECTURE MUST SCREAM. Oh, I forgot. It also shows why architects need to code.
A software architect's job is to leave the options open. Leave the decision on the details to others.
The database is a detail, the framework is a detail and the UI is a detail too.
Interesing link (part of the book)
Designing Data-Intensive Applications
By Martin Kleppmann
THE BOOK for understanding data related tools and patterns: from the begginings of storage to RDBMS, NoSQL... and data processing patterns like batch, streaming, etc. It teaches you the fundamentals. And you will see that they don't change.
Foundations of Architecting Data Solutions
By Ted Malaska & Jonathan Seidman
Interesting book that can guide through the process of choosing an open-source tool, understanding the roles within a data application development team and the phases of a product. It also explains briefly the different patterns and considerations for managing risk and communicating it to others.