I want to know about ejabberd is free or not, because I want to decide from openfire and ejabberd before started development of application
There are two versions of ejabberd: eCS and eBE. The former is a "community server" and is licensed under GPL. The latter is a "business edition" and has a commercial license.
Related
Question is above. I read that you have to pay for this service and now I want to cancel it. Is that possible? Or am I wrong and it is actually for free? I also tried deleting it but I keep getting the message that I can't install multiple versions.
If you are not a MongoDB customer, your use of MongoDB Enterprise Server is governed by the customer agreement that is presented during the download process (e.g. here). This agreement says:
(b) Free Evaluation and Development. MongoDB grants you a royalty-free, nontransferable and nonexclusive license to use and reproduce the Software in your internal environment for evaluation and development purposes. You will not use the Software for any other purpose, including testing, quality assurance or production purposes without purchasing an Enterprise Advanced Subscription. We provide the free evaluation and development license of our Software on an “AS-IS” basis without any warranty.
You may use the product indefinitely as long as you are using it for "evaluation and development purposes".
You can also uninstall the enterprise server at any time and install the community one.
I'm about to start deploying to production a couple of Kafka cluster in 2 different DCs. My main use is for replication using MirrorMaker. To continuously stream/replicate ElasticSearch and Postgres between DCs in order to have a (near) real-time backup and failover.
What I can't get my head around is this simplest question: should I use Confluent or apache Kafka?
I can see that Confluent adds many niceties but what I don't get it: why would someone pick plain Apache Kafka then? I've seen this answer and it seems clear: "pick Confluent, has way more stuff".
As answered in linked post, you can add whatever external processes you want to Apache Kafka.
Note: You are not picking either or, you are always picking Apache Kafka. Confluent Platform adds on top of, similar to Cloudera's Data Platform, as an alternative consideration.
If you want to connect Elasticsearch and Postgres (via JDBC), both of those connectors are Open-Source under the Confluent Community License, so that would be one potential reason for not using Confluent products.
Other reason: Do you need the "more stuff"? Are you able to get support from elsewhere? For example, AWS support on MSK or IBM Streams or Azure EventHub are not using Confluent Platform (because it's against the above license)
MirrorMaker and MirrorMaker2 are both under the Apache License, so they have no such usage / redistribution restrictions.
should I use Confluent or apache Kafka?
When deciding on deploying a vanilla Apache or a commercially supported product you should think about the O&M (operation and maintenance) timeline and what you gain and lose. Whatever you choose will be very difficult to replace once in production.
I'll also agree with #OneCricketeer's answer.
Do you need the "more stuff"?
I work as a professional services consultant with some Apache products. My advice is keep your stack (whatever it is) as simple as possible. So if you don't need the additional tools and functionality of Confluent, don't use them. It's how they make the product "sticky" (re: vendor lock-in).
Vanilla Apache Kafka
Pro No vendor lock-in or dependencies
Pro Faster updates and feature development
Con No nice dashboards
Con Harder to secure
Confluent
Pro Commercial support and professional services available
Pro More stable with fast and easy security patches
Pro Nice dashboard and management tools
Pro Easier to properly secure
Con Expensive
Con Expect vendor lock-in and frequent up-sells
My Opinion
If you have money to spare and this will be a critical piece of infrastructure I'd recommend buying through Confluent. If you try to avoid paying for them, you'll have to hire someone (expensive) who knows it anyway and you'll have to deal with the patching nightmare of open source projects.
If this is something you want to kick the tires on, can allow for downtime, or think you'll replace in 2 years, I'd just use the Apache Kafka with one of the open source dashboards.
I am working on implementing business rules. We would like to evaluate different open source product for business rule engine. Could any one tell me is drools.net free or licenced?
Drools itself (java and other JVM languages) is Apache Licensed which is very permissive open source license (free to use, free to modify, etc), see "apache license layman explanation".
Drools.net (.NET, C# etc) I don't know - does that still exist? I see most .NET users calling the KIE Execution Server through REST to do rules.
I am exploring the possibility of using the community version of FUSE ESB in a production system for a period of one year. Is it possible? Can you please provide some advice here?
Just like RHEL, can I continue to use RedHat Jboss FUSE in production environment free of cost, without availing the support? If I understand correctly, the subscription is for support.
Have your legal team review the agreement. My understanding matches yours. There are no technical limiting factors (no registration keys, etc), and Fuse is free to use the software for development purposes, but production usage requires a subscription.
Your understanding is correct. The entitlement is for support, not product usage.
does anyone know how licensing works for JBoss Fuse in a DR environment - say for example we need an active AMQ container running in DR with replicated db, would this count towards the core licensing?
If so is there any way to have anything other than cold DR without a license impact.
Technically, JBoss Fuse is not licensed. One would purchase an entitlement/subscription from Red Hat. An entitlement allows access to both the software and technical support. There is a 'self-supported' entitlement that provides access to the documentation and the knowledge base and software, but does not include the ability to open a support case.
There is no restrictions on the number of deployments with an entitlement.
Doug