Is there safety?
Posted: Sat Feb 08, 2025 9:41 am
Client nodes inject data streams into caching cores using Ignite Data Streamers;
data is automatically split between Ignite data nodes, and each node receives an equal amount of data;
Streaming data can be processed simultaneously directly on Ignite data nodes located in cells;
Clients can also execute parallel SQL queries on streaming data.
What are the alternatives on the market?
There is no breakthrough as such, there are similar products that have long used in-memory computing. For example: IMDG/IMCG products VMware Gemfire, Oracle Coherence, Alachisoft Ncache, Gigaspaces XAP Elastic Caching Edition, Hazelcast, Scaleout StateServer, IBM WebSphere eXtreme Scale, Terracotta Enterprise Suite, JBoss Infinispan.
Among the most successful players in the IMDM field are SAP (Hana and Sybase IQ), Oracle, IBM, Altibase, Tableau, Qliktech and Software AG. I have encountered solutions based on SAP Hana at many customers (in the retail sector, at financial institutions) - in contrast to GridGain, which is popular only at one large bank.
Conclusions about the popularity of a particular DB and technology can be made based on the DB ratings from db-engines as of August 2018: general for all types of DB (Fig. 7), for relational DB (Fig. 8) and for key-value DB (Fig. 9). It is also quite interesting to look at the history of queries for GridGain in the search engine - the topic is most popular in the Russian Federation (Fig. 10).
How is GridGain security? It's even simpler here: there is only one link on the manufacturer's website. It turns out that GridGain Enterprise Edition differs from Apache Ignite not only in the availability of technical support, error correction, and Enterprise Features, but also in the mechanisms for ensuring information security.
What information security mechanisms does GridGain offer?
Encryption. GridGain supports SSL/TLS hungary mobile database of data between its nodes, the main SSL/TLS encryption algorithms that were described for Java JDK 7 are supported.
Access control.
GridGain supports authentication and authorization of GridGain users and nodes using login/password or Java Authentication and Authorization (JAAS) service, compatible with JNDI, LDAP, Active Directory directories. Other more secure authentication options are also available by modifying the code itself, for example, using certificates, one-time passwords, tokens, access keys.
Permissions — access rights to the system, tasks, and cache level. In GridGain, restrictions can be set up for any operations — reading, writing data, administering (put, get, remove, close, or task), querying, and viewing data — right down to the cache. This will allow you to properly delimit access in GridGain, for example, to different IS, data, or companies (tenants) using one GridGain.
data is automatically split between Ignite data nodes, and each node receives an equal amount of data;
Streaming data can be processed simultaneously directly on Ignite data nodes located in cells;
Clients can also execute parallel SQL queries on streaming data.
What are the alternatives on the market?
There is no breakthrough as such, there are similar products that have long used in-memory computing. For example: IMDG/IMCG products VMware Gemfire, Oracle Coherence, Alachisoft Ncache, Gigaspaces XAP Elastic Caching Edition, Hazelcast, Scaleout StateServer, IBM WebSphere eXtreme Scale, Terracotta Enterprise Suite, JBoss Infinispan.
Among the most successful players in the IMDM field are SAP (Hana and Sybase IQ), Oracle, IBM, Altibase, Tableau, Qliktech and Software AG. I have encountered solutions based on SAP Hana at many customers (in the retail sector, at financial institutions) - in contrast to GridGain, which is popular only at one large bank.
Conclusions about the popularity of a particular DB and technology can be made based on the DB ratings from db-engines as of August 2018: general for all types of DB (Fig. 7), for relational DB (Fig. 8) and for key-value DB (Fig. 9). It is also quite interesting to look at the history of queries for GridGain in the search engine - the topic is most popular in the Russian Federation (Fig. 10).
How is GridGain security? It's even simpler here: there is only one link on the manufacturer's website. It turns out that GridGain Enterprise Edition differs from Apache Ignite not only in the availability of technical support, error correction, and Enterprise Features, but also in the mechanisms for ensuring information security.
What information security mechanisms does GridGain offer?
Encryption. GridGain supports SSL/TLS hungary mobile database of data between its nodes, the main SSL/TLS encryption algorithms that were described for Java JDK 7 are supported.
Access control.
GridGain supports authentication and authorization of GridGain users and nodes using login/password or Java Authentication and Authorization (JAAS) service, compatible with JNDI, LDAP, Active Directory directories. Other more secure authentication options are also available by modifying the code itself, for example, using certificates, one-time passwords, tokens, access keys.
Permissions — access rights to the system, tasks, and cache level. In GridGain, restrictions can be set up for any operations — reading, writing data, administering (put, get, remove, close, or task), querying, and viewing data — right down to the cache. This will allow you to properly delimit access in GridGain, for example, to different IS, data, or companies (tenants) using one GridGain.