Apache
/
activemq-artemis
mirror of https://github.com/apache/activemq-artemis.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

This closes #1342

This commit is contained in:
Martyn Taylor 2017-06-19 10:04:13 +01:00
parent a5beec7e25 060781d430
commit 487cc45425
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/user-manual/en/perf-tuning.md
View File

@ -6,7 +6,7 @@ performance.
## Tuning persistence ## Tuning persistence
- To get the best performance from Apache ActiveMQ Artemis whilst - To get the best performance from Apache ActiveMQ Artemis whilst
using perisistent messages it is recommended that the file store using persistent messages it is recommended that the file store
is used. Apache ActiveMQ Artemis also supports JDBC persistence, is used. Apache ActiveMQ Artemis also supports JDBC persistence,
but there is a performance cost when persisting to a database vs but there is a performance cost when persisting to a database vs
local disk. local disk.

2
docs/user-manual/en/rest.md
View File

@ -5,7 +5,7 @@ scalability features of Apache ActiveMQ Artemis over a simple REST/HTTP interfac
The REST Interface implementation sits on top of an Apache ActiveMQ Artemis JMS API and The REST Interface implementation sits on top of an Apache ActiveMQ Artemis JMS API and
as such exposes JMS like concepts via REST. as such exposes JMS like concepts via REST.
Using the REST internface Messages can produced and consumed by sending Using the REST interface Messages can be produced and consumed by sending
and receiving simple HTTP messages that contain the content you want to push around. For instance, and receiving simple HTTP messages that contain the content you want to push around. For instance,
here's a simple example of posting an order to an order processing queue here's a simple example of posting an order to an order processing queue
express as an HTTP message: express as an HTTP message: