Author: dmagda
Date: Tue Jan 23 01:16:06 2018
New Revision: 1821957
URL: http://svn.apache.org/viewvc?rev=1821957&view=rev
Log:
reworking what's ignite page
Added:
ignite/site/trunk/whatisignite-3.html (with props)
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=1821957&r1=1821956&r2=1821957&view=diff
==============================================================================
--- ignite/site/trunk/css/all.css (original)
+++ ignite/site/trunk/css/all.css Tue Jan 23 01:16:06 2018
@@ -9479,8 +9479,46 @@ div.square {
list-style-image:
url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAQAAAC1HAwCAAAAC0lEQVR42mNkYAAAAAYAAjCB0C8AAAAASUVORK5CYII=);
}
-#ignite-facts h3 {
- line-height: 40px;
+#ignite-facts > .fact-panel {
+ margin-bottom: 40px;
+}
+#ignite-facts > .fact-panel h3 {
+ line-height: 50px;
+ color: white;
+ padding-bottom: 0px;
+}
+#ignite-facts > .left {
+ padding-left: 0px;
+}
+#ignite-facts > .right {
+ padding-right: 0px;
+}
+
+.ignite-facts-question {
+ background: linear-gradient(to right, #bf0000, #ef0000);
+ margin-bottom: 10px;
+ padding-left: 10px !important;
+}
+
+.ignite-facts-answer {
+ padding-left: 10px !important;
+ padding-right: 10px !important;
+ margin-bottom: 45px;
+}
+
+#ignite-facts-3 > .fact-panel {
+ margin-bottom: 40px;
+}
+#ignite-facts-3 > .fact-panel h3 {
+ line-height: 50px;
+ padding-bottom: 0px;
+ font-weight: 500;
+}
+#ignite-facts-3 > .left {
+ padding-left: 0px;
+}
+#ignite-facts-3 > .right {
+ padding-right: 0px;
}
.btn-transparent {
Modified: ignite/site/trunk/scss/ignite.scss
URL:
http://svn.apache.org/viewvc/ignite/site/trunk/scss/ignite.scss?rev=1821957&r1=1821956&r2=1821957&view=diff
==============================================================================
--- ignite/site/trunk/scss/ignite.scss (original)
+++ ignite/site/trunk/scss/ignite.scss Tue Jan 23 01:16:06 2018
@@ -2058,7 +2058,55 @@ div.square {
}
#ignite-facts {
- h3 {
- line-height: 40px;
+ > .fact-panel {
+ margin-bottom: 40px;
+
+ h3 {
+ line-height: 50px;
+ color: white;
+ padding-bottom: 0px;
+ }
+ }
+
+ > .left {
+ padding-left: 0px;
+ }
+
+ > .right {
+ padding-right: 0px;
}
}
+
+.ignite-facts-question {
+ background: linear-gradient(to right, #bf0000, #ef0000);
+ margin-bottom: 10px;
+ padding-left: 10px !important;
+}
+
+.ignite-facts-answer {
+ padding-left: 10px !important;
+ padding-right: 10px !important;
+ margin-bottom: 45px;
+}
+
+
+#ignite-facts-3 {
+ > .fact-panel {
+ margin-bottom: 40px;
+
+ h3 {
+ line-height: 50px;
+ padding-bottom: 0px;
+ font-weight:500;
+ }
+ }
+
+
+ > .left {
+ padding-left: 0px;
+ }
+
+ > .right {
+ padding-right: 0px;
+ }
+}
\ No newline at end of file
Modified: ignite/site/trunk/whatisignite-2.html
URL:
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite-2.html?rev=1821957&r1=1821956&r2=1821957&view=diff
==============================================================================
--- ignite/site/trunk/whatisignite-2.html (original)
+++ ignite/site/trunk/whatisignite-2.html Tue Jan 23 01:16:06 2018
@@ -52,120 +52,129 @@ under the License.
<!--#include virtual="/includes/header.html" -->
<main id="main" role="main" class="container">
- <section id="whatisignite" class="page-section" style="border: none;">
- <h1 class="first heading" style="text-align: center;"><span>Apache
Ignite™ is ...</span></h1>
- <div class="col-sm-12 col-md-12 col-xs-12 description-block">
- <p style="text-align: center;"><i>memory-centric distributed
- <strong>database</strong>, <strong>caching</strong>, and
<strong>processing</strong> platform for
- transactional, analytical, and streaming workloads,<br/>
- delivering <nobr>in-memory</nobr> speeds at petabyte
scale</i>
- </p>
+ <div class="col-sm-12 col-md-12 col-xs-12" style="padding: 0px;">
+ <section id="whatisignite" class="page-section" style="border:
none;">
+ <h1 class="first heading" style="text-align:
center;"><span>Apache Ignite™ is ...</span></h1>
+ <div class="col-sm-12 col-md-12 col-xs-12 description-block">
+ <p style="text-align: center;"><i>memory-centric
distributed
+ <strong>database</strong>, <strong>caching</strong>,
and <strong>processing</strong> platform for
+ transactional, analytical, and streaming
workloads,<br/>
+ delivering <nobr>in-memory</nobr> speeds at petabyte
scale</i>
+ </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>
+ </div>
+ </section>
+ </div>
+ <div class="col-sm-12 col-md-12 col-xs-12" style="top: -50px; padding:
0px;">
+ <div class="section-heading">
+ <h2 style="text-align: center;">IGNITE FACTS</h2>
</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>
- </div>
- </section>
-
- <section id="ignite-facts" class="page-section">
- <div class="col-sm-12 col-md-12 col-xs-12" style="margin-top:
20px;">
- <h2 style="text-align: center; color: #e50000;">Ignite
Facts</h2>
- <hr><br/><br/><br/>
-
- <h3>Is Ignite a persistent or memory-only storage?</h3>
- <p>
- <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.
-
- </p>
- <br/><br/>
-
- <h3>Is Ignite an in-memory database (IMDB)?</h3>
- <p>
- <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.
- </p>
- <br/><br/>
-
- <h3>Is Ignite an in-memory data grid (IMDG)?</h3>
- <p>
- <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.
- </p>
- <br/><br/>
-
- <h3>Is Ignite a distributed cache?</h3>
- <p>
- <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.
- </p>
- <br/><br/>
-
- <h3>Is Ignite a distributed database?</h3>
- <p>
- <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.
- </p>
- <br/><br/>
-
- <h3>Is Ignite an SQL database?</h3>
- <p>
- <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.
- </p>
- <p>
- Essentially, Ignite purposely does not support any
constraints that would entail a cluster-wide broadcast
- message for each update and significantly hurt performance
and scalability of the system.
- </p>
- <br/><br/>
-
- <h3>Is Ignite a NoSQL database?</h3>
- <p>
- <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.
- </p>
- <br/><br/>
-
- <h3>Is Ignite a transactional database?</h3>
- <p>
- <strong>Not fully</strong>. 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.5.
- </p>
- <br/><br/>
-
- <h3>Is Ignite a multi-model database?</h3>
- <p>
- <strong>Yes</strong>. Ignite supports both, key-value and
SQL for modelling and accessing data.
- In addition, Ignite provides strong processing APIs for
computing on distributed data.
- </p>
- <br/><br/>
-
- <h3>Is Ignite a key-value store?</h3>
- <p>
- <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>
- </p>
- <p><a
href="https://apacheignite.readme.io/docs/data-grid";></a></p><br/><br/>
+ <hr>
+ <section id="ignite-facts" class="page-section">
+ <div class="col-sm-6 col-md-6 col-xs-12 fact-panel left">
+ <h3 class="ignite-facts-question">Is Ignite an in-memory
database?</h3>
+ <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.
+ </p>
+ </div>
+
+ <div class="col-sm-6 col-md-6 col-xs-12 fact-panel right">
+ <h3 class="ignite-facts-question">Is Ignite an in-memory
data grid?</h3>
+ <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.
+ </p>
+ </div>
+
+ <div class="col-sm-6 col-md-6 col-xs-12 fact-panel left">
+ <h3 class="ignite-facts-question">Is Ignite a distributed
cache?</h3>
+ <p class="ignite-facts-answer">
+ <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.
+ </p>
+ </div>
+
+ <div class="col-sm-6 col-md-6 col-xs-12 fact-panel right">
+ <h3 class="ignite-facts-question">Is Ignite a distributed
database?</h3>
+ <p class="ignite-facts-answer">
+ <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.
+ </p>
+ </div>
+
+ <div class="col-sm-6 col-md-6 col-xs-12 fact-panel left">
+ <h3 class="ignite-facts-question">Is Ignite an SQL
database?</h3>
+ <p class="ignite-facts-answer">
+ <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.
+ </p>
+ <!--<p>-->
+ <!--Essentially, Ignite purposely does not support any
constraints that would entail a cluster-wide broadcast-->
+ <!--message for each update and significantly hurt
performance and scalability of the system.-->
+ <!--</p>-->
+ </div>
+
+ <div class="col-sm-6 col-md-6 col-xs-12 fact-panel right">
+ <h3 class="ignite-facts-question">Is Ignite a disk or
memory-only storage?</h3>
+ <p class="ignite-facts-answer">
+ <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.
+ </p><br/><br/>
+ </div>
+
+ <div class="col-sm-6 col-md-6 col-xs-12 fact-panel left">
+ <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.
+ </p>
+ </div>
+
+ <div class="col-sm-6 col-md-6 col-xs-12 fact-panel right">
+ <h3 class="ignite-facts-question">Is Ignite a
transactional database?</h3>
+ <p class="ignite-facts-answer">
+ <strong>Not fully</strong>. 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.
<br/> <br/>
+ At SQL level Ignite supports atomic, but not yet
transactional consistency. Ignite community plans
+ to implement SQL transactions in version 2.5.
+ </p>
+ </div>
+
+ <div class="col-sm-6 col-md-6 col-xs-12 fact-panel left">
+ <h3 class="ignite-facts-question">Is Ignite a multi-model
database?</h3>
+ <p class="ignite-facts-answer">
+ <strong>Yes</strong>. Ignite supports both, key-value
and SQL for modelling and accessing data.
+ In addition, Ignite provides strong processing APIs
for computing on distributed data.
+ </p>
+ </div>
+
+ <div class="col-sm-6 col-md-6 col-xs-12 fact-panel right">
+ <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>
+ </p>
+ <p><a
href="https://apacheignite.readme.io/docs/data-grid";></a></p><br/><br/>
+ </div>
- <h3>Book</h3>
+ <h3 style="color: black;">Book</h3>
<p>Learn even more from <a href="http://a.co/h4MBi1v";
target="_blank">High-Performance in-memory computing with Apache Ignite</a>
book.</p>
- </div>
- </section>
+ </section>
+ </div>
</main>
<!--#include virtual="/includes/footer.html" -->
Added: ignite/site/trunk/whatisignite-3.html
URL:
http://svn.apache.org/viewvc/ignite/site/trunk/whatisignite-3.html?rev=1821957&view=auto
==============================================================================
Binary file - no diff available.
Propchange: ignite/site/trunk/whatisignite-3.html
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
