<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Trần Thành</title>
    <description>The latest articles on DEV Community by Trần Thành (@tranthanhdeveloper).</description>
    <link>https://dev.to/tranthanhdeveloper</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F517631%2F3b6550e6-c357-4faf-9167-a5d3f2b43e8a.jpeg</url>
      <title>DEV Community: Trần Thành</title>
      <link>https://dev.to/tranthanhdeveloper</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tranthanhdeveloper"/>
    <language>en</language>
    <item>
      <title>CONFIGURATION EMBEDDED H2 DATABASE IN SPRING BOOT APPLICATION</title>
      <dc:creator>Trần Thành</dc:creator>
      <pubDate>Sat, 02 Jan 2021 15:39:55 +0000</pubDate>
      <link>https://dev.to/tranthanhdeveloper/data-paging-and-sorting-with-spring-data-jpa-1om1</link>
      <guid>https://dev.to/tranthanhdeveloper/data-paging-and-sorting-with-spring-data-jpa-1om1</guid>
      <description>&lt;p&gt;Hi all guys, I have published an article introduce how to configure H2 database in Spring Boot application.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.programmingsharing.com/configuration-embedded-h2-database-in-spring-boot-application/"&gt;CONFIGURATION EMBEDDED H2 DATABASE IN SPRING BOOT APPLICATION&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Understanding Message in Spring Integration</title>
      <dc:creator>Trần Thành</dc:creator>
      <pubDate>Sat, 26 Dec 2020 17:35:55 +0000</pubDate>
      <link>https://dev.to/tranthanhdeveloper/understanding-message-in-spring-integration-30e8</link>
      <guid>https://dev.to/tranthanhdeveloper/understanding-message-in-spring-integration-30e8</guid>
      <description>&lt;p&gt;In order to loose coupling between components in a system, we typically apply the messaging system to achieve that aim. That requires a solid understanding of what is a message and some type of message for effective use for specific scenarios. So in this article, I would like to share the definition of the message, the structure of a message, and common types of messages in a messaging system. &lt;/p&gt;

&lt;p&gt;Remaining part of this article we already published at Medium &lt;a href="https://medium.com/programming-sharing/understanding-message-in-spring-integration-5270ae2787f3"&gt;Full article&lt;/a&gt;&lt;/p&gt;

</description>
      <category>systems</category>
      <category>architecture</category>
      <category>integration</category>
      <category>systemdesign</category>
    </item>
    <item>
      <title>POINT-TO-POINT AND PUBLISH/SUBSCRIBE MESSAGING MODEL</title>
      <dc:creator>Trần Thành</dc:creator>
      <pubDate>Sat, 19 Dec 2020 11:35:28 +0000</pubDate>
      <link>https://dev.to/tranthanhdeveloper/point-to-point-and-publish-subscribe-messaging-model-41j0</link>
      <guid>https://dev.to/tranthanhdeveloper/point-to-point-and-publish-subscribe-messaging-model-41j0</guid>
      <description>&lt;p&gt;&lt;strong&gt;Origin source: &lt;a href="https://www.programmingsharing.com/point-to-point-and-publish-subscribe-messaging-model/" rel="noopener noreferrer"&gt;https://www.programmingsharing.com/point-to-point-and-publish-subscribe-messaging-model/&lt;/a&gt;&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;Follow us on twitter: &lt;a href="http://twitter.com/progsharing" rel="noopener noreferrer"&gt;http://twitter.com/progsharing&lt;/a&gt;&lt;/strong&gt;&lt;br&gt;
&lt;strong&gt;Follow us on facebook: &lt;a href="https://www.facebook.com/programmingsharing" rel="noopener noreferrer"&gt;https://www.facebook.com/programmingsharing&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;In modern software architecture, the application needs to be decoupled, high scalability, serving high performance. Messaging service come in allows us to build that kind of application. Therefore with a solid understanding of messaging models is the key to build an effective system. There are two commonly messaging models, the point-to-point and the publish/subscribe model. Both of these messaging models are based on the message queue know as a central place to send messages to or place to get the message from. The sent messages are ordered in the message queue except it has higher priority. In basically, the message will be processed following the first-in-fist-out.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fimages.viblo.asia%2Fe1e26f91-7361-4cd0-a6a0-84449578104e.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fimages.viblo.asia%2Fe1e26f91-7361-4cd0-a6a0-84449578104e.png"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Point-to-Point Messaging Model
&lt;/h2&gt;

&lt;p&gt;In the point-to-point model, the message sent from the message sender to only one receiver even if many message receivers are listening in the same message queue. In the point-to-point model, the terms message sender and message receiver are usually applied rather than message publisher and message consumer. To illustrate, I have created a simple figure below.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fimages.viblo.asia%2F7621ed0f-a1fc-48ba-bd70-6a709b364d38.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fimages.viblo.asia%2F7621ed0f-a1fc-48ba-bd70-6a709b364d38.png"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;There are two types of point-to-point messaging, fire-and-forget(one-way) messaging and request/reply(request-response) messaging. The difference between fire-and-forget and request/reply is how the message sender cares about the status of the sending message.&lt;/p&gt;

&lt;h3&gt;
  
  
  Fire-and-forget
&lt;/h3&gt;

&lt;p&gt;In fire-and-forget, the message sender does not wait for any response from the message queue. It doesn’t care did the message queue receive the message or not. In this model, the Originator and the Recipient would have no interaction at all.&lt;/p&gt;

&lt;h3&gt;
  
  
  The request/reply messaging model.
&lt;/h3&gt;

&lt;p&gt;Different from the fire-and-forget mode, in the request/reply messaging model, the message sender sends a message on one queue, and then it waits for the response from the receiver. with this model, the send cares about the message status that’s it received or not yet.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fimages.viblo.asia%2F27dcf27f-f717-40cf-ba0c-1133d86aa305.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fimages.viblo.asia%2F27dcf27f-f717-40cf-ba0c-1133d86aa305.png"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Publish/Subscribe Messaging model
&lt;/h2&gt;

&lt;p&gt;The Publish/Subscribe Messaging or normally called pub/sub messaging is a form of asynchronous. In this domain, the message producers are called publishers and the message consumers are called subscribers. The publisher produces messages to a topic then all subscribers which subscribed to that topic will receive the sending messages and consume them. The difference between the point-to-point and publish/subscribe messaging model is how many receivers for a message. Another difference is in the point-to-point model, the message sender must know the receiver but in the publish/subscribe the message publishers do not need to know where the message will be consumed. This characteristic provides a high decoupling for the application when applying the publish/subscribe message model.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fimages.viblo.asia%2Fd05461f0-ea55-4275-9b6f-9223ccdc81d8.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fimages.viblo.asia%2Fd05461f0-ea55-4275-9b6f-9223ccdc81d8.png"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;Through this article, I have introduced you to common messaging models and I hope that will help you have a solid understanding of messaging services that have a good choice when trying to applying it to your application.&lt;/p&gt;

</description>
      <category>messagingservice</category>
      <category>pointtopoint</category>
    </item>
    <item>
      <title>String Pool in Java</title>
      <dc:creator>Trần Thành</dc:creator>
      <pubDate>Mon, 30 Nov 2020 08:07:24 +0000</pubDate>
      <link>https://dev.to/tranthanhdeveloper/spring-pool-in-java-3lph</link>
      <guid>https://dev.to/tranthanhdeveloper/spring-pool-in-java-3lph</guid>
      <description>&lt;p&gt;An article to show how Spring Pool works in Java language.&lt;br&gt;
&lt;a href="https://www.programmingsharing.com/string-pool-in-java/"&gt;Spring Pool in Java&lt;/a&gt;&lt;/p&gt;

</description>
      <category>java</category>
      <category>javase</category>
    </item>
  </channel>
</rss>
