You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis A. Magda (Jira)" <ji...@apache.org> on 2020/11/30 23:07:00 UTC
[jira] [Updated] (IGNITE-13780) Ignite Website: update use cases
section
[ https://issues.apache.org/jira/browse/IGNITE-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis A. Magda updated IGNITE-13780:
------------------------------------
Description:
Presently, the website introduces 2 use cases of Ignite - "Ignite as a cache" and "Ignite as a digital integration hub". After defining Ignite as a distributed database, we need to update this website section featuring the following 3 primary usage scenarios of Ignite.
*How Most Developers Use Apache Ignite*
1. _Applications Acceleration & Data Caching_
Gain up to 100x acceleration for existing applications using Ignite as an in-memory cache over a single or multiple backend systems. The cache that you can query with SQL, transact and compute on.
2. _Distributed Database for Mixed Workloads_
Store and process petabytes of operational and historical data using Ignite as a distributed database for mixed workloads. The database that scales up and out across available memory, disk, and Intel Optane storage.
3. _High-Performance Compute Cluster_
Deploy and execute your kilobyte-size code over petabytes of data. Turn your Ignite cluster into a limitless supercomputer for low-latency calculations, complex analytics, and machine learning.
was:
Presently, the website introduces 2 use cases of Ignite - "Ignite as a cache" and "Ignite as a digital integration hub". After defining Ignite as a distributed database, we need to update this website section featuring the following 3 primary usage scenarios of Ignite.
*How Most Developers Use Apache Ignite*
_Applications Acceleration & Data Caching_
Gain up to 100x acceleration for existing applications using Ignite as an in-memory cache over a single or multiple backend systems. The cache that you can query with SQL, transact and compute on.
*Distributed Database for Mixed Workloads*
Store and process petabytes of operational and historical data using Ignite as a distributed database for mixed workloads. The database that scales up and out across available memory, disk, and Intel Optane storage.
_High-Performance Compute Cluster_
Deploy and execute your kilobyte-size code over petabytes of data. Turn your Ignite cluster into a limitless supercomputer for low-latency calculations, complex analytics, and machine learning.
> Ignite Website: update use cases section
> ----------------------------------------
>
> Key: IGNITE-13780
> URL: https://issues.apache.org/jira/browse/IGNITE-13780
> Project: Ignite
> Issue Type: Sub-task
> Components: website
> Reporter: Denis A. Magda
> Assignee: Denis A. Magda
> Priority: Critical
>
> Presently, the website introduces 2 use cases of Ignite - "Ignite as a cache" and "Ignite as a digital integration hub". After defining Ignite as a distributed database, we need to update this website section featuring the following 3 primary usage scenarios of Ignite.
> *How Most Developers Use Apache Ignite*
> 1. _Applications Acceleration & Data Caching_
> Gain up to 100x acceleration for existing applications using Ignite as an in-memory cache over a single or multiple backend systems. The cache that you can query with SQL, transact and compute on.
> 2. _Distributed Database for Mixed Workloads_
> Store and process petabytes of operational and historical data using Ignite as a distributed database for mixed workloads. The database that scales up and out across available memory, disk, and Intel Optane storage.
> 3. _High-Performance Compute Cluster_
> Deploy and execute your kilobyte-size code over petabytes of data. Turn your Ignite cluster into a limitless supercomputer for low-latency calculations, complex analytics, and machine learning.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)