You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by mtod <mt...@thetods.net> on 2017/04/28 20:01:45 UTC
Artemis production ready?
Is Artemis production ready?
I have ActiveMQ 5.10 in production today but our infrastructure is moving to
AWS and global ( US and Europe).
I would like to upgrade from a single on prem cluster to a 2 failover
cluster model with a network connector across the pond.
before I spend all the cycles I would like to know if Artemis is used in
production today.
Thanks
Mike
--
View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-production-ready-tp4725363.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Artemis production ready?
Posted by Clebert Suconic <cl...@gmail.com>.
Just as a FYI: I'm having a last issue that I'm asking help for on the
dev-list.. I will start the voting and build the artifacts as soon as
I get past that:
http://activemq.2283324.n4.nabble.com/DISCUSS-HELP-Help-with-ArtemisFeatureTest-tp4725403.html
On Thu, May 4, 2017 at 1:31 PM, Clebert Suconic
<cl...@gmail.com> wrote:
> I will call it 2.1 as it has a few features included. Adding feature means
> bump it. Only fix is minor.
>
>
> But it's totally compatible with 2.0.
>
>
> On Thu, May 4, 2017 at 1:30 PM Clebert Suconic <cl...@gmail.com>
> wrote:
>>
>> There is a pending PR that I am waiting maven central to sync with the
>> required component.
>>
>> I will start it tonight if everything ok.
>>
>>
>> On Thu, May 4, 2017 at 1:13 PM mtod <mt...@thetods.net> wrote:
>>>
>>> The filtering or routing could be a camel microservice (I have this
>>> working
>>> on docker AWS today) or I can work up something using the
>>> https://activemq.apache.org/artemis/docs/1.0.0/wildcard-routing.html
>>>
>>> Our current ActiveMQ uses a Camel content router for managing queue to
>>> topics. We setup a single input queue for each application then use camel
>>> to
>>> route the messages based on a route element in the message header. This
>>> keeps the number of application connections down and in case of a queue
>>> corruption should not affect other consumers. We are using ActiveMQ in an
>>> event based message model today.
>>>
>>> But the final method is still an open question.
>>>
>>> I'm still working on getting the architectural model up and running so I
>>> can
>>> refine the routing and security requirements.
>>>
>>> btw when will the 2.0.1 release be out?
>>>
>>> Thanks
>>>
>>> Mike
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://activemq.2283324.n4.nabble.com/Artemis-production-ready-tp4725363p4725618.html
>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>> --
>> Clebert Suconic
>
> --
> Clebert Suconic
--
Clebert Suconic
Re: Artemis production ready?
Posted by Clebert Suconic <cl...@gmail.com>.
I will call it 2.1 as it has a few features included. Adding feature means
bump it. Only fix is minor.
But it's totally compatible with 2.0.
On Thu, May 4, 2017 at 1:30 PM Clebert Suconic <cl...@gmail.com>
wrote:
> There is a pending PR that I am waiting maven central to sync with the
> required component.
>
> I will start it tonight if everything ok.
>
>
> On Thu, May 4, 2017 at 1:13 PM mtod <mt...@thetods.net> wrote:
>
>> The filtering or routing could be a camel microservice (I have this
>> working
>> on docker AWS today) or I can work up something using the
>> https://activemq.apache.org/artemis/docs/1.0.0/wildcard-routing.html
>>
>> Our current ActiveMQ uses a Camel content router for managing queue to
>> topics. We setup a single input queue for each application then use camel
>> to
>> route the messages based on a route element in the message header. This
>> keeps the number of application connections down and in case of a queue
>> corruption should not affect other consumers. We are using ActiveMQ in an
>> event based message model today.
>>
>> But the final method is still an open question.
>>
>> I'm still working on getting the architectural model up and running so I
>> can
>> refine the routing and security requirements.
>>
>> btw when will the 2.0.1 release be out?
>>
>> Thanks
>>
>> Mike
>>
>>
>>
>> --
>> View this message in context:
>> http://activemq.2283324.n4.nabble.com/Artemis-production-ready-tp4725363p4725618.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
> --
> Clebert Suconic
>
--
Clebert Suconic
Re: Artemis production ready?
Posted by Clebert Suconic <cl...@gmail.com>.
There is a pending PR that I am waiting maven central to sync with the
required component.
I will start it tonight if everything ok.
On Thu, May 4, 2017 at 1:13 PM mtod <mt...@thetods.net> wrote:
> The filtering or routing could be a camel microservice (I have this working
> on docker AWS today) or I can work up something using the
> https://activemq.apache.org/artemis/docs/1.0.0/wildcard-routing.html
>
> Our current ActiveMQ uses a Camel content router for managing queue to
> topics. We setup a single input queue for each application then use camel
> to
> route the messages based on a route element in the message header. This
> keeps the number of application connections down and in case of a queue
> corruption should not affect other consumers. We are using ActiveMQ in an
> event based message model today.
>
> But the final method is still an open question.
>
> I'm still working on getting the architectural model up and running so I
> can
> refine the routing and security requirements.
>
> btw when will the 2.0.1 release be out?
>
> Thanks
>
> Mike
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Artemis-production-ready-tp4725363p4725618.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
Clebert Suconic
Re: Artemis production ready?
Posted by mtod <mt...@thetods.net>.
The filtering or routing could be a camel microservice (I have this working
on docker AWS today) or I can work up something using the
https://activemq.apache.org/artemis/docs/1.0.0/wildcard-routing.html
Our current ActiveMQ uses a Camel content router for managing queue to
topics. We setup a single input queue for each application then use camel to
route the messages based on a route element in the message header. This
keeps the number of application connections down and in case of a queue
corruption should not affect other consumers. We are using ActiveMQ in an
event based message model today.
But the final method is still an open question.
I'm still working on getting the architectural model up and running so I can
refine the routing and security requirements.
btw when will the 2.0.1 release be out?
Thanks
Mike
--
View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-production-ready-tp4725363p4725618.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Artemis production ready?
Posted by Clebert Suconic <cl...@gmail.com>.
On Mon, May 1, 2017 at 10:57 AM, Mike Tod <mt...@foundationmedicine.com> wrote:
> One failover cluster in the AWS US instance another failover cluster in the AWS Europe instance (more specifically the German instance) then connect both and filter by region to keep local traffic within the region.
How would you do the filter? HTTP and local connection?
I think it can be done... however I would of course test your
solution. Let us know how it goes and if you need help eventually.
>
> -----Original Message-----
> From: Justin Bertram [mailto:jbertram@apache.org]
> Sent: Friday, April 28, 2017 3:49 PM
> To: users@activemq.apache.org
> Subject: Re: Artemis production ready?
>
> When you say "across the pond" what exactly are you referring to? Also, when you say you're going to run two 2-node clusters wouldn't that just be a 4-node cluster?
>
>
> Justin
>
> ----- Original Message -----
> From: "mtod" <mt...@thetods.net>
> To: users@activemq.apache.org
> Sent: Friday, April 28, 2017 4:26:10 PM
> Subject: Re: Artemis production ready?
>
> Thanks everyone for the responses that helps.
>
> For the support model we have been running ActiveMQ in production for 4 years I'm very happy with the performance. I know there are several 3rd parties that if I need to add a support model they would be happy to sign a contract. :)
>
> I plan on setting up 2-2 node clusters and connecting them across the pond and stress test the solution.
>
>
> Mike
>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-production-ready-tp4725363p4725368.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
> This communication and any files transmitted with it may contain information that is considered to be confidential, privileged and exempt from disclosure under applicable law. This message is intended for Foundation Medicine-affiliated use and that of the intended recipient only and may contain information that is protected by Foundation Medicine policies and the HIPAA Privacy Rule, 45 CFR § 164.500. This communication is intended solely for the use of intended recipient. If you are not the intended recipient, you are hereby notified that any use, dissemination or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately and delete this message immediately. Thank you for your cooperation.
--
Clebert Suconic
RE: Artemis production ready?
Posted by Mike Tod <mt...@foundationmedicine.com>.
One failover cluster in the AWS US instance another failover cluster in the AWS Europe instance (more specifically the German instance) then connect both and filter by region to keep local traffic within the region.
-----Original Message-----
From: Justin Bertram [mailto:jbertram@apache.org]
Sent: Friday, April 28, 2017 3:49 PM
To: users@activemq.apache.org
Subject: Re: Artemis production ready?
When you say "across the pond" what exactly are you referring to? Also, when you say you're going to run two 2-node clusters wouldn't that just be a 4-node cluster?
Justin
----- Original Message -----
From: "mtod" <mt...@thetods.net>
To: users@activemq.apache.org
Sent: Friday, April 28, 2017 4:26:10 PM
Subject: Re: Artemis production ready?
Thanks everyone for the responses that helps.
For the support model we have been running ActiveMQ in production for 4 years I'm very happy with the performance. I know there are several 3rd parties that if I need to add a support model they would be happy to sign a contract. :)
I plan on setting up 2-2 node clusters and connecting them across the pond and stress test the solution.
Mike
--
View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-production-ready-tp4725363p4725368.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
This communication and any files transmitted with it may contain information that is considered to be confidential, privileged and exempt from disclosure under applicable law. This message is intended for Foundation Medicine-affiliated use and that of the intended recipient only and may contain information that is protected by Foundation Medicine policies and the HIPAA Privacy Rule, 45 CFR § 164.500. This communication is intended solely for the use of intended recipient. If you are not the intended recipient, you are hereby notified that any use, dissemination or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately and delete this message immediately. Thank you for your cooperation.
Re: Artemis production ready?
Posted by Justin Bertram <jb...@apache.org>.
When you say "across the pond" what exactly are you referring to? Also, when you say you're going to run two 2-node clusters wouldn't that just be a 4-node cluster?
Justin
----- Original Message -----
From: "mtod" <mt...@thetods.net>
To: users@activemq.apache.org
Sent: Friday, April 28, 2017 4:26:10 PM
Subject: Re: Artemis production ready?
Thanks everyone for the responses that helps.
For the support model we have been running ActiveMQ in production for 4
years I'm very happy with the performance. I know there are several 3rd
parties that if I need to add a support model they would be happy to sign a
contract. :)
I plan on setting up 2-2 node clusters and connecting them across the pond
and stress test the solution.
Mike
--
View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-production-ready-tp4725363p4725368.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Artemis production ready?
Posted by mtod <mt...@thetods.net>.
Thanks everyone for the responses that helps.
For the support model we have been running ActiveMQ in production for 4
years I'm very happy with the performance. I know there are several 3rd
parties that if I need to add a support model they would be happy to sign a
contract. :)
I plan on setting up 2-2 node clusters and connecting them across the pond
and stress test the solution.
Mike
--
View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-production-ready-tp4725363p4725368.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Artemis production ready?
Posted by Justin Bertram <jb...@apache.org>.
For what it's worth, Artemis is based on HornetQ which has been deployed in production for years by users of JBoss AS, Wildfly, and Red Hat JBoss Enterprise Application Platform.
Substantial improvements have been made to the code-base since the donation to Apache including (among others) OpenWire, AMQP, & MQTT support, JDBC storage support, lots of usability improvements, etc. As far as I'm aware all functionality is designed for production use.
Justin
----- Original Message -----
From: "mtod" <mt...@thetods.net>
To: users@activemq.apache.org
Sent: Friday, April 28, 2017 3:01:45 PM
Subject: Artemis production ready?
Is Artemis production ready?
I have ActiveMQ 5.10 in production today but our infrastructure is moving to
AWS and global ( US and Europe).
I would like to upgrade from a single on prem cluster to a 2 failover
cluster model with a network connector across the pond.
before I spend all the cycles I would like to know if Artemis is used in
production today.
Thanks
Mike
--
View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-production-ready-tp4725363.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Artemis production ready?
Posted by Clebert Suconic <cl...@gmail.com>.
Although I must emphasize the Apache license*.
If you need extra warranties you probably need a company supporting you **
* https://www.apache.org/licenses/LICENSE-2.0.html
7. Disclaimer of Warranty. Unless required by applicable law or agreed to
in writing, Licensor provides the Work (and each Contributor provides its
Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied, including, without limitation, any
warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or
FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for
determining the appropriateness of using or redistributing the Work and
assume any risks associated with Your exercise of permissions under this
License.
** http://activemq.apache.org/support.html
On Fri, Apr 28, 2017 at 4:21 PM Clebert Suconic <cl...@gmail.com>
wrote:
> I know of a few large deployments using 1.5.4.
>
>
>
> I have myself done a lot of testing using production similar (actually
> worse than production) testcases.
>
> You have to actually as with any new system check your configurations and
> do your testing. But I wouldn't release something under Apache where I
> wouldn't mean production ready.
>
>
> For 2.0 there will be a 2.1 next week. Very safe.
>
>
>
> On Fri, Apr 28, 2017 at 4:13 PM mtod <mt...@thetods.net> wrote:
>
>> Is Artemis production ready?
>>
>> I have ActiveMQ 5.10 in production today but our infrastructure is moving
>> to
>> AWS and global ( US and Europe).
>>
>> I would like to upgrade from a single on prem cluster to a 2 failover
>> cluster model with a network connector across the pond.
>>
>> before I spend all the cycles I would like to know if Artemis is used in
>> production today.
>>
>> Thanks
>>
>> Mike
>>
>>
>>
>> --
>> View this message in context: http://activemq.2283324.n4.nab
>> ble.com/Artemis-production-ready-tp4725363.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
> --
> Clebert Suconic
>
Re: Artemis production ready?
Posted by Clebert Suconic <cl...@gmail.com>.
I know of a few large deployments using 1.5.4.
I have myself done a lot of testing using production similar (actually
worse than production) testcases.
You have to actually as with any new system check your configurations and
do your testing. But I wouldn't release something under Apache where I
wouldn't mean production ready.
For 2.0 there will be a 2.1 next week. Very safe.
On Fri, Apr 28, 2017 at 4:13 PM mtod <mt...@thetods.net> wrote:
> Is Artemis production ready?
>
> I have ActiveMQ 5.10 in production today but our infrastructure is moving
> to
> AWS and global ( US and Europe).
>
> I would like to upgrade from a single on prem cluster to a 2 failover
> cluster model with a network connector across the pond.
>
> before I spend all the cycles I would like to know if Artemis is used in
> production today.
>
> Thanks
>
> Mike
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Artemis-production-ready-tp4725363.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
Clebert Suconic