dreat/homepage
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

change permalinks

Browse source
This commit is contained in:
Lukasz Skotarek 2020-04-02 10:54:30 +02:00
parent 63f9168258
commit a8f4b86046
23 changed files with 46 additions and 46 deletions
Download patch file Download diff file Expand all files Collapse all files

6
_posts/2017-03-26-integration-series-messaging.md
View file

@ -5,11 +5,11 @@ author: dreat
post_excerpt: ""
layout: post
permalink: >
http://dreat.info/2017/03/26/integration-series-messaging/
http://dreat.info/2017-03-26-integration-series-messaging/
published: true
post_date: 2017-03-26 20:50:50
---
<a href="http://dreat.info/2017/03/17/introduction-to-integration/">Last time</a> we spoke about some integration methods we can use.
<a href="http://dreat.info/2017-03-17-introduction-to-integration/">Last time</a> we spoke about some integration methods we can use.
As we see, there are methods that are not so tight coupled, being able to generate lots of little data packages (like file transfer), easily synchronizable (like shared database), details of storage's structure hidden from applications (unlike shared database) and being able to send data to invoke behavior in other app (like RPI) but with being resistant to failure (unlike RPI).
@ -19,4 +19,4 @@ And here messaging comes to play. The rules are simple: you create message, send
<li>Decoupling. Messages will be sent to message channel without knowing almost anything about receiver. The common interface are the types of messages sent, not the bidings between apps. It also allows separation integration developement from application developement.</li>
<li>Frequent, small messages allow applications to behave almost immediatly by sending more messages.</li>
</ol>
And many more we'll explore in the series. Why I will write a series on it? The main disadvantage of messaging is the learning curve. While other methods are fairly easy to use, messaging and async thinking is not something we're used to. But once learned this concepts will help you not only when integrating lots of enormous applications. You can also apply it to "integrate" classes/functions/actors in your code.
And many more we'll explore in the series. Why I will write a series on it? The main disadvantage of messaging is the learning curve. While other methods are fairly easy to use, messaging and async thinking is not something we're used to. But once learned this concepts will help you not only when integrating lots of enormous applications. You can also apply it to "integrate" classes/functions/actors in your code.