Greetings, I can see this question has been asked in some form before, and recently. But I just wanted to clarify our use case and ask which version would be a better bet going into production in a few months. Some details:
* Client/service access is 99% via JMS, except for a few management methods (enumerate queues, get queue count) which we hit via Jolokia * Usage is 95% RPC (post to named queue, reply on temp queue) and 5% topics * AMQ has been working in test for many months. Artemis is being tested and we are shaking out a few semantic differences. * Our performance needs seem to be covered by both versions. * We don’t need HA yet. HA is on the roadmap for 2023. * We need persistence (so messages are not lost if broker is bounced) * We are in a Kubernetes pod environment. The broker itself *can* run in a separate VM if that is the preferred or more-stable configuration. We realize the Artemis is the future, so we are inclined that way if possible. In order to avoid opinion wars, I really just want to ask “what are the known risks” for the two options. Given that we are in K8S, does one have better K8S support/experience over the other? Secondary question: is it OK to deploy the broker in K8S pods, or is it better to use a dedicated VM? Thanks john [rg] <https://www.redpointglobal.com/> John Lilley Chief Architect, Redpoint Global Inc. 888 Worcester Street, Suite 200 Wellesley, MA 02482 M: +1 7209385761<tel:+1%207209385761> | john.lil...@redpointglobal.com<mailto:john.lil...@redpointglobal.com> PLEASE NOTE: This e-mail from Redpoint Global Inc. (“Redpoint”) is confidential and is intended solely for the use of the individual(s) to whom it is addressed. If you believe you received this e-mail in error, please notify the sender immediately, delete the e-mail from your computer and do not copy, print or disclose it to anyone else. If you properly received this e-mail as a customer, partner or vendor of Redpoint, you should maintain its contents in confidence subject to the terms and conditions of your agreement(s) with Redpoint.
