anchor.diff:        .setHeader("Subject").simple("Question created/edited")
         .setBody().simple("Question '${body.text}' was created or edited")
         .to(SMTP_SERVER);
  -
     }
   }
   
  
positive.code: = Integration Scenarios with Debezium and Camel
  jpechane
  :awestruct-tags: [ camel, integration, quarkus ]
  :awestruct-layout: blog-post
  
negative.code: 
  Internally the component exposes a Debezium https://camel.apache.org/manual/latest/endpoint.html[endpoint] with Camel event driven https://www.javadoc.io/doc/org.apache.camel/camel-api/latest/org/apache/camel/Consumer.html[consumer] that encapsulates an instance of https://debezium.io/documentation/reference/1.1/operations/embedded.html[Debezium embedded engine].
  
  == An Example
  
  As an example we've built a simple Question & Answer (Q & A) application,
  loosely inspired by StackOverflow and the likes.
  A REST API allows to post new questions as well as answers to existing questions,
  which are stored in a database.
  
  Any data changes generated by the application (e.g. if a new question or answer got created) are captured via Debezium and passed to the Camel pipeline,
  which sends emails via an SMTP server and posts a corresponding tweet on a provided Twitter account.
  
  You can find the complete https://github.com/debezium/debezium-examples/tree/master/camel-component[source code] of the example on GitHub.
  
  === Topology
  
  There are multiple components in the solution topology:
  
  [.centered-image.responsive-image]
  ====
  ++++
  <img src="/images/camel-component-topology.svg" style="max-width:100%;" class="responsive-image">
  ++++
  *Figure 1. The Deployment Topology*
  ====
  
  * The Q & A application is implemented using the https://quarkus.io/[Quarkus] stack and exposes a REST API to create questions and answers.
  * The application stores its data in the PostgreSQL database.
  * The Camel route runs as a plain Java application that uses an embedded https://infinispan.org/[Infinispan] store to persist its state (used to build an aggregate object linking questions to their answers) and sends messages to 
  * A https://github.com/mailhog/MailHog[MailHog] SMTP server running in a container as well as into an associated Twitter account.
  
  === Question & Answer Application
  
  The source application is a simple REST service based on Quarkus.
  It manages two entities, `Question` and `Answer`, with a `1:n` relation stored in the PostgreSQL database.
  
  [.centered-image.responsive-image]
  ====
  ++++
  <img src="/images/camel-component-erd.svg" style="max-width:100%;" class="responsive-image">
  ++++
  *Figure 2. The Q&A Backend Service Entity Relationship Diagram*
  ====
  
  The entities are created using REST API and the association is automatically established between them.
  
  === The Camel Pipeline
  
  The Camel pipeline is an expression of the following business rules:
  
  