-
Notifications
You must be signed in to change notification settings - Fork 6
/
Copy pathdirect-publishing.html
25 lines (25 loc) · 1.8 KB
/
direct-publishing.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
<!DOCTYPE html>
<html>
<head>
<title>Eiffel | Sepia Implementation Architecture | Direct Publishing</title>
<meta name="theme-color" content="#ffffff">
<link rel="apple-touch-icon" sizes="180x180" href="./images/favicon/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="./images/favicon/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="./images/favicon/favicon-16x16.png">
<link rel="manifest" href="./manifest.json">
<link rel="mask-icon" href="./images/favicon/safari-pinned-tab.svg" color="#5bbad5">
<link rel='stylesheet' href='./css/index.css'>
<meta name="theme-color" content="#ffffff">
<script src="./js/csi.min.js"></script>
</head>
<body class="container">
<div data-include="includes/header.html"></div>
<section>
<div>
<h1 class="section-heading">Direct Publishing</h1>
<p class="section-paragraph">To publish Eiffel event data, actors may interface directly with the <a href="rabbitmq-message-broker.html">RabbitMQ Message Broker</a>. When doing so, the actor takes full responsibility for behaving as a <a href="https://www.rabbitmq.com/clients.html">RabbitMQ Client</a> and for authoring and serializing the JSON document constituting the event. For certain use cases this may be a preferable option, but the authoring and serialization of events can be non-trivial. In particular, the need to reference other events via UUID may require lookups using <a href="event-persistence.html">Event Persistence</a>. It is also worth noting that direct publishing requires library level RabbitMQ integration, whereas <a href="assisted-publishing.html">Assisted Publishing</a> offers REST API integration.</p>
</div>
</section>
<div data-include="includes/footer.html"></div>
</body>
</html>