anchor.diff:  7. The route part related to the answer message type is very similar (answers are added to question aggregate).
   The main difference is the posting of a Twitter message when the aggregate contains three answers.
   
  +== Demo
  +
  +In order to run the demo, you need to have a Twitter https://developer.twitter.com/en/docs/basics/getting-started[developer account] with appropriate API keys and secrets.
  +
  +Go to the application directory and build all components:
  +
  +[source,shell]
  +----
  +$ mvn clean install
  +----
  +
  +Start the PostgreSQL database and MailHog SMTP server:
  +
  +[source,shell]
  +----
  +$ mvn -N docker:start
  +----
  +
  +In another terminal start the Q&A application backend service:
  +
  +[source,shell]
  +----
  +$ java -jar qa-app/target/component-qa-app-1.0.0-SNAPSHOT-runner.jar
  +----
  +
  +In yet another terminal start the Camel pipeline (provide your own Twitter API credentials):
  +
  +[source,shell]
  +----
  +$ mvn exec:java -Dtwitter.consumerKey=<...> \
  +    -Dtwitter.consumerSecret=<...> \
  +    -Dtwitter.accessToken=<...> \
  +    -Dtwitter.accessTokenSecret=<...> \
  +    -pl qa-camel
  +----
  +
  +Create a question and three answers to it:
  +
  +[source,shell]
  +----
  +$ curl -v -X POST -H 'Content-Type: application/json' http://0.0.0.0:8080/question/ -d @src/test/resources/messages/create-question.json
  +$ curl -v -X POST -H 'Content-Type: application/json' http://0.0.0.0:8080/question/1/answer -d @src/test/resources/messages/create-answer1.json
  +$ curl -v -X POST -H 'Content-Type: application/json' http://0.0.0.0:8080/question/1/answer -d @src/test/resources/messages/create-answer2.json
  +$ curl -v -X POST -H 'Content-Type: application/json' http://0.0.0.0:8080/question/1/answer -d @src/test/resources/messages/create-answer3.json
  +----
  +
  +The Twitter account should contain a new tweet with a text like `Question 'How many legs does a dog have?' has many answers (generated at 2020-02-17T08:02:33.744Z)`.
  +
  +The http://localhost:8025/[MailHog server UI] should display messages like these:
  +
  +[.centered-image.responsive-image]
  +====
  +++++
  +<img src="/images/camel-component-mailhog.png" style="max-width:100%;" class="responsive-image">
  +++++
  +*Figure 4. The MailHog Messages*
  +====
   
   == Conclusion
   
  
positive.code: = Integration Scenarios with Debezium and Camel
  jpechane
  :awestruct-tags: [ camel, integration, quarkus ]
  :awestruct-layout: blog-post
  
negative.code: 
  This article is focusing on the third option - a dedicated integration framework.
  
  == Apache Camel
  
  https://camel.apache.org/[Camel] is an open-source integration framework that enables developers to read, transform, route and write data from and to disparate systems and services.
  It provides a large amount of ready-made https://camel.apache.org/components/latest/[components] that either provide interfaces to 3rd party systems or offers an implementation of https://en.wikipedia.org/wiki/Enterprise_Integration_Patterns[enterprise integration patterns].
  
  This combination allows the developer to easily connect to target systems and express integration pipelines using a declarative DSL.
  
  === Camel and Debezium
  
  