## 5 Discussion and Limitations  
A wide variety of messaging patterns are included in the profile. Efforts were made to keep the stereotypes names for the patterns brief and concise. However, the full names of patterns, components, or protocols were placed in stereotypes in the form of devoted tagged values. For ease of modeling, the icons for patterns should be unique. That is not fulfilled for all environments. For example, Apache Camel uses the same icon for Messaging Bridge and Change Data Capture patterns. Moreover, another icon is shared also by Threads and Throttle patterns. An important feature of the profile is the uniqueness of the proposed names for patterns and their icons. In the current version of the profile, protocols used in Internet of Things applications are included [25]. For protocols, there are no icons in the profile due to the fact that those stereotypes are attached to directed links between actions, which have standard look in the UML. Instead, the name of the stereotype is used. However, in terms of the Internet of Things, Covert Channels attract more and more researchers' attention. [PERSON] et al. [26] analyzed that topic, and their work may be a good source of patterns. Currently, they are out of the scope of the profile. The article shows that the area of communication between systems/services is constantly being developed, and more and more flexible patterns are emerging. An interesting is the Freelance pattern introduced in the ZeroMQ framework. It makes the communication mechanism independent of a single intermediary element. Therefore, it eliminates a single point of failure. These types of patterns can become the basis for communication between networks of distributed blockchain nodes. Such exchange of messages may also be organized in a distributed manner. For example, [PERSON] et al. [27] proposed a decentralized platform for the stock exchange that is based on blockchain technology. Another vital blockchain application is the managing of energy exchange among prosumer communities [28]. The patterns presented in the work vary in terms of complexity and range from single actions to architecturally complex but clearly defined components. For example, the use of the Resilient Publish-Subscribe pattern can greatly simplify the architectural description of the communication design between cooperating services. That is why the description of the software architecture is so important. The ability to present a design mechanism at a higher level of abstraction enables the definition of patterns that can be reused by the community. The actual limitation is that in the profile there are no detailed descriptions of the patterns. Future work should involve the configuration of constituents of the patterns. It should encompass those standard components provided by the pattern and components that fulfill certain roles that must be delivered by the integration flow designer. The next step is the generation of integration flows using tagged values as configuration parameters of message patterns. This mechanism has been successfully used in the continuous delivery and deployment of complete distributed blockchain applications and node deployment configurations for blockchain networks [29]. The use of the UML profile also positively affects the ease of maintenance of the designed integration models. Model elements in models are independent of stereotypes because they use basic types from the UML language. The tool used connects the profile to integration projects in the form of an external associated file. The profile design can therefore be developed independently, and the changes will be visible in the related integration projects. In addition, updating the profile involves adding more stereotypes or modifying the existing ones. Thanks to this, existing integration projects will be provided with the used set of stereotypes and newly added ones. The author has also intended to prepare the profile in a commonly used and affordable modeling tool, the Visual Paradigm Standard version.