https://github.com/jmnarloch/hermes-spring-cloud-starter-stream

Spring Cloud Stream Hermes binder
https://github.com/jmnarloch/hermes-spring-cloud-starter-stream

Last synced: 4 days ago
JSON representation

Spring Cloud Stream Hermes binder

• Host: GitHub
• URL: https://github.com/jmnarloch/hermes-spring-cloud-starter-stream
• Owner: jmnarloch
• License: apache-2.0
• Created: 2016-06-11T17:06:04.000Z (over 8 years ago)
• Default Branch: master
• Last Pushed: 2016-07-11T22:25:47.000Z (over 8 years ago)
• Last Synced: 2023-07-04T14:06:58.390Z (over 1 year ago)
• Language: Java
• Size: 94.7 KB
• Stars: 4
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Spring Cloud Stream Hermes binder

> A Sprning Cloud Stream binder for Allegro Hermes

[![Build Status](https://travis-ci.org/jmnarloch/hermes-spring-cloud-starter-stream.svg?branch=master)](https://travis-ci.org/jmnarloch/hermes-spring-cloud-starter-stream)

[![Coverage Status](https://coveralls.io/repos/jmnarloch/hermes-spring-cloud-starter-stream/badge.svg?branch=master&service=github)](https://coveralls.io/github/jmnarloch/hermes-spring-cloud-starter-stream?branch=master)

## Setup

Add the Spring Cloud starter to your project:

```xml

  io.jmnarloch

  hermes-spring-cloud-starter-stream

  0.2.0

```

## Features

This project adds a binder for [Allegro Hermes](https://github.com/allegro/hermes) to [Spring Cloud Stream](https://github.com/spring-cloud/spring-cloud-stream).

By the way the Hermes has been designed there is no simple way to create a consumer so at this point only binding a

producer `MessageChannel` is being supported.

### Creating the binding

Creating the bindings for the Spring Cloud Stream is straightforward process and has been described in

Spring Cloud Stream [reference guide](http://docs.spring.io/spring-cloud-stream/docs/current/reference/htmlsingle/)

You can always bind to the generic `Source.class` using `@EnableBinding` and afterwards specify the final destination

through the properties:

```

spring:

  cloud:

    stream:

      bindings:

        output:

          destination: 'io.jmnarloch.events.purchases'

```

This way you specify the fully qualified name of the Hermes topic.

Alternative approach is to design the your own binding, example:

```

interface Events {

        @Output

        MessageChannel purchases();

}

```

In this case the topic name will be establish based on the method name, if you want to use specific topic name you can

do this by specific the value of the `@Output` annotation. Alternatively you can use the binding properties as showed

above.

### Binder properties

`spring.cloud.stream.hermes.binder.uri` - specifies the Hermes producer URI

## License

Apache 2.0