The DevDiscuss Podcast begins with an interview and ends with commentary from listeners — and we like to feature the actual voices from our communi...
For further actions, you may consider blocking this person and/or reporting abuse
You can answer any (or none!) of these :-)
Thanks, @ender_minyard !! Any chance you'd be interested in sending in a voice recording of this comment? Or a similar one? We'd love to feature your voice on the podcast :) Instructions above if you are open to this!
Hello,
My questions are:
1) Why people are talking they are doing microservices when what are they actually doing is a monolith with several services or REST calls? Where is the misunderstanding? :)
2) Which are the most commonly used software architecture styles and patterns?
3) Are there any steps to follow when starting a new project and you have to design the architecture for it?
Thanks in advance!
Thank you, @alexandrum ! We'd love to hear a voice recording of this comment if you're open to it! Instructions above if you might be interested in that!
Glad you like them, but I am too shy even for a voice recording. Sorry :(
As someone who is starting to work on larger projects and trying to bring in other devs to contribute, I'd love to get a bit of a breakdown on how to approach architecture planning for a project.
As an architect myself, who learned what not to do from inheriting others' architecture (and who was forced to implement it earlier in my career), my question is:
Why do so many of you make it so damn complicated? And have none of you ever considered that junior devs might make up part (or possibly even all) of the team implementing it?
Go work for a tiny, cash-strapped startup, and you'll see how little of that crap can fly.
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?
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.
Should we always follow a design pattern? When is it ok to not use one?
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?
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?
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.
One big question;
Is SOA dead and replaced by Micro-Services?
I have this question for years now. I learned about SOA as an undergraduate and I have this burning question. 🤷
Thanks, @niweera ! I'd be interested to hear an answer to this myself!
Any interest in sharing this comment as a recording so we can feature your voice on an upcoming episode of the pod? If so, instructions on recording and submitting are above! Thanks 😊
Sure I'll try. 😊
What is the best way to store authentication API tokens on the client?
where can i found latest architecture trending ? podcast, Twittier account ..
Is agile still used ?
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?
how to scale 1 million people a day without downtime what should i prepare?
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!