Who is using spring integration

And when 1, users publish something in 10 seconds, each one of whom has 1, followers? This specific problem could be resolved by using a queue.

Service A the producer , which is responsible for publishing posts, will just do that. It will publish a post and push an event with the list of users who need to receive an email and the post itself.

The list of users could be fetched in service B, but for simplicity of this example, we will send it from service A.

This is an asynchronous operation. This means the service that is publishing will not have to wait to send emails. Service B the consumer will pull the event from the queue and process it. This way, we could easily scale our services, and we could have n consumers sending emails processing events.

The annotation Value means that Spring will inject the value defined in the application properties into the field. This means redis. Now, we need to define the message we want to send to the queue. A simple example message could look like:. You can learn more about it from this Toptal article. The message itself will be saved in JSON format in the queue. Every time an event is published to the queue, the message will be serialized to JSON. And when consuming from the queue, the message will be deserialized.

With the message defined, we need to define the queue itself. In Spring Integration, it can be easily done via an. The next step is to define the gateway, which is mentioned in the.

For a gateway, we are using the RedisChannelGateway class from the org. StringRedisSerializer is used to serialize message before saving in Redis. Also in the. This means that the RedisChannelGateway bean could be injected into other beans. Class definition:. To wire this configuration into our application, we have to import it. This is implemented in the SpringIntegrationConfig class. ImportResource annotation is used to import Spring. And AutoConfigureAfter annotation is used to hint that an auto-configuration should be applied after other specified auto-configuration classes.

We will now create a service and implement the method that will enqueue events to the Redis queue. And now, you can easily send a message to the queue using the enqueue method from QueueService.

Redis queues are simply lists with one or more producer and consumer. And if you monitor Redis hint: type redis-cli monitor , you can see that the message is added to the queue:.

Now, we need to create a consumer application which will pull these events from the queue and process them. The consumer service needs the same dependencies as the producer service. The content of the queue config is:. In the. Again, to wire this config, we will need the SpringIntegrationConfig class, which can be the same as before.

And lastly, we need a service which will actually process the event. With Spring Integration and Redis, building a Spring microservices application is not as daunting as it normally would be. With a little configuration and a small amount of boilerplate code, you can build the foundations of your microservice architecture in no time.

Even if you do not plan to scratch your current Spring project entirely and switch to a new architecture, with the help of Redis, it is very simple to gain huge performance improvements with queues.

Each service in the system communicates by passing messages to the others. In a monolithic application, all components reside within the same process and communication is usually based on method or function calls within the same process. Subscription implies consent to our privacy policy. Thank you! Check out your inbox to confirm your invite. Engineering All Blogs Icon Chevron.

Filter by. View all results. Author Adnan Kukuljac. Spring Integration The project Spring Integration extends the Spring framework to provide support for messaging between or within Spring-based applications. Redis Redis is an extremely fast in-memory data store. Multiple consumers cannot consume the same event—this ensures that one event is processed once. Benefits of using Redis as a message queue: Parallel execution of discrete tasks in a non-blocking fashion Great performance Stability Easy monitoring and debugging Easy implementation and usage Rules: Adding a task to the queue should be faster than processing the task itself.

How do you go about doing this? Why should we have to write that code? What about the polling to see whether an application is available? And the webservice call? Generic components for TCP communication, polling or event handling, Web Service calls, routing and transforming, and many others. And it tries to mimic the full power of the patterns described in the EIP book while using a component model familiar to previous Spring Framework users.

It can be deployed within in application either stand alone application or part of a Java EE solution within an application server , within an ESB if you need, as part of a message broker, etc. Apache Camel is also a very powerful and highly capable solution to the integration problem space and it also implements the patterns from the EIP book. I can do a comparison in a future blog post if readers show interest.

For more information about Spring Integration, I recommend visiting their project page , taking a look at a recent book Pro Spring Integration , and of course reading and fully understanding the EIP book. See the original article here.

Integration Zone. Thanks for visiting DZone today,. Edit Profile. Sign Out View Profile. Over 2 million developers have joined DZone. What is Spring Integration? Like 2.