Any questions about software architecture? Let us know for the chance to be featured on a DEV podcast!

#podcast #discuss

The DevDiscuss Podcast begins with an interview and ends with commentary from listeners — and we like to feature the actual voices from our community!

This week's prompt: “What are you burning questions about software architecture?”

For your chance to appear on an upcoming episode, answer the question above by:

Calling our Google Voice at +1 (929)500-1513 and leave a message 📞
Sending a voice memo to pod@dev.to 🎙
OR, leaving a comment here (we'll read your response aloud for you) 🗣

Please send in your recordings by September 30th at 5 PM PT (8 PM ET, 12 AM UTC)

Don't forget to check out the latest episode, released on September 16th!

Latest comments (24)

Drakso • Oct 1 '20 • Edited

How does architecture affect small scale systems and applications?
What architecture is the best fit for small applications and solutions?
How do we know when to stop adding complexity to our architecture and prevent over engineering?

Btara Truhandarien • Sep 30 '20 • Edited

There is a sense from job postings that software architecture is solely within the territory of more senior engineers. While the argument for experience makes sense, I also feel like junior developers should be put into more hands on architecture. A key aspect of architecture is design, and if making software isn't primarily seen as the task of designing computer systems, I don't know what it is then. Can you chime in on your experience or thoughts about bringing more junior roles to architecture decisions?

Henry Quinn • Sep 29 '20

When I have to implement something I've never done before, I often read a bunch of blog posts, articles, and StackOverflow answers - then homogenize all of that to come up with a solution.

How do architects go about making a decision when they have a handful of viable options for solving a problem they're facing?

Ankit Utekar • Sep 29 '20

What things an aspiring software architect should specifically focus on/things he/her should pay more attention to in his/her day to day job? What habits/practices he/her should try to employ?

Andres Cespedes Morales • Sep 29 '20

Hi @graciegregory ,

I've sent it out already but bringing it here as well.

Now, in this microservices world, software architectures are defining distributed systems (a.k.a. microservices) but when it comes to defining the granularity or size of these services there's no definite guideline, so what would be the advice on making this sizing/granularity challenge easier to deal with?

Also, there are plenty of questions that I would love to provide a solid point of view on them. Moreover, to participate in upcoming podcasts too.

Best,
Andres.

Gökay Okyay • Sep 29 '20

Hey!
My questions are:
1) When can a person call himself/herself a software architect?
2) Do you recommend any books/resources?
3) How to horizontally scale a stateful microservice?

Thanks!

Denis Anisimov • Sep 29 '20

My perpetual struggle is documenting the software architecture. Boxes and arrows diagrams in a Google Doc works fine, but I keep searching for the better approach. What are the tools, processes, and automations an architect can use to produce and keep in sync the documentation?

Simon Brown • Sep 30 '20

In case this doesn't get asked/answered on the podcast ... I created something called the C4 model that might help. It's a hierarchical set of diagrams that can be used to visualise software architecture. The website has lots of information, examples, and some links to tooling too. My recommendation would be to look at text-based tooling, which you'll find easier to keep in sync with changes in your codebase.