Date: Fri, 29 Mar 2024 04:27:21 +0000 (UTC)
Message-ID: <1008957871.560.1711686441579@cwiki-he-fi.apache.org>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_559_1980323615.1711686441579"
------=_Part_559_1980323615.1711686441579
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
How do the direct, event, seda and vm endpoints compare
How do the direct, event, seda and vm endpoints compare
How do the direct, event, seda and v=
m endpoints compare?
- VM and SEDA endpoints are basically the same; they bot=
h offer asychronous in memory SEDA queues; they differ in visibility endpoi=
nts are visible inside the same JVM or within the same CamelContext respect=
ively.
- Direct uses no threadi=
ng; it directly invokes the consumer when sending.
- Spring Event add=
s a listener to Spring's application events; so the consumer is invoked the=
same thread as Spring notifies events. Event differs in that the payload s=
hould be a Spring ApplicationEvent object whereas Direct, =
SEDA and VM can use any pa=
yload
------=_Part_559_1980323615.1711686441579--