You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ignite.apache.org by dm...@apache.org on 2018/01/25 00:07:22 UTC
svn commit: r1822169 - in /ignite/site/trunk: css/all.css scss/ignite.scss
whatisignite-2.html
Author: dmagda
Date: Thu Jan 25 00:07:22 2018
New Revision: 1822169
URL: http://svn.apache.org/viewvc?rev=1822169&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-2.html
Modified: ignite/site/trunk/css/all.css
URL: http://svn.apache.org/viewvc/ignite/site/trunk/css/all.css?rev=1822169&r1=1822168&r2=1822169&view=diff
==============================================================================
--- ignite/site/trunk/css/all.css (original)
+++ ignite/site/trunk/css/all.css Thu Jan 25 00:07:22 2018
@@ -9483,9 +9483,10 @@ div.square {
margin-bottom: 40px;
}
#ignite-facts > .fact-panel h3 {
- line-height: 50px;
+ line-height: 30px;
color: white;
- padding-bottom: 0px;
+ padding-bottom: 10px;
+ padding-top: 10px;
}
#ignite-facts > .left {
padding-left: 0px;
@@ -9495,7 +9496,7 @@ div.square {
}
.ignite-facts-question {
- background: linear-gradient(to right, #bf0000, #ef0000);
+ background: #e50000;
margin-bottom: 10px;
padding-left: 10px !important;
}
@@ -9503,7 +9504,6 @@ div.square {
.ignite-facts-answer {
padding-left: 10px !important;
padding-right: 10px !important;
- margin-bottom: 45px;
}
#ignite-facts-3 > .fact-panel {
Modified: ignite/site/trunk/scss/ignite.scss
URL: http://svn.apache.org/viewvc/ignite/site/trunk/scss/ignite.scss?rev=1822169&r1=1822168&r2=1822169&view=diff
==============================================================================
--- ignite/site/trunk/scss/ignite.scss (original)
+++ ignite/site/trunk/scss/ignite.scss Thu Jan 25 00:07:22 2018
@@ -2062,9 +2062,10 @@ div.square {
margin-bottom: 40px;
h3 {
- line-height: 50px;
+ line-height: 30px;
color: white;
- padding-bottom: 0px;
+ padding-bottom: 10px;
+ padding-top: 10px;
}
}
@@ -2078,7 +2079,7 @@ div.square {
}
.ignite-facts-question {
- background: linear-gradient(to right, #bf0000, #ef0000);
+ background: #e50000;
margin-bottom: 10px;
padding-left: 10px !important;
}
@@ -2086,7 +2087,6 @@ div.square {
.ignite-facts-answer {
padding-left: 10px !important;
padding-right: 10px !important;
- margin-bottom: 45px;
}
Modified: ignite/site/trunk/whatisignite-2.html
URL: http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite-2.html?rev=1822169&r1=1822168&r2=1822169&view=diff
==============================================================================
--- ignite/site/trunk/whatisignite-2.html (original)
+++ ignite/site/trunk/whatisignite-2.html Thu Jan 25 00:07:22 2018
@@ -63,7 +63,7 @@ under the License.
</p>
</div>
<div class="col-sm-12 col-md-12 col-xs-12 img-holder">
- <a href="/images/durable-memory.png"><img class="img-responsive" src="/images/durable-memory.png" alt="Apache Ignite - Durable Memory" width="900px;"/></a>
+ <a href="/images/durable-memory.png"><img class="img-responsive" src="/images/ignite_architecture.png" alt="Apache Ignite Architecture" width="600px;"/></a>
</div>
</section>
</div>
@@ -78,7 +78,7 @@ under the License.
<p class="ignite-facts-answer">
<strong>Yes</strong>. Even though Ignite durable memory works well in-memory and on-disk, the disk
persistence can be disabled and Ignite can act as a distributed in-memory database, with
- support for SQL and distributed joins.<br/><br/>
+ support for SQL and distributed joins.<br/>
<a href="/use-cases/database/in-memory-database.html" target="_blank">Read more</a>
</p>
</div>
@@ -88,7 +88,7 @@ under the License.
<p class="ignite-facts-answer">
<strong>Yes</strong>. Ignite is a full-featured distributed key-value data grid, which can be used either in
memory-only mode or with Ignite native persistence. It can also automatically integrate with any 3rd party databases,
- including any RDBMS or NoSQL stores.<br/><br/>
+ including any RDBMS or NoSQL stores.<br/>
<a href="/features/datagrid.html" target="_blank">Read more</a>
</p>
</div>
@@ -99,7 +99,7 @@ under the License.
<strong>Yes</strong>. When native persistence is disabled, Ignite becomes a distributed cache.
Ignite implements JCache specification (JSR 107) and provides
a lot more functionality than required by the specification, including partitioned and replicated
- distribution modes, distributed ACID transactions, SQL queries, native persistence, and more.<br/><br/>
+ distribution modes, distributed ACID transactions, SQL queries, native persistence, and more.<br/>
<a href="/use-cases/caching/database-caching.html" target="_blank">Read more</a>
</p>
</div>
@@ -110,7 +110,7 @@ under the License.
<strong>Yes</strong>. Data in Ignite is either partitioned or replicated across a cluster of
multiple nodes. This provides scalability and adds resiliency 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.<br/><br/>
+ and collocate various pieces of data together for efficiency.<br/>
<a href="/use-cases/database/distributed-database.html" target="_blank">Read more</a>
</p>
</div>
@@ -121,7 +121,7 @@ under the License.
<strong>Not fully</strong>. 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.<br/><br/>
+ Ignite also does not support foreign key constraints.<br/>
<a href="/use-cases/database/sql-database.html" target="_blank">Read more</a>
</p>
<!--<p>-->
@@ -136,7 +136,7 @@ under the License.
<strong>Both</strong>. Native persistence in Ignite can be turned on and off. This allows Ignite to store
data sets bigger than can fit in the available memory. Essentially, smaller operational data sets
can be stored in-memory only, and larger data sets that do not fit in memory can be stored on disk,
- using memory as a caching layer for better performance.<br/><br/><br/> <br/>
+ using memory as a caching layer for better performance.<br/><br/> <br/>
</p>
</div>
@@ -144,7 +144,7 @@ under the License.
<h3 class="ignite-facts-question">Is Ignite a NoSQL database?</h3>
<p class="ignite-facts-answer">
<strong>Not exactly</strong>. Just like other NoSQL databases, Ignite is highly available and
- horizontally scalable. However, unlike other NoSQL databases, Ignite supports SQL and ACID transactions.<br/><br/>
+ horizontally scalable. However, unlike other NoSQL databases, Ignite supports SQL and ACID transactions.<br/>
<a href="/use-cases/comparison/ignite-for-nosql.html" target="_blank">Read more</a>
</p>
</div>
@@ -172,7 +172,7 @@ under the License.
<h3 class="ignite-facts-question">Is Ignite a key-value store?</h3>
<p class="ignite-facts-answer">
<strong>Yes</strong>. Ignite provides a feature rich key-value API, that is JCache (JSR-107) compliant
- and supports Java, C++, <nobr>and .NET.</nobr><br/><br/>
+ and supports Java, C++, <nobr>and .NET.</nobr><br/>
<a href="/use-cases/database/key-value-store-database.html" target="_blank">Read more</a>
</p>
</div>