Скачать или смотреть 4 Enterprise Application Integration Patterns | EAI Patterns

4 Enterprise Application Integration Patterns

0:00 - How applications in C#, Java and Python Programming Languages can talk to each other.
0:32 - 1st Enterprise Integration Pattern. use Flat Files
1:08 - 2nd Enterprise Integration Pattern. Use Shared Databases.
1:49 - 3rd Enterprise Integration Pattern. Use Message Queue
2:38 - 4th Enterprise Integration Pattern. Use Remote Procedure Call (RPC)

My Social Links
1. Twitter
  / vikasnetdev  
2.Linked In
  / vikas-ker.  .
3. Instagram
  / softwarearchitecturematters  
4.Blog
vikasnetdev.blogspot.com

Subscribe to this channel for your regular updates by clicking the following link
https://rb.gy/u1z0k0

Full Transcript:
What are the enterprise integration patterns? Let me ask how a .NET application can communicate with a Java application. These are different languages and different platforms. So today, we'll discuss the four ways in which you can write an application in Python, Java, and .NET, and then have them communicate with each other.

The first way is the oldest method, which is how we started: using flat files. The .NET application can read and write flat files, and the Java application can do the same. This is how applications written in different technologies and on different platforms can interoperate with each other. So, we are talking about the interoperability of different technologies and platforms. This is the first, primitive method: file sharing.

As we grew, files were not a good way, especially when working in a distributed environment where more and more people need to update data. Then databases came into the picture. Shared databases are another way that .NET applications, Java applications, or Python applications can communicate with each other. With files, a locking problem arose to ensure data consistency, especially when multiple users accessed the data. Databases offered a more meaningful and scalable solution.

The third way that .NET and Java applications can communicate is through messaging. There are many messaging solutions available, such as Microsoft Message Queue for .NET and various message queues in the Java world. Message queues provide benefits like working in disconnected architectures where pure internet connectivity may not be guaranteed. You can store a message in a message queue, and the message queue ensures that the message is delivered to the server.

The fourth and very popular, economical way for a .NET application to communicate with a Java application is through RPC (Remote Procedure Call). The most popular way is using web services, which can be either RESTful services or SOAP-based services that exchange XML-based or JSON-based data over HTTP.

So, today, we discussed the four enterprise integration patterns: file sharing, shared databases, messaging, and RPC.