10 Architecture Patterns Used In Enterprise Software Development Today

Ever wondered how large enterprise scale systems are designed? Before major software development starts, we have to choose a suitable architecture that will provide us with the desired functionality and quality attributes. According to Wikipedia, an architectural pattern is a general, reusable solution to a commonly occurring problem in software architecture within a given context. In this video, I will briefly explain the most important architectural patterns used in the enterprise app development today.
****
INTERESTED IN THE STOCK MARKET?
I developed a profitable trading model that generates high probability BUY & SELL signals on S&P500. To learn about it, visit yuriymatso.com/sp500-model/

[@yuriymatso]

0:33 Layered Pattern / n-tier architecture 1:40 Pipe Filter Pattern 2:49 Client Server Pattern 3:48 Model View Controller Pattern 4:48 Event Bus Pattern 5:48 Microservices Pattern 6:45 Broker Pattern 7:46 Peer to Peer Pattern 8:54 Blackboard Pattern 10:00 Master Slave Pattern

[@domemvs]

What‘s important to understand is that these patterns are not mutually exclusive.

[@rbrohitbisht]

@k r If you try to integrate different applications then you may need to introduce more than one pattern. Say your application one need to call API's of application two, as well as a messaging queue also needed for the asynchronous task. In this way, API and messaging patterns are needed with pipes.

[@domnik9062]

This is very important. Today almost all projects use the Microservice architecture but is eazy applicable in others, for example Peer 2 Peer systems.

[@PabitraPadhy]

A mobile game/app uses almost all of these mentioned application pattern.

[@Titanium-de8hj]

Really sir! I haven't heard these pattern being an iOS developer until now. I have been heard MVC, MVVM, VIPER, MVP & so on patterns only.@@PabitraPadhy

[@domemvs]

Can‘t figure out if this is text-to-speech or a real person talking.

[@adelam.6123]

love love love the simple and structured descriptions and advantages/disadvantages for each pattern

[@stannone7272]

I think its crazy that you can find all this patterns in a frontend application nowadays.

[@moneyfish2490]

Good list of patterns. Great overview.

[@demarco6967]

this series is great!

[@user-jv8py1qe8t]

Thank you for your charity and kindness! Your lessons are awesome

[@kevinshoang]

Did you just present a mix of patterns in many domains in 1 video?

[@khalilbenali6037]

Thanks for this valuable content.

[@nicholas_obert]

Very clear explaination

[@animeshbhatt3383]

There are some subtle differences between architecture and design. Like MVC is more of a design pattern.

[@chloinger]

Thanks for this Video! Really helpful for my IOT course. ☺️

[@RefkyWahib]

Great video Thank you

[@mrsbootsworkouts]

Good information, thank you

[@riley3269]

I hear distortions in the audio that either means it's text to speech or just a crappy mic. If not then would love to know what text to speech this is because it's really good.

[@riptide828]

Great video. Thank you for that. I think there might be a mistake at 4:46 because the arrow between View and User should be pointing in the opposite direction as the user sees the view and not vice versa, or do I miss something? Best wishes and please keep up the good work!

[@crossugo5738]

I had the same thought as well.

[@ovidiub13]

Not necessarily. The arrows represent the flow of information.

[@matswessling6600]

@@ovidiub13the relation is named at the arrow is "sees" and it breaks the pattern. controller manipluates model but view doesnt see user.

[@vampiroast]

Thank you for your video! I have used n-tier and MVC patterns in my projects, I want to learn new patterns or architectures, I'm confused sometimes those words are used interchangeably. But I can't find practical projects of all the other patterns, just theory. Anyone knows where can I find practical projects?

[@1testrad]

thanks ...

[@sarthaksharma4816]

Thanks.

[@shizhouliu8912]

What's the diff between the broker pattern and event but pattern? They both like the Kafka.

[@yeabuddy9365]

Great video, anyone know of a valid use case/example for the blackboard pattern? Very possible only having experience with web and mobile development has limited my perception but, I can't think of when this would be an obvious design choice, although, I'm sure there are many obvious ones

[@lol785612349]

I think it's used for data analysis. By inputting more and more data, your model gets stronger.

[@zeektm1762]

Artificial intelligence in games and apps

[@hpgildwel]

I really dig the eventbus pattern

[@nck9689]

Often used in combination with microservices to ensure possible data duplication and general communication capabilities between the services.

[@deepaghera6801]

could some one recommend book which cover these all this architecture pattern?

[@elementsoflife2677]

I assume that the large enterprise apps can utilize multiple patterns concurrently. Is that true?

[@AntonMochalin]

Yes many of them are actually supposed to work together like MVC is often considered a way to implement presentation layer.

[@rainchai851]

Is the content generated?

[@contactdi8426]

I don't know but I found all of these patterns to be same.. Layered (4/3 tier architecture) == MVC =~ Client-Server architecture

[@andreujuanc]

Ah, the broken pattern. It never works. xD

[@martapfahl940]

7:17 So the Broker is nothing more than a Reverse Proxy right?

[@brianpack369]

Why is the Event Bus Pattern used in Android development and not iOS?

[@designthinkingwithgian]

What is a good book that helps introduce this topic to new readers?

[@alxx736]

Difference with Architectures Style ?

[@MrKristian252]

Can you justify why there is a performance bottleneck in Client-Server pattern? 3:18 Is it a performance bottleneck *because* it's a single point of failure, or just a performance bottleneck in general?

[@jojotheoj]

If your server is old and alone, it’s a limiting factor for everything else. If you’re spinning up VMs with replication/redundancy, you’re ok.

[@guidobit]

Hmmm what about cqrs, event sourcing, actor model...

[@subhadiphalder8873]

These are design patterns which can be used in any of these mentioned architecture patterns

[@carponneutrality1955]

@@subhadiphalder8873 Wrong. CQRS for example affects everything from your database design, your logic, to the UI implementation. It doesn‘t become more architectural than that. The other way round is true: the video mixes architectural patterns with design patterns. For example, MVC is no architectural pattern at all, but a design pattern for presentation implementations.

[@MrDubzein]

what is the modern combination of these patterns? MVC + Microservices?

[@penizesouta]

Layered + microservice + broker

[@coryserratore5951]

Layered (in a clean architecture manner) + MVC + microservices + broker + event bus + micro front-end

[@Casey_W]

I don't believe this presenter realizes that application patterns and enterprise patterns deal with very different issues.

[@technologicalwaste7612]

These concepts are how non-experts understand systems which they cannot resolve to any greater detail.

[@Warpgatez]

I mean, she’s clearly reading a script

[@fivedragons4526]

lol

[@aymanpatel5862]

Isn't Event Bus used in Kafka instead of Broker pattern?

[@Voidstroyer]

Kafka itself uses the event bus (or pub/sub as it's more commonly known) internally. But you can use Kafka as a service in your own application which would make it a broker because it does things for you on your behalf and you are oblivious as to how it does it. All you care about is the required input and the corresponding output.

[@ntcuong01ct1]

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.

[@pythontutorials5895]

Microservices is definitely the modern Top Ranked pattern!

[@JustCallMePCra]

Especially enterprise level

[@gangsterholla179]

Well it's more of s combination. Your load balancer is a broker pattern, your message queue uses a sub pub, your web api uses MVC,your database uses etc...

[@kayakMike1000]

Unix philosophy, a program should do one thing and one thing well is the same concept... Circa 1978.

[@penizesouta]

No, it is just one part. You need messaging and distributed memory such as Redis. Also all logs, metrics and business intelligence is in one place.

[@swagatdash6049]

Half of them are similar, like master-slave and broker, mvc and blackboard and so on

[@this.channel]

What's the difference between Architecture patterns and design patterns?

[@lepidoptera9337]

To your compiler? Nothing. To your code reliability? Nothing. To your ability to finish the project on time and budget? Nothing. That solely depends on how good you and your team really are as software engineers and how much room for success management gives you. The little bit of coarse/fine-graining on the architecture level can't prevent catastrophe if the project and team are not in good shape.

[@PositiveAlex]

Seems a bit random

[@pbdivyesh]

The top level categorisation is not correct here

[@paulfrischknecht2381]

Is this read by a robot or not?

[@_ashout]

A little too surface level. Not sure if I got much value out of this video

[@lepidoptera9337]

You don't get any value out if any of these videos because patterns are NOT what leads to good software. Patterns are ways to distribute tasks between programmers. Once the compiler is done with your code, the only difference between a flat piece of code with global variables and an OO version of the code using patterns is the order of heap variables and the call hierarchy on the stack. It turns out that deep stacks and convoluted heaps are actually counterproductive to safe code, so the OO pattern techniques are actually causing problems at the machine level (in case of buffer overflows, for instance). The only thing they help to untangle is the presentation of the code to the developers, i.e. they are not making the program better, they are merely reducing the confusion of the programmers... somewhat.

[@penizesouta]

@@lepidoptera9337 I liked your comment, but nowadays systems are distributed so it is not just about a single machine. At some point, you need a pattern to get better performance, not just to write a better codew.

[@lepidoptera9337]

@@penizesouta The compiler doesn't care about your distributed systems, either. That's just calls to code that shares data between machines. At the machine level it's still the same code transformations. There is nothing wrong with OO, but you should know what it is and what it isn't. It is _not_ a technique to write reliable software.

[@amcallejasherrera]

not recommended, it's mixing stuff, feels like a Wikipedia basic article

[@AntonMochalin]

How clueless are the people leaving comments like "this is informative". Except maybe they're sarcastic.

[@kayakMike1000]

Gotta start somewhere, but yeah. This is sorta kindergarten level software design.

[@AntonMochalin]

@@kayakMike1000 Kindergarten is ok but it is in some parts just plain incorrect and some explanations don't actually clarify things supposed to be explained

[@bestofthebest5642]

@@AntonMochalin can you write up where exactly did the video presenter go wrong?

[@AntonMochalin]

@@bestofthebest5642 one has already been mentioned here about n-tier vs layered, and even though they have those arrows in the animation they don't explain that layers have a particular order of dependencies. When describing microservices they in fact describe SOA. The MVC diagram though popular is misleading because it looks like model has dependency on view (model "updates" view) which isn't the case.

[@kayakMike1000]

@@AntonMochalin hum.... I didn't bother with it much... I assumed it was regurgitated from the gang of four book...

[@Smarttradingchannel]

You don’t make difference between design model and architecture Please study before learn to people

[@panth5501]

Is it just me or these are Design patterns and not Architecture patterns ?

[@kayakMike1000]

I wouldn't trust Wikipedia for a definition.

[@simolajustice6555]

the MVC pattern has no longer been the trend in the industry

[@hiphiphorhayy]

I havent gone thru the whole vid yet but where do monoliths go in all of this?

[@ismalcb31]

first

[@simbamore7768]

hi

[@charterest5100]

Who came up with the 'master-slave' naming? Appalling !

[@kayakMike1000]

Pretty sure it was a Democrat.

[@StevenMartinGuitar]

Oh no! We can't use words anymore! 🤐😭🤣

[@kayakMike1000]

@@StevenMartinGuitar it's worse than that, my operating system is systemically racist because it was written by mostly white guys.

[@penizesouta]

@@kayakMike1000 the code in my IDE is also white.

[@brianpack369]

Do you pay your modules for the work they do?