CLARIFICATION I wanted to make one clarification for those watching this video. When I show the first "monolithic" architecture example, this is not representative of what a monolithic architecture describes. Monolithic and microservices describes how an application is distributed, while a "layered" architecture is a design that can be implemented within both a monolithic architecture and a microservices architecture. Therefore, the first example I show should more accurately be described as a "Monolithic architecture (with poor "n-tier" / "layered" design)" while the second example I show should more accurately be described as a "Monolithic architecture (with better "n-tier" / "layered" design)". This is just a complicated way to say that just because it is a monolith does not mean the code is poorly written (as portrayed in the video). Likewise, just because it is a microservice does not mean that the code is properly designed. That's all :) Hope everyone has a great day.
@HenrikMonsen2 жыл бұрын
Thanks for this clarification, exactly was I was confused about regarding this topic. You just helped my understanding finally "click" after hours of reading this stuff. Book I'm reading didn't make this very clear and went straight from layered to distribution architectures like client server.
@vasantdacha81004 жыл бұрын
The best part is you have shown using real time example.Thanks for the video Zach.
@bienne7773 жыл бұрын
Thanks Zack for explaining to us something very complex and not easy to grasp at all SLOWLY and CLEARLY, unlike many others who dashed off everything like lightning fast but leaving us with nothing solid on our mind!
@programmingchannel78912 жыл бұрын
Zach, many thanks to understand beginners minds. I searched many times for videos with practical code examples but I could not find. Finally I got your video what I wanted deeply. Really you know what beginners want. Many many thanks. Please upload more videos on software architecture and system design with practical codes. Thanks a lot again.
@dinn3825 Жыл бұрын
Nice explanation Zach! Thanks
@dawid_dahl4 жыл бұрын
Thank you SO much for providing this high quality content for free.
@For_bikers2 жыл бұрын
First time I am creating Architecture Diagram for our new OCI Application and had couple of doubts. Your video help me lot to clear the blockers. Thanks.
@shashankagarwal92852 жыл бұрын
Thanks from India bro, it was a great session and was one if the best available on KZbin platform which I am actually looking for.
@manisham11522 жыл бұрын
Explained it very well.Thanks Zack.
@ratnadeepchakraborty56164 жыл бұрын
Great video mate. Unfair that it has such less view. Such videos should reach more people. Best wishes !
@ahmedelshobaky50102 жыл бұрын
Perfect, thank you for this video!
@dmassawe3 жыл бұрын
Great simplest explanation I can find with code examples. Great job
@HylianEvil5 жыл бұрын
Great job on this video
@lilsoo23222 жыл бұрын
Thank you Zach! Excellent explanation about the three architecture. Really really appreciate it
@Sarch9614 жыл бұрын
Great explanation, examples and context! Much appreciated.
@hasansadaqa4545 Жыл бұрын
hey Zack! u r amazing man! thx alot
@halali31915 жыл бұрын
Thanks Zach ! , wonderfully explained
@rezNezami Жыл бұрын
well explained Zack.
@ignacemorel6412 жыл бұрын
Great tutorial from a real pro.
@lisaren66612 жыл бұрын
I learned a lot. Thank you so much!
@moussafiradil17003 жыл бұрын
high quality content, the examples are on point n really helpful, you earned your sub 🙏🏼
@AtulShukla15 жыл бұрын
You explain things very nicely.
@paytonthomas8585 жыл бұрын
Thank you for this video! I am new to all this and was still able to understand what I needed to understand.
@tri54314 жыл бұрын
Nicely done, thank you !
@chanelym3 жыл бұрын
Awesome! Thank you very much
@TheGameIsOverCy2 жыл бұрын
Thanks for the video :)
@balacr12 жыл бұрын
Thanks for the very simplified explanation of different architecture models. It was easy to understand with your examples. I have one question on the micro services architecture. In real micro service architecture, each service has its own UI/Views, business logic layer, and even data store. In such cases how is data shared between the different micro services? To explain if further, if you take your example. Say, the Authentication service or registration micro service has its own database. And the Game micro service has its own separate database. In this scenario, how will the Game service saves scores of a user? Will the Game Microservice use the same key ( Say user email) as the authentication service? And if the Game micro service needs more that just the email, say, it needs the users subscription details, payment details etc.? How do we handle such scenarios? I think database needs to be the same for the microservices to enable such requirements.
@zachgoll2 жыл бұрын
Yes, you’re right, you’ll need some sort of shared persistence layer like a database or in-memory store like Redis. Has been a while since I created this, so not sure if that made it into the video.
@bofyonkers3 жыл бұрын
During my time at large enterprises, we called the apps Monoliths, but based on this video were actually building a Layered architecture. The monolith described in this video only matches with what I've seen in amateur code. Does any "business" actually write code similar to this video's monolith design?
@pareshteredesai70484 жыл бұрын
Great informative video. Thanks
@alirabee764910 ай бұрын
I loved it. thanks
@bichhubiswa133 жыл бұрын
I must say it's a very informative video, thanks buddy for your efforts 👍👍👍
@o2662424 жыл бұрын
Brilliant. Thank you so much!
@przemyslaw5684 жыл бұрын
You saved my life. Thanks for this video
@redachouiba48624 жыл бұрын
Great job, Thank you so much.
@AyushGupta-dx1vf4 жыл бұрын
Are the two Microservices in the last example using the same datalayer or database ? If true, What if can these use distributed databases?
@VikasKumar-qj1vm Жыл бұрын
please make videos on other types also, please...
@HassaanIlyas4 жыл бұрын
Thanks man. It was really very helpful.
@SankarJankoti3 жыл бұрын
Great content!
@asifuddinkamruddin81303 жыл бұрын
Brilliant. To the point.
@miguelfernandez40514 ай бұрын
Thank you!
@luiscarlosricoalmada42962 жыл бұрын
Coool tutorial!
@itravelnotenough4 жыл бұрын
It was more than just a little bit of entitlement. Keep it going man!
@ntcuong01ct12 жыл бұрын
Dear Friends, When I design a software system, I divide it into 3 categories: 1/ Conceptual: I will state the names of the software that will respond to the requirements of the business process from users, describe the names of the software to be processed and the behaviors. 2/ Logical: I can define software architecture by applying architectural pattern in this step and I will include constraints on availability, scalability, maintainability. I also describe in detail the function of each component. This step 3/ Physical: Define programming language, platform to realize the description in Logical step. Could you recommend?. Thank you.
@shripadkalambkar87873 жыл бұрын
Very good information.
@zachgoll3 жыл бұрын
Thanks!!
@hazemhany32544 жыл бұрын
can i say that each micro-service you make is simply a layered architecture with it's own data access as if it was a break down project ?
@riyazahamed63344 жыл бұрын
Thank You for this video
@damarion585122 жыл бұрын
What course or master class do you recommend for someone to take if they are interested in being a software architect
@zachgoll2 жыл бұрын
I think the AWS Solutions Architecture certification is probably where you’d want to look, and there are lots of prep courses for that. It covers pretty advanced stuff. Most senior level architects have many years of software development experience. It’s much easier to architect something when you’ve already built something similar yourself.