Thanks for all the answers. It sounds like I can't quite achieve what I
want out of the box. (Which is not a surprise)
I'll have a look at the internal code and see how hard it will be to build
something custom that is basically a combination of a small non-persistent
in-memory queue, and a larger
On 26 January 2018 at 20:58, Clebert Suconic
wrote:
> With artemis you can simply disable syncs on producer and you would get
> similar performance numbers. Usually people turn of persistence to gain
>
Ah, it's not perf I'm after, think of this as a kind of IOT/sensor device,
I want to preserve
On Fri, 26 Jan 2018 at 19:22, Tim Bain wrote:
>
> 5.x can also do in-memory-till-full-then-spool-to-disk when using
> non-persistent messages (which go to the memory store and then to the temp
> store if the memory store is full).
>
That’s useful info thanks. But non persistent means that the br
On Fri, 26 Jan 2018 at 17:59, Justin Bertram wrote:
>
> If you're asking about ActiveMQ, can you clarify if you're asking about the
> 5.x or Artemis broker?
>
I’ve only just started looking at tech options, so I don’t even know what
those are. I assume different forks of active mq?
eated with a
plugin?
For context, the requirement is slightly weird in that I'm
(a) wanting to push some data back over a flakey WAN
(b) from an underpowered piece of hardware that doesn't like it's little SSD
drive being written too hard
:-)
Thanks, Noel Grandin
