ignite-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dma...@apache.org
Subject svn commit: r1803118 - in /ignite/site/trunk: css/all.css scss/ignite.scss whatisignite.html
Date Wed, 26 Jul 2017 22:03:21 GMT
Author: dmagda
Date: Wed Jul 26 22:03:21 2017
New Revision: 1803118

URL: http://svn.apache.org/viewvc?rev=1803118&view=rev
Log:
updated what's ignite page

Modified:
    ignite/site/trunk/css/all.css
    ignite/site/trunk/scss/ignite.scss
    ignite/site/trunk/whatisignite.html

Modified: ignite/site/trunk/css/all.css
URL: http://svn.apache.org/viewvc/ignite/site/trunk/css/all.css?rev=1803118&r1=1803117&r2=1803118&view=diff
==============================================================================
--- ignite/site/trunk/css/all.css (original)
+++ ignite/site/trunk/css/all.css Wed Jul 26 22:03:21 2017
@@ -9084,6 +9084,7 @@ hr.vertical {
 
 #ignite-faq h2 {
   font-size: 22px;
+  padding-bottom: 10px;
 }
 
 .header {

Modified: ignite/site/trunk/scss/ignite.scss
URL: http://svn.apache.org/viewvc/ignite/site/trunk/scss/ignite.scss?rev=1803118&r1=1803117&r2=1803118&view=diff
==============================================================================
--- ignite/site/trunk/scss/ignite.scss (original)
+++ ignite/site/trunk/scss/ignite.scss Wed Jul 26 22:03:21 2017
@@ -1628,7 +1628,8 @@ hr.vertical {
 
 #ignite-faq {
     h2 {
-    font-size: 22px;
+        font-size: 22px;
+        padding-bottom: 10px;
     }
 }
 

Modified: ignite/site/trunk/whatisignite.html
URL: http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite.html?rev=1803118&r1=1803117&r2=1803118&view=diff
==============================================================================
--- ignite/site/trunk/whatisignite.html (original)
+++ ignite/site/trunk/whatisignite.html Wed Jul 26 22:03:21 2017
@@ -55,23 +55,22 @@ under the License.
             <h1 class="first">What is Ignite?</h1>
             <div class="col-sm-12 col-md-12 col-xs-12" style="padding: 0px;">
                 <div class="col-sm-6 col-md-6 col-xs-12" style="padding-left:0; padding-right:0">
-                    <p style="margin-bottom: 10px;"><b>Ignite is a memory-centric
platform</b></p>
+                    <p style="margin-bottom: 10px;"><b style="font-weight: 500">Ignite
is a memory-centric platform</b></p>
                     <ul class="page-list">
-                        <li>combining a <b>distributed SQL</b> database</li>
-                        <li>with a <b>key-value</b> data grid</li>
-                        <li>that is <b>ACID</b>-compliant</li>
-                        <li>and horizontally <b>scalable</b></li>
+                        <li>combining a <b style="font-weight: 500">distributed
SQL</b> database</li>
+                        <li>with a <b style="font-weight: 500">key-value</b>
data grid</li>
+                        <li>that is <b style="font-weight: 500">ACID</b>-compliant</li>
+                        <li>and horizontally <b style="font-weight: 500">scalable</b></li>
                     </ul>
-                    <div style="padding-top: 10px;">
-                        <h2 style="font-size: 22px;">Is Ignite a distributed database?</h2>
+                    <div style="padding-top: 10px;"><br/>
+                        <h2 style="font-size: 22px; padding-bottom: 10px;">Is Ignite
a distributed database?</h2>
                         <p>
-                            <b>Yes</b>. Data in Ignite is either partitioned
or replicated across a cluster of multiple nodes.
+                            <b style="font-weight: 500">Yes</b>. Data in Ignite
is either partitioned or replicated across a cluster of multiple nodes.
                             This provides scalability and adds resilience to the system.
Ignite automatically controls how data is partitioned,
                             however, users can plugin their own distribution (affinity) functions
and collocate various pieces of data together for efficiency.
                         </p>
-                        <p><a href="https://apacheignite.readme.io/v2.1/docs/distributed-sql">Read
more</a></p>
+                        <p><a href="https://apacheignite.readme.io/v2.1/docs/distributed-sql">Read
more</a></p><br/>
                     </div>
-
                 </div>
 
                 <div class="col-sm-6 col-md-6 col-xs-12" style="padding-right:0; top:
-5px;">
@@ -82,7 +81,7 @@ under the License.
         <section id="ignite-faq" class="page-section">
             <h2>Is Ignite a relational SQL database?</h2>
             <p>
-                <b>Not fully</b>. Although Ignite aims to behave like any other
relational SQL database, there are differences in how Ignite handles constraints and indexes.
+                <b style="font-weight: 500">Not fully</b>. Although Ignite aims
to behave like any other relational SQL database, there are differences in how Ignite handles
constraints and indexes.
                 Ignite supports primary and secondary indexes, however, the uniqueness can
only be enforced for the primary indexes.
                 Ignite also does not support foreign key constraints.
             </p>
@@ -90,37 +89,37 @@ under the License.
                 Essentially, Ignite purposely does not support any constraints that would
entail a cluster broadcast message for each update
                 and significantly hurt performance and scalability of the system.
             </p>
-            <p><a href="https://apacheignite.readme.io/v2.1/docs/indexes">Read
more</a></p>
+            <p><a href="https://apacheignite.readme.io/v2.1/docs/indexes">Read
more</a></p><br/>
 
             <h2>Is Ignite an in-memory database?</h2>
             <p>
-                <b>Yes</b>. Even though Ignite durable memory works well in-memory
and on-disk, the disk persistence can be disabled and Ignite can act as a pure in-memory database.
+                <b style="font-weight: 500">Yes</b>. Even though Ignite durable
memory works well in-memory and on-disk, the disk persistence can be disabled and Ignite can
act as a pure in-memory database.
             </p>
-            <p><a href="https://apacheignite.readme.io/v2.1/docs/distributed-sql">Read
more</a></p>
+            <p><a href="https://apacheignite.readme.io/v2.1/docs/distributed-sql">Read
more</a></p><br/>
 
             <h2>Is Ignite a transactional database?</h2>
             <p>
-                <b>Not fully</b>. ACID Transactions are supported, but only at
key-value API level. Ignite also supports cross-partition transactions,
+                <b style="font-weight: 500">Not fully</b>. ACID Transactions
are supported, but only at key-value API level. Ignite also supports cross-partition transactions,
                 which means that transactions can span keys residing in different partitions
on different servers.
             </p>
 
             <p>
                 At SQL level Ignite supports atomic, but not yet transactional consistency.
Ignite community plans to implement SQL transactions in version 2.2.
             </p>
-            <p><a href="https://apacheignite.readme.io/v2.1/docs/sql-queries#known-limitations">Read
more</a></p>
+            <p><a href="https://apacheignite.readme.io/v2.1/docs/sql-queries#known-limitations">Read
more</a></p><br/>
 
             <h2>Is Ignite a key-value store?</h2>
             <p>
-                <b>Yes</b>. Ignite provides a feature rich key-value API, that
is JCache (JSR-107) compliant and supports Java, C++, and .NET.
+                <b style="font-weight: 500">Yes</b>. Ignite provides a feature
rich key-value API, that is JCache (JSR-107) compliant and supports Java, C++, and .NET.
             </p>
-            <p><a href="https://apacheignite.readme.io/v2.1/docs/data-grid">Read
more</a></p>
+            <p><a href="https://apacheignite.readme.io/v2.1/docs/data-grid">Read
more</a></p><br/>
 
             <h2>Is Ignite an in-memory data grid?</h2>
             <p>
-                <b>Yes</b>. Ignite is a full-featured data grid, which can be
used either in pure in-memory mode or with Ignite native persistence.
+                <b style="font-weight: 500">Yes</b>. Ignite is a full-featured
data grid, which can be used either in pure in-memory mode or with Ignite native persistence.
                 It can also integrate with any 3rd party database, including any RDBMS or
NoSQL store.
             </p>
-            <p><a href="https://apacheignite.readme.io/v2.1/docs/data-grid">Read
more</a></p>
+            <p><a href="https://apacheignite.readme.io/v2.1/docs/data-grid">Read
more</a></p><br/>
 
             <h2>What is durable memory?</h2>
             <p>
@@ -128,7 +127,7 @@ under the License.
                 allocator which becomes durable by persisting to the write-ahead-log (WAL)
and, then, to main Ignite persistent storage. When persistence
                 is disabled, durable memory acts like a pure in-memory storage.
             </p>
-            <p><a href="https://apacheignite.readme.io/v2.1/docs/durable-memory">Read
more</a></p>
+            <p><a href="https://apacheignite.readme.io/v2.1/docs/durable-memory">Read
more</a></p><br/>
 
             <h2>What is collocated processing?</h2>
             <p>
@@ -136,7 +135,7 @@ under the License.
                 Data collocation becomes especially important when performing distributed
SQL joins. Ignite also supports sending user logic
                 (functions, lambdas, etc.) directly to the nodes where the data resides and
computing on data locally.
             </p>
-            <p><a href="https://apacheignite.readme.io/v2.1/docs/collocate-compute-and-data">Read
more</a></p>
+            <p><a href="https://apacheignite.readme.io/v2.1/docs/collocate-compute-and-data">Read
more</a></p><br/>
 
             <h2>Book</h2>
                 <p>Learn even more from <a href="http://a.co/h4MBi1v" target="_blank">High-Performance
in-memory computing with Apache Ignite</a> book.</p>



Mime
View raw message