Choosing the right architecture or pattern
Help with the decision-making process of matching software architecture, design patterns, and deployment strategies with a particular kind of application.
(or maybe include this in "Tooling and workflow choices")
There is an endless influx of these types of questions in the Software Engineering community and they are all way too broad to be answerable. I've been redirecting people to discussions. There is some overlap with "Tooling and workflow choices". I just feel like "tooling and workflow" choices completely misses discussions about "I am building a X style application. What is the right architecture?"
I like reading these kinds of discussions and engaging with them. It's a great way to get introduced to new ways of doing things, but I don't see a spot for it anywhere in the Stack Exchange ecosystem.
Some examples:
- Designing a third-party web solution
- Architecture of a scientific software
- What are the CPU architectures for the most common general purpose devices (i.e., Android, Windows/Linux PC, RaspberryPi etc.)?
- Architecture for SaaS that can run in my company's cloud or in clients' networks
- Best way to design an API that will allow for the remote controlling of a robot arm
- What is the best way to organize the folders and files in my web project?
- How can I merge between two software architectures in software design?
- Architectural pattern for testable C code
- What would be a best design for a 'cloud relay' application?
You can peruse the closed questions in the architecture tag for more examples.
I would like such questions to live in Discussions.