10 Architecture Patterns Used In Enterprise Software Development Today 

@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.

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

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

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

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

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

I had the same thought as well.

Not necessarily. The arrows represent the flow of information.

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

Especially enterprise level

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...

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

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.

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

Artificial intelligence in games and apps

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

@@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.

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.

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

I mean, she’s clearly reading a script

lol

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.

Layered + microservice + broker

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

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.

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.

@@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.

@@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.

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

@@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

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

@@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.

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

Pretty sure it was a Democrat.

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

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

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

Do you pay your modules for the work they do?