agura commented on code in PR #2409: URL: https://github.com/apache/ignite-3/pull/2409#discussion_r1285488840
########## README.md: ########## @@ -1 +1,102 @@ -# Apache Ignite 3.x +Apache Ignite 3.x +=== + +Apache Ignite 3 is a distributed database for high-performance computing with in-memory speed. + +* MULTI-TIER STORAGE: Ignite scales up and out across memory and disk. By default, Ignite operates in a pure in-memory mode. But, by toggling a single configuration setting, you can turn a cluster into a database that can grow beyond the cluster's memory capacity. Review Comment: Ignite 3 is not a multi-tier storage. Actually Ignite 2 too :) The tired storage was a part of Ignite 1 architecture. And I'm not sure that the in-memory mode is a default mode. ########## README.md: ########## @@ -1 +1,102 @@ -# Apache Ignite 3.x +Apache Ignite 3.x +=== + +Apache Ignite 3 is a distributed database for high-performance computing with in-memory speed. Review Comment: Copy&past from Ignite 2? :) I believe we should reconsider this statement, because, IMHO, the in-memory is not the main mode and is not the main use-case. ########## README.md: ########## @@ -1 +1,102 @@ -# Apache Ignite 3.x +Apache Ignite 3.x +=== + +Apache Ignite 3 is a distributed database for high-performance computing with in-memory speed. + +* MULTI-TIER STORAGE: Ignite scales up and out across memory and disk. By default, Ignite operates in a pure in-memory mode. But, by toggling a single configuration setting, you can turn a cluster into a database that can grow beyond the cluster's memory capacity. +* DISTRIBUTED SQL: Use Ignite as a traditional SQL database by leveraging JDBC drivers, ODBC drivers, or the native SQL APIs that are available for Java, C#, C++, Python, and other programming languages. Review Comment: I'm not sure, but we haven't Python client for now. ########## README.md: ########## @@ -1 +1,102 @@ -# Apache Ignite 3.x +Apache Ignite 3.x +=== + +Apache Ignite 3 is a distributed database for high-performance computing with in-memory speed. + +* MULTI-TIER STORAGE: Ignite scales up and out across memory and disk. By default, Ignite operates in a pure in-memory mode. But, by toggling a single configuration setting, you can turn a cluster into a database that can grow beyond the cluster's memory capacity. +* DISTRIBUTED SQL: Use Ignite as a traditional SQL database by leveraging JDBC drivers, ODBC drivers, or the native SQL APIs that are available for Java, C#, C++, Python, and other programming languages. +* ACID TRANSACTIONS: Ignite can operate in a strongly consistent mode that provides full support for distributed ACID transactions. +* COMPUTE APIS: With traditional databases, for in-place calculations, you use stored procedures that are written in a language such as PL/SQL. With Ignite, you use modern JVM languages, C# or C++ to develop and execute custom tasks across your distributed database. +* MACHINE LEARNING: Ignite machine learning uses built-in algorithms and tools, as well as TensorFlow integration, to enable the building of scalable machine learning models and avoid costly data transfers. +* CONTINUOUS QUERIES: With relational databases, you use triggers to react to certain events. With Ignite, you deploy continuous queries that are written in a modern programming language such as Java or C# and process streams of changes on the database and application side. Review Comment: Not implemented yet. ########## README.md: ########## @@ -1 +1,102 @@ -# Apache Ignite 3.x +Apache Ignite 3.x +=== + +Apache Ignite 3 is a distributed database for high-performance computing with in-memory speed. + +* MULTI-TIER STORAGE: Ignite scales up and out across memory and disk. By default, Ignite operates in a pure in-memory mode. But, by toggling a single configuration setting, you can turn a cluster into a database that can grow beyond the cluster's memory capacity. +* DISTRIBUTED SQL: Use Ignite as a traditional SQL database by leveraging JDBC drivers, ODBC drivers, or the native SQL APIs that are available for Java, C#, C++, Python, and other programming languages. +* ACID TRANSACTIONS: Ignite can operate in a strongly consistent mode that provides full support for distributed ACID transactions. +* COMPUTE APIS: With traditional databases, for in-place calculations, you use stored procedures that are written in a language such as PL/SQL. With Ignite, you use modern JVM languages, C# or C++ to develop and execute custom tasks across your distributed database. +* MACHINE LEARNING: Ignite machine learning uses built-in algorithms and tools, as well as TensorFlow integration, to enable the building of scalable machine learning models and avoid costly data transfers. Review Comment: Just a copy&past from Apache Ignite 2 There is no any ML support in Apache Ignite 3 yet. ########## README.md: ########## @@ -1 +1,102 @@ -# Apache Ignite 3.x +Apache Ignite 3.x +=== + +Apache Ignite 3 is a distributed database for high-performance computing with in-memory speed. + +* MULTI-TIER STORAGE: Ignite scales up and out across memory and disk. By default, Ignite operates in a pure in-memory mode. But, by toggling a single configuration setting, you can turn a cluster into a database that can grow beyond the cluster's memory capacity. +* DISTRIBUTED SQL: Use Ignite as a traditional SQL database by leveraging JDBC drivers, ODBC drivers, or the native SQL APIs that are available for Java, C#, C++, Python, and other programming languages. +* ACID TRANSACTIONS: Ignite can operate in a strongly consistent mode that provides full support for distributed ACID transactions. +* COMPUTE APIS: With traditional databases, for in-place calculations, you use stored procedures that are written in a language such as PL/SQL. With Ignite, you use modern JVM languages, C# or C++ to develop and execute custom tasks across your distributed database. Review Comment: Only Java (or JVM based) for now. ########## README.md: ########## @@ -1 +1,102 @@ -# Apache Ignite 3.x +Apache Ignite 3.x Review Comment: Do we really need ".x" here? ########## README.md: ########## @@ -1 +1,102 @@ -# Apache Ignite 3.x +Apache Ignite 3.x +=== + +Apache Ignite 3 is a distributed database for high-performance computing with in-memory speed. + +* MULTI-TIER STORAGE: Ignite scales up and out across memory and disk. By default, Ignite operates in a pure in-memory mode. But, by toggling a single configuration setting, you can turn a cluster into a database that can grow beyond the cluster's memory capacity. +* DISTRIBUTED SQL: Use Ignite as a traditional SQL database by leveraging JDBC drivers, ODBC drivers, or the native SQL APIs that are available for Java, C#, C++, Python, and other programming languages. +* ACID TRANSACTIONS: Ignite can operate in a strongly consistent mode that provides full support for distributed ACID transactions. Review Comment: It's true, at least for Apache Ignite 3 :) I think we should emphasize a serializable transaction isolation level here. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
