Glad to hear this! If there's anything I can do to make it easier let me know. I don't speak Russian but I set the subtitles in English so it's easier to read. Hopefully that helps;

@@ADevStory Yes. your subtitles helped me a lot. otherwise I won't understand your video completely. thank you for your time

Anytime!

Thank you! Glad you enjoyed it!

Glad it was useful! :)

Thank you very much! Glad you liked it! Let me know if you have other topics you'd like me to cover.

Nice! Hope you liked it!

Thanks!

Glad you found it useful! Thanks for the feedback! Let me know if there's specific content you'd like to see

@@ADevStory DDD and hexagonal architecture. Basically to know if it's worth it

Sounds good!

Glad to hear that! Good luck in your journey!

Glad it was useful! 😁 Feel free to suggest additional topics that may be interesting

Oh thank you! Cheers!

Thank you! 🙂 Really glad tou enjoyed it so much!

Thanks! Glad you enjoyed it!

Great summary!

Oh thank you! Glad you enjoyed it!

Thank you! Glad you liked it!

Thank you! And good luck in this career!

Thank you! glad you enjoyed it

Thank you for the feedback! Glad you enjoyed it!

Thanks for the chance and to the people like you leaving comments! Always learning and specially learning on how to edit videos and record sound 🤣 latest videos hopefully are better

Awesome glad you enjoyed it!

Oh thank you! Glad you liked it!

That was the idea! Glad you found it useful!

Awesome :)

Thank you for watching and sharing your feedback! Glad it was useful! If you like a video on a specific topic please let me know

Thanks!

Glad it helped :)

Hahaha thanks!

Yeah. There are different ways to learn that are helpful. Glad you enjoyed the video!

Glad it was useful!

Glad to hear that! In my experience Product Managers should focus on the what and devs on the how. Of course there's collaboration and from my point of view better devs should also get more on to product, and better product mangers should also improve the understanding of the how, but the focus should be the same.

Thanks! Glad you enjoyed it!

Glad you liked it!

Thank you!

Haha thanks!

Glad you enjoyed it!

Thanks! :)

Glad you liked it!

Amazing! Glad you liked it and happy to have you onboard!

Thank you!

Thank you! Any specific topic?

Glad you found it useful!

Thanks!

You're welcome! Glad you enjoyed it!

I can give it a try! Will add it to my list of topics :) thanks for the suggestion

Oh wow, you have a good challenge on your hands! So a developer with some time can help. No need for a solution architect (unless the tools are very common or standard and you can find experts). There are different ways to document architectures (for example the 4+1 view model: en.wikipedia.org/wiki/4%2B1_architectural_view_model) but being pragmatic I would start from a very high overview to the details. For example: - Start first with network communications: Which systems need to talk to which other systems? Does the Admin Panel talk to a database? does it talk to Shopify? these type of things. If you can have a big space for a diagram (in a whiteboard or diagramming tools like Miro) you can add it incrementally over some time. - Then continue going into more and more details. For example: Why does system A need to talk to system B? (there will probably be an API, like "PurchaseAPI" or something like that) so you can start having some names to those lines. In very complex systems it may be hard or time consuming to find all these communications, so I would recommend you to start with the most critical ones (the most used, the most risky, the most buggy, whatever the most critical ones mean to you) instead of trying to do all at once. Another approach is to do it by "use cases". Again, pick the most critical use cases for you and dig into the details of what's happening. For example: if the main use case is "user purchase", check all the systems, classes, databases that are affected throughout the interactions. Good luck!

Thank you very much for the detailed answer! it has been a great help. @@ADevStory

You're welcome!

Thank you for watching and the feedback!

Glad you liked it!

Awesome! :)

Thanks!

You're welcome! Glad you liked it!

Some people tend to use them without paying too much attention to the difference (like me :S), but Systems Design is more tilted towards the implementation details while Software Architecture it's more about the "big picture". As I see it, for example, in Software Architecture you would say: "I'll have a 3 layer application with one layer being the persistence layer/database", and when you start designing the system you decide how to actually setup the tables, which indexes you want to create on the data, etc. You are not alone in the confusion, I'll leave you with a couple of links with discussions/explanations on the differences. Hopefully they are clearer: - stackoverflow.com/questions/704855/software-design-vs-software-architecture - medium.com/@concisesoftware/whats-the-difference-between-software-architecture-and-design-b705c2584631

@@ADevStory This is extremely helpful information and resources, thank you so much for sharing this! I am currently at the senior software engineer stage and am looking to eventually grow into a Software Architect role... your channel is very helpful in my journey! All the best to you!

Thank you! Glad it has been useful!

Thank you!

Glad you enjoyed it!

Glad you liked it!

Haha thanks!

Thanks!

So in terms of what type of architecture to use is always tricky, hard and sometimes you may find that the architecture wasn't the best later and need to pivot. In some domains there's a "dominant" or "default" architecture. For example, in web applications typically a layered architecture works well. In high traffic/data driven applications, event driven architecture is commonly used. So in terms of being super practical, unless you have a very clear vision of the things that are different is good to start with the "default architecture" for that domain. You can find similar examples of the type of system you want to build on the internet and start with that base type of architecture. Of course, as you gain more experience, you would have seen more and more systems (some successful and other failures), maybe some built by you that allows you to get a clearer vision. There are different views to visualize architecture. One of the most famous/older ones is the 4+1 View Model, that includes different views: en.wikipedia.org/wiki/4%2B1_architectural_view_model. You can of course go with UML but the most important thing is not the type of diagrams you use but the message you want to communicate to others (and yourself!) about the system you are building. So as long as everyone involved in the project can understand all the moving parts feel free to use any type of diagram. Hope is clear, let me know if you have more doubts :)

Glad you enjoyed it!

Thanks for watching and the feedback! :)

Thank you!!

¡Gracias! ¡Qué bueno que te gustó!

Glad it was THAT clear🤣

@@ADevStory 🤣

Glad you liked it! Link is in he description. Sadly the pdf is not longer available for free.

@@ADevStory What are your consideration while choosing an architectural pattern to work with?

Usually what I mentioned in the video: it depends. Most enterprise project have a "default architecture" (or how George Fairbanks calls it in "Just Enough Architecture": "presumptive architecture). That means that most projects in certain domains will have similar needs. When I face something new I try to look for similar projects online/books and how they were solved, and if by any chance I can't find the information, try to build something stable but cheap, so I can pivot later more esaily in case the design fails.

@@ADevStory Thank you

Anytime!

Thank you!

Thanks!

Sorry it took me so long to reply! Yeah, there are some resources in the description of the video. There are a few, but some of my favorites are: - Fundamentals of Software Architecture: An Engineering Approach amzn.to/48mnsyL - System Design Interview - An Insider's Guide: Volume 2 amzn.to/460ynwM On the free side, I really like GOTO Conferences KZfaq channel: www.youtube.com/@GOTO-, Martin Fowler's Blog : martinfowler.com/ or Chris Richardson's blog on Microservices: microservices.io/ Please let me know if you'd like more resources.

Sorry about that. In newer videos it's smoother as I've tried to improve continuous recording. As a viewer I can also agree it's sometimes annoying

Thank you! And yes of course. In the description are my top recommendations and all the links. I would start with the free one I mentioned: Software Architecture Patterns since it's the shortest and very practical for reference. Let me know if it helps you!

@@ADevStory it'll be useful for me. Thanks!

Thanks! :)

There are cheap and expensive choices to make when designing software. So for example, changing the parameters of a function is way cheaper than deciding the persistent layer of the application. Software architecture is about making those expensive choices wisely. Decide what are the things that are harder to change in your application. Hope it's clearer

It depends on the company. But in many (or most) companies you first start as a junior software developer and gain more and more experience until you get more insights into how to design systems better and better. Some companies have an "architect" role and others are just more senior developers (or principal engineers) doing it. In my experience, the best "architects" are also the ones that do some hands-on or stay close to the software implementation. It can by participating in code reviews or running proof of concepts. So my tip is to try to practice different software architectures in small/pet projects and gain experience in companies building software and that will eventually get you there :) good luck

Haha nice!

Good question! I would say yes, it's fair. A senior developer must have already worked in multiple systems and it's typically a reference in the team on the technical side. What do you think?

Yep you are totally right. Not sure how I missed it and how no one mentioned it until now 😅

Oh it seems it's not longer available from that link in O'Reilly. I can't find a new link right now, so maybe by googling for the name you are able to find a new link. I can try and check again in the future if O'Reilly fixes/add a new link.

Thanks for reporting it, though

Here is a link to the pdf, hope it helps github.com/gg-daddy/ebooks/blob/master/software-architecture-patterns.pdf

What do you mean by it? Like word documents templates or sample architectures for similar startups?

​@@ADevStory Sample architectures for similar startups. Basically what type of infrastructure do startups usually use just to build and deploy the MVP? (Let's say... Browser -> Router 53 -> Load Balander -> ECS ... ? )

Oh but you are looking for typical setups if aws/cloud infrastructure. Hard to tell. There are probably other resources on the internet, I'm sorry I don't have them at hand. In terms of attitude, my approach would be the same as in this video. If you don't know anything about cloud start with something very basic and the start building more stuff. For example, how would you do it without cloud? Then try to find the equivalent approach in cloud. I can think of using a server where I'll deploy my code, so probably EC2 would be the first thing. As you get more knowledge then you can optimize (maybe use lambda) and so on

@@ADevStory Thanks for the detailed reply! I'm thinking about Heroku (for Front, Back and Database). I don't know if you have any thoughts on Heroku, but I don't want to take more of your time asking questions, but thank you so much for spending the time to answer my last question.

@@DanBP21 I haven't personally used Heroku but I've heard good things. It also depends on what you are trying to do in your startup. If you have too many unknowns, try to choose "boring technology" to reduce risks (boringtechnology.club/). With this I mean try to use what you know the most, what you can get more support of or can hire more easily.

You're welcome!

Thank you!

Sure! Someone already asked it in the comments, but KZfaq doesn't allow to link to the comment, so I'll paste the same answer: Some people tend to use them without paying too much attention to the difference (like me :S), but Systems Design is more tilted towards the implementation details while Software Architecture it's more about the "big picture". As I see it, for example, in Software Architecture you would say: "I'll have a 3 layer application with one layer being the persistence layer/database", and when you start designing the system you decide how to actually setup the tables, which indexes you want to create on the data, etc. You are not alone in the confusion, I'll leave you with a couple of links with discussions/explanations on the differences. Hopefully they are clearer: - stackoverflow.com/questions/704855/software-design-vs-software-architecture - medium.com/@concisesoftware/whats-the-difference-between-software-architecture-and-design-b705c2584631

@@ADevStory , the application architecture is the same meaning with the software architecture, right?

Yes

Sadly not possible anymore. O'Reilly made it paid.

It's a good question. I'm guessing since all application would have some type client/rendering aspect to it when access by users, so the book is focused on how is that application built instead of how do clients access it. Of course, i recommended the book because: it's short and concise, it's free and it's good, but by no means is exhaustive :) Also, keep in mind that some people differentiate between patterns and styles. The book talks about patterns, while client-server can be a style. More on that here: stackoverflow.com/questions/3958316/whats-the-difference-between-architectural-patterns-and-architectural-styles#:~:text=Styles%20generally%20provide%20guidance%20and,(or%20perhaps%20multiple%20styles).

Thank you!

Hard to say because I haven't seen their code but probably yes 😅

Thanks for the feedback! In newer videos I try adding shadows, but will consider adding even more contrast. Thanks!