Am I right in saying that Gridgain visor and Wan replication can only be used on an Enterprise subscription?
http://www.gridgain.org/support/ suggests they are.
Thanks
Datacenter Replication (DR) and GUI-based Visor management are part of enterprise edition.
However, GridGain Command Line Visor management (http://atlassian.gridgain.com/wiki/display/GG60/Command+Line+Interface) is part of open source edition.
Additionally, some of the other cool features provided as open source include different language connectivity (like C++, C#, HTTP), and off-heap storage.
Related
I am a little confused by the JOOQ product compatibility with AWS RDS Aurora MySQL.
Perhaps this purely a licence restriction rather than technical one.
This page https://www.jooq.org/legal/licensing#databases shows RDS Aurora support in Professional Edition & Enterprise Edition. The "License Terms" section on https://www.jooq.org/download/ show that the open source version does not allow for commercial databases and only allows for open source ones.
My question is:
Can anyone confirm that this is actually a licence usage terms restriction, rather than a technical one with the open source code, e.g. it's not that when using the professional edition one actually would run a different flavour of JOOQ, e.g. a different binary with more features?
Purely for bonus points & general interest:
We can see in this commit https://github.com/jOOQ/jOOQ/commit/863ade3b3c7a004d477d54193ac5104435b9835b and in this github issue https://github.com/jOOQ/jOOQ/issues/5196 dating back to 2018 support was added to the open source project.
Given AWS generally refer to the Aurora product as being compatible with mysql 5.7, why would JOOQ need to do anything at all to "support" this, shouldn't it "just" look like using MySQL 5.7 from the perspective of a client application? https://aws.amazon.com/rds/aurora/faqs/ Perhaps the critical word below is "most".
most of the code, applications, drivers and tools you already use today with your MySQL databases can be used with Aurora with little or no change. The Amazon Aurora database engine is designed to be wire-compatible with MySQL 5.6 and 5.7 using the InnoDB storage engine.
Lukas from the jOOQ team here.
The "License Terms" section on https://www.jooq.org/download/ show that the open source version does not allow for commercial databases and only allows for open source ones.
Perhaps that section title "License Terms" is misleading for this particular purpose (which we'll review). There's no way for the jOOQ Open Source Edition to not allow you to use the jOOQ Open Source Edition with any database product of your choice. The ASL 2.0, which is the license governing the jOOQ Open Source Edition, does not allow for any such "amendments" or restrictions on top of the ASL 2.0 - otherwise it would no longer be the ASL 2.0 license.
What this website section means is that the jOOQ Open Source Edition does not technically support any other databases than the ones listed there, nor do we offer any support for such an integration as a vendor, but if you can get it to work (through patching, integration testing, etc.) you're free to do so.
Can anyone confirm that this is actually a licence usage terms restriction, rather than a technical one with the open source code, e.g. it's not that when using the professional edition one actually would run a different flavour of JOOQ, e.g. a different binary with more features?
There is no "license usage term restriction" whatsoever in the jOOQ Open Source Edition, apart from the ASL 2.0
Given AWS generally refer to the Aurora product as being compatible with mysql 5.7, why would JOOQ need to do anything at all to "support" this, shouldn't it "just" look like using MySQL 5.7 from the perspective of a client application?
We as a vendor will give you warranties and commercial support, as well as maintenance on your Aurora MySQL integration when you use jOOQ's Aurora MySQL support.
In case you do run into one of those cases where Aurora MySQL doesn't work exactly like vanilla MySQL, we'll fix (or may already have fixed) the issue for Aurora MySQL only, not affecting other MySQL users.
What architecture and application development best practices must be followed in order to scale a TWX application?
The majority of applications start with few devices but with time they quickly build up to thousands of devices. Once the amount of traffic is too much for one TWX instance what strategy should be followed?
The same question applies when the front end is overwhelmed by the number of users.
Anytime I have had ThingWorx architecture concerns, I have been redirected to the PTC ThingWorx guide linked below. I do not believe you need a PTC account to view it, but if so it is free.
ThingWorx 8 High Availability Administrators Guide
http://support.ptc.com/WCMS/files/173281/en/ThingWorx_8_High_Availability_Administrators_Guide.pdf
In your case where you have big load concerns, the guide recommends using
two ThingWorx instances to handle the load.
At least two ThingWorx instances are required for HA configuration. A
single instance is started, which becomes leader and fully connects to
the database. Standby servers boot up and can become the leader if
needed, but they do not fully connect to the database or load
information like the leader does. All ThingWorx servers have a service
that is called by the load balancer, which indicates their
availability. Different codes identify the leader, which receives
traffic, and standby nodes, which do not receive traffic but may
become leader.
High-Level Architecture example from the referenced guide:
The Load Balancer determines which ThingWorx instance is to be used by the user. Usually it is used to determine which is available in a redundant architecture (which is what makes it Highly Available). However, it can also be used to determine which to use based on performance. In PTC's HA Admin Guide, they use HAProxy (see page 47) as the Load Balancer. See Section 3.2 of the HAProxy Config Doc for how to configure based on performance.
Hope this helps! It is a pretty open-ended topic
With ThingWorx 9.0 release, the ThingWorx Foundation platform supports true horizontal scalability with an active-active clustering setup providing no single points of failure. The document here provides the details about the install and setup.
There is also a ThingWorx 9.0 deployment architecture guide for an overview of all the architectural details.
ThingWorx High Availability Clustering setup image
I have a question regarding Hazelcast community edition.
If I form a cluster consisting of 2 hosts [1 in NY data center,1 in NJ data center] but in NA region only, is it possible to use replication or even for that we are required to go for Enterprise edition?
If yes, could you guide me how we can achieve that for Maps?
Thanks,
Dharam
Hazelcast Wan Replication is available in the Community Edition but some of the fancy features are not available unless you go with Enterprise. You also lose out on Management Center to monitor the clusters. Depending on your needs you may be able to get away with Community Edition and write your own custom monitoring.
As DataStax will discontinue the OpsCenter (http://docs.datastax.com/en/opscenter/5.2/opsc/opscPolicyChanges.html), which was rather okay for monitoring purposes and the daily management tasks,
I'm searching for a valid alternative. The list of tools under http://www.planetcassandra.org/related-projects/ does not really look attractive.
Is there a meaningful or even better way? OpsCenter already had very limited functionality for OSS. Any recommendations?
Cassandra exposes own metrics via JMX, so you can use any tool that is able to collect JMX data.
On production environment we are using Zabbix for monitoring purposes.
Also we looked at Graphite but we chose Zabbix because it is our "corporate standard"
Is there an advantage to using one or the classes to execute statement in a .Net application. As a .Net developer using CqlConnection and CqlCommand is very similar what is done for other dbs (like SqlServer). I read on some web sites that Cluster and Session is a better way to go.
The documentation in DataStax does not describe the differences or any suggestions of which to use under what circumstances.
Thanks
Use the cluster and session objects in the DataStax driver
DataStax drivers provide critical functionality for enterprise cassandra apps, including configurable load balancing policies, automatic failover, retry policy, and tunability. These features are exposed via the cluster and session objects.
Notice that CqlConnection and CqlCommand are not even mentioned in the DataStax documentation. This is because they are used under the hood by the driver.
You can certainly use these to connect and read/write to cassandra but you will be missing out on the features I mentioned.
Pro Tip: Check the code comments here to see the functionality of the Cluster object. DataStax drivers are Open Source so feel free to go code diving!