Changes 7 + new frontpage hero-screen
diff --git a/404.html b/404.html
index e26b6ef..b305975 100644
--- a/404.html
+++ b/404.html
@@ -4,10 +4,10 @@
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1" />
<title>404 Not found - Apache Ignite</title>
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="/css/errors.css?ver=0.7" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/errors.css?ver=0.8" />
<style>
.error404 {
flex-flow: column nowrap;
@@ -28,7 +28,7 @@
}
}
</style>
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -429,6 +429,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/_src/_components/base.pug b/_src/_components/base.pug
index 546a0fc..f6360e6 100644
--- a/_src/_components/base.pug
+++ b/_src/_components/base.pug
@@ -1,4 +1,4 @@
-- var config = { hdrClassName: '', version: '0.7' }
+- var config = { hdrClassName: '', version: '0.8' }
include ../_components/mixins.pug
doctype html
html(lang="en")
diff --git a/_src/arch/multi-tier-storage.pug b/_src/arch/multi-tier-storage.pug
index be3526d..9061ebf 100644
--- a/_src/arch/multi-tier-storage.pug
+++ b/_src/arch/multi-tier-storage.pug
@@ -29,7 +29,7 @@
.innerhero__pre.pb-3 Apache Ignite
h1.h1.innerhero__h1 Multi-Tier Storage
.innerhero__descr.pt-2.h5.
- Store and access your data across memory <br>and disk with no compromises
+ Store and access your data across memory <br>and disk without compromise
.innerhero__action
a.button.innerhero__button(href="https://ignite.apache.org/docs/latest/index") Start Coding
img.innerhero__pic.innerhero__pic--multitier(src="/img/usecases/in-memory-hero.svg", alt="Distributed In-Memory Cache")
@@ -106,7 +106,7 @@
img.multitierblock__pic(src="/img/features/multitier/04-bd.svg", alt="")
.multitiers__right.multitiers__text
h4.multitier3__h4.fz20.pb-1x How It Works
- p 100% of data is persisted to Ignite native persistence, and the same or smaller amount is cached in memory. The more data cached, the faster the performance.
+ p 100% of data is persisted to Ignite native persistence,and the same amount or less is cached in memory. The more data cached, the faster the performance.
p Applications can query both in-memory and disk-only records transparently scaling beyond available memory capacity.
p There is no need for memory warm-ups on restarts since Ignite can serve data from disk. SSD, Flash, HDD or Intel® Optane™ operating in the AppDirect Mode can be used as a storage device.
h4.multitier3__h4.fz20.pt-3.pb-2 Use-Cases
diff --git a/_src/arch/native-persistence.pug b/_src/arch/native-persistence.pug
index c6a130e..fe26e86 100644
--- a/_src/arch/native-persistence.pug
+++ b/_src/arch/native-persistence.pug
@@ -43,7 +43,7 @@
.native1__block.native1__block--bad
img.native1__icon(src="/img/features/smile-doesnt-have.svg", alt="")
.native1__title.fz20.pt-1x Usually, in-memory caches and databases provide limited persistence capabilities.
- p.pt-2 For instance, some solutions just do a backup copy of <br>the in-memory data purely for restart purposes.
+ p.pt-2 For instance, some solutions create a backup copy of <br>the in-memory data purely for restart purposes.
.native1__block
img.native1__icon(src="/img/features/smile-done.svg", alt="")
.native1__title.fz20.pt-1x.
@@ -57,7 +57,7 @@
h3.fz20.native2item__title Scale beyond memory <br>capacity
p.pt-1x 100% of data is always stored on disk. You decide how much memory to allocate to your data.
article.native2item
- h3.fz20.native2item__title Seconds needed <br>for recovery
+ h3.fz20.native2item__title Just seconds needed <br>for recovery
p.pt-1x Ignite becomes operational from disk instantaneously. There is no need to wait for the data to get preloaded on restarts.
article.native2item
h3.fz20.native2item__title Query in-memory <br>and on-disk data
@@ -101,7 +101,7 @@
.nativestepitem__text
p As the WAL grows, it periodically gets checkpointed to the main storage.
p <a href="https://ignite.apache.org/docs/latest/persistence/native-persistence.html#checkpointing">Checkpointing</a> is the process of copying dirty pages from the memory tier to the partition files on disk.
- p.nativestepitem__small A dirty page is a page that was updated in memory, was appended to the WAL, but was not written to the respective partition file on disk yet.
+ p.nativestepitem__small A dirty page is a page that has been updated in memory and appended to the WAL, but has not yet been written to the respective partition file on disk.
article.nativestepitem
i.fz20.pb-1x 03
//- .nativestepitem__title.fz20 Third Step
diff --git a/_src/faq.pug b/_src/faq.pug
index caf0929..63c585d 100644
--- a/_src/faq.pug
+++ b/_src/faq.pug
@@ -26,7 +26,7 @@
.innerhero__main.innerhero__main--long
h1.h1.innerhero__h1 Frequently Asked Questions <br>About Apache Ignite
.innerhero__descr.pt-5.h4.
- Ignite’s rich feature set enables it for a myriad of use cases. <br>
+ Ignite’s rich feature set means it has a myriad of use cases.<br>
Is Ignite a cache, transactional database, key-value store? <br>Find the answers below.
img.innerhero__pic.innerhero__pic--faq(src="/img/faq/hero.svg", alt="Frequently asked questions")
// /.innerhero
@@ -134,7 +134,7 @@
.faqbox__anwser.h5.pt-3 Not fully
.faqbox__text.pt-3
p 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 At SQL level, Ignite supports atomic, but not yet transactional consistency. SQL transactions implementation is already <a href="https://cwiki.apache.org/confluence/display/IGNITE/IEP-3%3A+Transactional+SQL" target="_blank">in the works</a> and will be released in Ignite 3.
+ p At SQL level, Ignite supports atomic but not yet transactional consistency. A SQL transactions implementation is already <a href="https://cwiki.apache.org/confluence/display/IGNITE/IEP-3%3A+Transactional+SQL" target="_blank">in the works</a> and will be released in Ignite 3.
.cardsimple__bottom
a.cardsimple__button.button.button--shadow(href="/features/acid-transactions.html") Learn More: ACID Transactions
@@ -151,7 +151,7 @@
h3.faqbox__itemtitle.h5 Is Ignite A Key-Value Store?
.faqbox__anwser.h5.pt-3 Yes
.faqbox__text.pt-3
- p Ignite provides a feature-rich key-value API, that is JCache (JSR-107) compliant and supports Java, C++, .NET, and other programming languages.
+ p Ignite provides a feature-rich key-value API that is JCache (JSR-107) compliant and supports Java, C++, .NET, and other programming languages.
.cardsimple__bottom
a.cardsimple__button.button.button--shadow(href="/use-cases/key-value-store.html") Learn More: Distributed Key-Value Store
// /.faqboxs
diff --git a/_src/features/acid-transactions.pug b/_src/features/acid-transactions.pug
index 5794c3e..306c248 100644
--- a/_src/features/acid-transactions.pug
+++ b/_src/features/acid-transactions.pug
@@ -52,26 +52,26 @@
.acid1__item
.acid1__title.fz20 Durability
.acid1__text.pt-3
- p Multi-tier storage persists changes durably to disk. Committed transactions always survive failures, incomplete transactions are rolled back.
+ p Multi-tier storage persists changes durably to disk. Committed transactions always survive failures, and incomplete transactions are rolled back.
.acid1__item
.acid1__title.fz20 Fault-Tolerance
.acid1__text.pt-3
- p The transactional engine avoids inconsistencies even if your transaction is failed in the middle of a commit.
+ p The transactional engine avoids inconsistencies even if your transaction fails halfway through.
// /.acid1
section.acid2.container
- h2.acid2__h2 To guarantee data consistency, durability and fault-tolerance<br> <strong>Ignite implements a two-phase commit protocol</strong>
+ h2.acid2__h2 To guarantee data consistency, durability and fault-tolerance,<br> <strong>Ignite implements a two-phase commit protocol</strong>
.acid2__wrap.flexi.pt-5
.acid2__main
- p In distributed systems, a transaction usually spans across multiple cluster nodes.
+ p In distributed systems, a transaction usually spans multiple cluster nodes.
p To handle possible distributed failures properly and avoid data inconsistencies cluster-wide, a two-phase commit protocol (2PC) is used.
h3.acid2__subtitle.h5.pb-2 How ACID transactions work
p Whenever the records get updated within a transaction, Ignite keeps the transactional state in a local transaction map until the changes are committed.
p From here, the data is transferred to the participating remote nodes. Only the nodes that hold primary or backup copies of the data participate in the transaction.
- p If a transaction is mapped to a single node, then, Ignite optimizes the transaction execution by switching to the one-phase-commit (1PC) protocol.
+ p If a transaction is mapped to a single node, then Ignite optimizes the transaction execution by switching to the one-phase-commit (1PC) protocol.
aside.acid2__right
img(src="/img/features/acid/acid-func.svg", alt="").acid2__funcimg
// /.acid2
@@ -96,7 +96,7 @@
p.pt-1 The WAL provides a recovery mechanism for failure scenarios when a single node or the whole cluster goes down. A cluster can always be recovered to the latest successfully committed transaction.
.acid3__col
h3.h5.pb-2 Transactions with external databases
- p.fz20.acid3__collead Your transactions will be updated both in external database and in Apache Ignite
+ p.fz20.acid3__collead Your transactions will be updated both in the external database and in Apache Ignite
.acid3__small.pt-4
p When Apache Ignite is used as a caching layer for an external database, such as RDBMS, transactions span the cached data in Ignite as well as the data persisted in a database supporting transactional APIs.
p For instance, if a relational database is configured as a disk tier, Ignite writes the transactional changes to the database before sending a commit message to participating cluster nodes.
diff --git a/_src/features/key-value-apis.pug b/_src/features/key-value-apis.pug
index 584e3c4..6a60c1b 100644
--- a/_src/features/key-value-apis.pug
+++ b/_src/features/key-value-apis.pug
@@ -88,7 +88,7 @@
p A near cache is a local client-side cache that stores the most frequently <br>used data on the application end.
.keyvalue__title How it works
.keyvaluetext.pt-2.pb-5
- p It is applied for applications that require a consistent response time ranging <strong>in microseconds.</strong> Ignite automatically invalidates and updates the near cache.
+ p It is applied to applications that require a consistent response time of a few <strong>microseconds.</strong> Ignite automatically invalidates and updates the near cache.
p Whenever the primary copy of a record gets updated on a server node, Ignite propagates the change to all the nodes that store the record’s backup copy, as well as to the applications that keep the record’s copy in their near caches.
.keyvalue3__left
.keyvalue3__picwrap.picwrap
@@ -107,7 +107,7 @@
.keyvalue4__left
h3.keyvalue__title ACID Transactions To Update Your Distributed Records Consistently
.keyvaluetext.pt-2.pb-5
- p Apache Ignite key-value APIs are fully transactional which means that data can be updated consistently and reliably.
+ p Apache Ignite key-value APIs are fully transactional, which means that data can be updated consistently and reliably.
.keyvalue__title How it works
.keyvaluetext.pt-2.pb-5
p An Ignite transaction can update multiple records from different tables stored on different cluster nodes. Ignite can even span a transaction to an underlying relational database. Ignite implements <a href="/features/acid-transactions.html">two-phase-commit protocol to ensure data consistency at scale.</a>
diff --git a/_src/features/sql.pug b/_src/features/sql.pug
index 8fe01df..cc0a4d5 100644
--- a/_src/features/sql.pug
+++ b/_src/features/sql.pug
@@ -44,7 +44,7 @@
.dist__block.flexi
.dist__info
h2.dist__h2.h4 Apache Ignite as a SQL Database
- p.dist__text The native support for SQL let’s you work with Ignite as with a standard SQL database. Literally, you can use just SQL if your applications need nothing else:
+ p.dist__text The native support for SQL let’s you work with Ignite as with a standard SQL database. You can use simply SQL if your applications need nothing else:
.dist__items.flexi
.dist__item
h3.dist__item-title DDL commands
@@ -85,7 +85,7 @@
section.dist1
.container
h2.dist1__h2.h4 Join, Group and Aggregate Distributed Data Sets
- .dist1__subtext Whether you use a two or thousand-node cluster, you always can do the following:
+ .dist1__subtext Whether you use a two or thousand-node cluster, you can always do the following:
.dist1__parts.flexi
.dist1__part group data
.dist1__part join data
@@ -97,13 +97,13 @@
.dist1__blocks.flexi
.dist1__block
h4.dist1__h4 Co-located joins
- p.dist1__texts this is the most performant type of joins that avoids data shuffling between nodes and minimize network usage.
+ p.dist1__texts These are the most performant types of joins that avoid data shuffling between nodes and minimize network usage.
p.dist1__texts.pt-1 This type of join is used if you join <a class="dist1__link" href="https://ignite.apache.org/docs/latest/data-modeling/affinity-collocation" target="_blank">partitioned and replicated tables</a> or partitioned tables that are co-located with each other.
.dist1__block
- h4.dist1__h4 Non-colocated joins:
- p.dist1__texts less performant type of joins that join data of non-colocated tables. Ignite needs to shuffle data over the network to produce a correct result set.
+ h4.dist1__h4 Non-colocated joins
+ p.dist1__texts A less performant type of join that joins data of non‑colocated tables. Ignite needs to shuffle data over the network to produce a correct result set.
.dist1__block
- h4.dist1__h4 Hash joins:
+ h4.dist1__h4 Hash joins
p.dist1__texts Ignite supports classic hash join algorithm that is more efficient than nested loop joins for many scenarios.
// /.dist1
@@ -119,7 +119,7 @@
summary.dist2__active
img(src="/img/features/sql/plus.svg", alt="sql-hero")
.dist2__subtext
- p In this mode, Ignite SQL performs the fastest way possible as long as all the data is served from memory with no usage of the disk tier at all.
+ p In this mode, Ignite SQL carries out tasks as quickly as possible, as long as all the data is served from memory, with no usage of the disk tier at all.
.dist2__block
h3.dist2__h3 In-Memory <br>+ Native Persistence Mode
p.dist2__text Ignite scales beyond available<br> memory capacity
@@ -128,7 +128,7 @@
img(src="/img/features/sql/plus.svg", alt="sql-hero")
.dist2__subtext
p Ignite persists 100% of data and indexes in the <a href="/arch/native-persistence.html">native persistence</a> while caching as much as possible in memory.
- p.pt-1 Ignite SQL engine does not require to cache an entire data set in memory to operate correctly.
+ p.pt-1 Ignite SQL engine does not require the caching of entire data set in memory to operate correctly.
p.pt-1 If the engine finds that a record is not cached, then it will read the record from disk. Your application only executes SQL queries, and Ignite gets the records from both memory and disk automatically.
p.pt-1 On cluster restarts, Ignite reads data and indexes from disk, eliminating the need for memory warm-up, which significantly decreases downtime.
@@ -139,8 +139,8 @@
summary.dist2__active
img(src="/img/features/sql/plus.svg", alt="sql-hero")
.dist2__subtext
- p In this mode, the Ignite SQL engine requires caching all the data needed for distributed queries in memory since the engine currently does not support federated queries.
- p.pt-1 If federated queries between Ignite and an external database are required, then you can consider Ignite integration for Spark, where the DataFrames API can join the data stored in Ignite and other systems.
+ p In this mode, the Ignite SQL engine requires caching of all the data needed for distributed queries in memory, since the engine does not currently support federated queries.
+ p.pt-1 If federated queries between Ignite and an external database are required, then you can consider Ignite integration for Spark, where the DataFrames API can combine the data stored in Ignite and other systems.
diff --git a/_src/index.pug b/_src/index.pug
index ab24924..29ae224 100644
--- a/_src/index.pug
+++ b/_src/index.pug
@@ -25,17 +25,19 @@
block main
- global.pageHref = ""
- - config.hdrClassName = "hdr__dark"
+ - config.hdrClassName = ""
.fronttop
include ./_components/header.pug
+ img.fronttop__pic(src="/img/frontpage/hero-white.svg", alt="")
+
section.innerhero.fronthero
.container.innerhero__cont
.innerhero__main.innerhero__main--long
//- .innerhero__pre.pb-3 Scale Across Memory And Disk With No Compromises
h1.h1.innerhero__h1.innerhero__mega Distributed Database For <br>High‑Performance Applications <br>With In‑Memory Speed
- .innerhero__h2.h4.pt-2 Scale Across Memory And Disk With No Compromises
+ .innerhero__h2.h4.pt-2 Scale Across Memory And Disk Without Compromise
.innerhero__action.pt-5
a.button.fronthero__button(href="https://ignite.apache.org/docs/latest/index") Start Coding
// /.innerhero
@@ -64,7 +66,7 @@
a(href="/use-cases/provenusecases.html").frontcard
.frontcard__network
img(src="/img/frontpage/b1-planet.svg", alt="")
- .frontcard__title.h5.pt-3 Leading companies around the world select Ignite to speed and scale applications used by millions of people daily
+ .frontcard__title.h5.pt-3 Leading companies around the world select Ignite to speed up and scale applications used by millions of people daily
// /.frontcard
// /.fronttopcards
@@ -385,7 +387,7 @@
li Financial Services
li Retail
li Biotech
- li And others
+ li Others
.frontstories__sliderwrap
button.ctrl.ctrl--prev
img(src="/img/frontpage/icon-slider-arrow.svg", alt="")
@@ -480,7 +482,7 @@
.frontconfs__iconwrap.pb-3
img(src="/img/frontpage/events/001.svg", alt="")
h4.h5.frontconfcard__title.pb-2 Ignite Virtual Meetup
- p Experts and practitioners give <strong>online-talks and presentations</strong> and share their Apache Ignite experience.
+ p Experts and practitioners give <strong>online talks and presentations</strong> and share their Apache Ignite experience.
.frontconfcard__bottom
p.capstext Online
.frontconfcard__cal Regularly
@@ -546,11 +548,11 @@
a(href="/resources.html#training").frontresitem.flexi.frontresitem--rose
.frontresitem__icon
img(src="/img/frontpage/res-vebinar.svg", alt="")
- .frontresitem__text Trainings and courses that help building high-performance and data-intensive applications with the Apache Ignite
+ .frontresitem__text Trainings and courses that help with building high‑performance and data-intensive applications with the Apache Ignite
a(href="https://www.shamimbhuiyan.com/ignitebook", target="_blank").frontresitem.flexi.frontresitem--rose
.frontresitem__icon
img(src="/img/frontpage/res-book.svg", alt="")
- .frontresitem__text Apache Ignite book to expand your knowledge <br>in in-memory computing and distributed databases
+ .frontresitem__text Apache Ignite book to expand your knowledge <br>in in‑memory computing and distributed databases
.frontconfs__bottom.pt-5
a.button.button--shadow(href="/resources.html") View All Resources
diff --git a/_src/resources.pug b/_src/resources.pug
index 27590fb..ff6c085 100644
--- a/_src/resources.pug
+++ b/_src/resources.pug
@@ -134,7 +134,7 @@
+resvideo('https://www.youtube.com/watch?v=UeQKuAQaMNU', "In-Memory Computing Essentials")
p In this video, we introduce the fundamental capabilities of in-memory computing platforms, such as high-speed performance and scalability.
+resvideo('https://www.youtube.com/watch?v=hrnrsIkCnI0', "Distributed Computing <br>With Apache Ignite")
- p In this video, we show how to design and execute distributed computations considering all the pros and cons.
+ p In this video, we demonstrate how to design and execute distributed computations, and consider all the pros and cons.
+resvideo('https://www.youtube.com/watch?v=TCsl-W0tsEE', "Consistency And Transactions <Br>Of Apache Ignite")
p In this webinar, we provide a deep understanding of Apache Ignite’s support for ACID transactions and data consistency.
@@ -153,8 +153,8 @@
section.rescourses.container#training
h2.h4.resicontitle.flexi
img(src="/img/resourses/icon-training.svg", alt="")
- span Trainings and Courses
- p.pt-2.h5 Enhance your knowledge in building high-performance and <br>data-intensive applications with the Apache Ignite capabilities.
+ span Training and Courses
+ p.pt-2.h5 Enhance your knowledge of building high-performance and <br>data-intensive applications with the Apache Ignite capabilities.
.rescourses__wrap.pt-5
article.rescourse.cardsimple
p.fz20.rescourse__title.pb-2.maxline3 Apache Ignite Management <br>And Monitoring Guide
@@ -264,7 +264,7 @@
article.faqblock.flexi
h3.faqblock__title.faqblock__title--simple.h5
- span Report about bugs, possible <br>improvements and ctr.
+ span Report bugs, possible <br>improvements and ctr.
.faqblock__right
p.faqblock__rightitle By e-mail
p <a href="mailto:issues@ignite.apache.org">issues@ignite.apache.org</a>
diff --git a/_src/use-cases/hadoop-acceleration.pug b/_src/use-cases/hadoop-acceleration.pug
index 62d9c1f..7a6083c 100644
--- a/_src/use-cases/hadoop-acceleration.pug
+++ b/_src/use-cases/hadoop-acceleration.pug
@@ -72,7 +72,7 @@
h2.doop3__h2.h5 There are 3 basic steps:
.fz20.doop3__number 01
p.doop3__subtext Depending on the data volume and available memory capacity, you can enable<a href="/arch/native-persistence.html" target="_blank"> Ignite native persistence</a> to store historical data sets on disk while dedicating a memory space for operational records.
- p.doop3__subtext.pt-1 You can continue to use Hadoop as storage for less frequently used data or for long-running and ad-hoc analytical queries.
+ p.doop3__subtext.pt-1 You can continue to use Hadoop as storage for less frequently-used data or for long-running and ad-hoc analytical queries.
.fz20.doop3__number 02
p.doop3__subtext Your applications and services should use Ignite native APIs to process the data residing in the in-memory cluster. Ignite provides SQL, compute (aka. map-reduce), and machine learning APIs for various data processing needs.
.fz20.doop3__number 03
diff --git a/_src/use-cases/high-performance-computing.pug b/_src/use-cases/high-performance-computing.pug
index 38d8404..181ac5d 100644
--- a/_src/use-cases/high-performance-computing.pug
+++ b/_src/use-cases/high-performance-computing.pug
@@ -44,11 +44,11 @@
h3.h5.high1__title What is high-performance computing?
.high1__text.pt-3.pb-5
p High-performance computing is the ability to process data and perform complex calculations at high speeds.
- p You keep all your data on the cluster node and execute your kilobyte-size custom code over petabytes of data avoiding network-like utilization.
+ p You keep all your data on the cluster node and execute your kilobyte-size custom code over petabytes of data, avoiding network-like utilization.
h3.h5.high1__title How it works
.high1__text.pt-2
.high1__sub.pb-2 In traditional disk-based systems, <br>such as relational or NoSQL databases
- p Client applications usually bring data from servers, use the records for local calculations, and discard the data as soon as the business task is complete.
+ p Client applications usually bring data from servers, use the records for local calculations, and discard the data as soon as the business task is completed.
p This approach does not scale well if a significant volume of data gets transferred over the network.
.high1__sub.pt-2.pb-2 In in-memory computing systems, <br>such as Apache Ignite
p Apache Ignite supports a co-located processing technique. The primary aim of this technique is to increase the performance of your data-intensive or compute-intensive calculations by running them straight on Ignite cluster nodes.
@@ -117,7 +117,7 @@
.highicons__iconwrap.flexi
img(src="/img/usecases/high-peformance/icon-perf5.svg", alt="").highicons__icon
.highicons__title Biotech
- .highicons__descr e.g. drugs and vaccines discovery, sequencing DNA
+ .highicons__descr e.g. drug and vaccine discovery, sequencing DNA
// /.highicons
@@ -128,7 +128,7 @@
.highcases__topleft
.highcases__subtitle.pb-2 Personalized websites with dynamically changing content
p.pb-3 Whenever you visit Amazon, Walmart, Booking, or other websites, you see personalized content, such as relevant deals made especially for you.
- p Personalized content considering your age, location, preferences, and previous interactions is being processed and displayed in few seconds thanks to high-performance computing tasks that process gigabytes of data within a second.
+ p Personalized content that takes your age, location, preferences, and previous interactions into consideration is processed and displayed in just a few seconds thanks to high-performance computing tasks that process gigabytes of data within a second.
.highcases__topright
+powvideo(
"https://www.youtube.com/watch?v=qYd9GGRC4L0",
@@ -158,7 +158,7 @@
"How nference.ai Leverages Ignite For Distributed Analytics In The Bioinformatics Domain",
"comvideo__txt--small"
)
- p <strong>nference.ai:</strong> high-performance compute APIs used to define different statistical analyses and execute numerical data in real-time.
+ p <strong>nference.ai:</strong> high-performance compute APIs used to define different statistical analyses and execute numerical data in real time.
.highcases__one.flexi.pt-4.pb-4
.highcases__topleft
@@ -175,7 +175,7 @@
.highcases__two.pt-4
.highcases__subtitle.pb-2 Real-time analytics enables fast and precise decisions
- p High-performance computing allows the processing of unlimited data sets, <br>with analyzation taking only seconds.
+ p High-performance computing allows the processing of unlimited data sets, <br>with analysis taking only seconds.
.highcases__twowrap.flexi.pt-5
.highcases__twoitem
+powvideo(
diff --git a/_src/use-cases/in-memory-cache.pug b/_src/use-cases/in-memory-cache.pug
index db53c78..58be752 100644
--- a/_src/use-cases/in-memory-cache.pug
+++ b/_src/use-cases/in-memory-cache.pug
@@ -42,7 +42,7 @@
section.inmememor1.container
header.blockheader.blockheader--spl.flexi
- h2.capstext.pb-3 What Is In-Memory Cache
+ h2.capstext.pb-3 What Is In-Memory Cache?
.inmememor1__text
p In-memory cache is a storage layer placed between applications and databases. The cache keeps your hot data in memory to offload existing databases and accelerate applications.
// /.inmememor1
@@ -60,7 +60,7 @@
.inmememor-adv__text Memory as a storage layer provides the lowest latency and highest throughput. Laws of physics.
.inmememor-adv__item
h3.h4 Scale
- .inmememor-adv__text Horizontal scalability lets you grow the cluster unlimitedly to accommodate <br>data size and throughput.
+ .inmememor-adv__text Horizontal scalability lets you grow the cluster size to an unlimited extent to accommodate data size and throughput.
// /.inmememor-adv
@@ -132,11 +132,11 @@
p It’s usually assumed that changes will be fully replicated eventually and, <br>thus, the cache and the primary store will become consistent.
.inmememor3__bottom
- h3.fz20 Cach-Aside Deployment And Native Persistence
+ h3.fz20 Cache-Aside Deployment And Native Persistence
.inmememor3__botwrap.flexi.pt-3
.inmememor2__left
- p When Apache Ignite is deployed in a cache-aside configuration, its native persistence can be used as a disk store for Ignite datasets. <a href="/arch/native-persistence.html">Native persistence</a> allows for elimination of the time-consuming cache warm-up step.
- p As native persistence maintains a full copy of data on disk, you can cache a subset of records in memory. If a required data record is missing from memory, then Ignite reads the record from the disk automatically, regardless of which API you use — whether SQL, key-value, or scan queries.
+ p When Apache Ignite is deployed in a cache-aside configuration, its native persistence can be used as a disk store for Ignite datasets. <a href="/arch/native-persistence.html">Native persistence</a> allows for the elimination of the time-consuming cache warm-up step.
+ p As native persistence maintains a full copy of data on disk, you can cache a subset of records in memory. If a required data record is missing from memory, then Ignite reads the record from the disk automatically, regardless of which API you use — be it SQL, key-value, or scan queries.
.inmememor2__right
ul.inmememor3__checklist
li Seconds needed for recovery
diff --git a/_src/use-cases/in-memory-data-grid.pug b/_src/use-cases/in-memory-data-grid.pug
index 3f8463f..e8d8ff0 100644
--- a/_src/use-cases/in-memory-data-grid.pug
+++ b/_src/use-cases/in-memory-data-grid.pug
@@ -51,7 +51,7 @@
h2.compute2__h2 In-Memory Data Grid Overview
.hub1__block.flexi
.hub1__info
- h3.h5.hub1__title What is an in-memory data-grid?
+ h3.h5.hub1__title What is an in-memory data grid?
p.hub1__text An in-memory data grid (IMDG) is an advanced read-through/write-through cache that is deployed on top of multiple databases.
p.hub1__text Applications write to and read from the grid, and the grid propagates changes to the underlying data stores in a consistent way.
h3.h5.hub1__title.hub1__titleend How does an in-memory data grid work?
diff --git a/_src/use-cases/in-memory-database.pug b/_src/use-cases/in-memory-database.pug
index 4b5c973..589fd76 100644
--- a/_src/use-cases/in-memory-database.pug
+++ b/_src/use-cases/in-memory-database.pug
@@ -30,10 +30,8 @@
section.innerhero
.container.innerhero__cont
.innerhero__main
-
- h1.h1.innerhero__h1 In-Memory Database
- <br>
- span.with-apache With Apache Ignite
+ h1.h1.innerhero__h1 In-Memory Database<br>
+ span.with-apache With Apache Ignite
.innerhero__descr.pt-2.h5.
In-memory database that scales horizontally across memory<br> and disk with full SQL support
.innerhero__action
@@ -44,32 +42,32 @@
section.hub1
.container
- h2.compute2__h2 In-Memory Database Overview
- .hub1__block.flexi
- .hub1__info
- h3.h5.hub1__title What is an in-memory database?
- p.hub1__text An in-memory database (IMDB) is a data management system that stores data primarily in the computer’s main memory.
- h3.h5.hub1__title.hub1__titleend How an in-memory database works?
- p.hub1__text In-memory databases rely on spinning disks for data storage. IMDBs allow mission-critical applications to benefit from faster response times than disk-based databases.
- img.hub1__image(src="/img/usecases/database/image.svg", alt="image")
+ h2.compute2__h2 In-Memory Database Overview
+ .hub1__block.flexi
+ .hub1__info
+ h3.h5.hub1__title What is an in-memory database?
+ p.hub1__text An in-memory database (IMDB) is a data management system that stores data primarily in the computer’s main memory.
+ h3.h5.hub1__title.hub1__titleend How does an in-memory database work?
+ p.hub1__text In-memory databases rely on spinning disks for data storage. IMDBs allow mission-critical applications to benefit from faster response times than disk-based databases.
+ img.hub1__image(src="/img/usecases/database/image.svg", alt="image")
// /.hub1
section.base1
.container
- h2.base1__h2.h5 Apache Ignite as a distributed in-memory database scales horizontally across memory and disk with no compromises
- .base1__blocks.flexi
- .base1__block
- p.base1__text Apache Ignite works with memory, disk, and Intel Optane as active storage tiers.
- p.base1__text.pt-1 This <a href="/arch/multi-tier-storage.html">multi-tier</a> architecture combines, in one system, the advantages of in-memory computing with disk durability and strong consistency.
- .base1__block
- .base1__item.flexi
- .compute2-points__item.fz20
- h3.base1__black Speed of memory
- .base1__item.flexi
- .compute2-points__item.fz20
- h3.base1__black Strong consistency
- .base1__item.flexi
- .compute2-points__item.fz20
- h3.base1__black Durability of disk
+ h2.base1__h2.h5 Apache Ignite as a distributed in-memory database scales horizontally across memory and disk without compromise
+ .base1__blocks.flexi
+ .base1__block
+ p.base1__text Apache Ignite works with memory, disk, and Intel Optane as active storage tiers.
+ p.base1__text.pt-1 This <a href="/arch/multi-tier-storage.html">multi-tier</a> architecture combines the advantages of in-memory computing with disk durability and strong consistency, all in one system.
+ .base1__block
+ .base1__item.flexi
+ .compute2-points__item.fz20
+ h3.base1__black Speed of memory
+ .base1__item.flexi
+ .compute2-points__item.fz20
+ h3.base1__black Strong consistency
+ .base1__item.flexi
+ .compute2-points__item.fz20
+ h3.base1__black Durability of disk
// /.base1
section.compute2
@@ -80,7 +78,7 @@
.compute2-points__item.fz20
.compute2item__block
h3.fz20.compute2item__title Instantaneous cluster restarts
- p.compute2__text.base2__text Ignite becomes fully operational from disk upon a cluster startup or restarts without requiring to preload or warm up the memory tier.
+ p.compute2__text.base2__text Ignite becomes fully operational from disk upon a cluster startup or restarts without requiring a preload or a warm-up the memory tier.
.compute2item.hub2item
.compute2-points__item.fz20
@@ -95,45 +93,45 @@
.container
h2.base3__h2.h4 Apache Ignite as an in-memory database <br>supports a variety of developer APIs
.base3__blocks.flexi
- .base3__block
- h3.base3__h3 Essential Developer APIs
- .base3__images.flexi
- .base3__item.flexi
- img.base3__image(src="/img/features/03-distributed-SQL.svg", alt="sql")
- .base3__subtext SQL
- .base3__item.flexi
- img.base3__image(src="/img/features/05-key-value-APIs.svg", alt="apis")
- .base3__subtext Key-value
- .base3__item.flexi
- img.base3__image(src="/img/features/04-ACID-transactions.svg", alt="acid")
- .base3__subtext ACID<br> transactions
- p.base3__text Enable you to request, join, and group distributed datasets.
- .base3__block
- h3.base3__h3 High-Performance Computing APIs
- .base3__images.flexi
- .base3__item.flexi
- img.base3__image(src="/img/features/06-compute-APIs.svg", alt="sql")
- .base3__subtext Compute
- .base3__item.flexi
- img.base3__image(src="/img/features/07-machine-learning.svg", alt="apis")
- .base3__subtext Machine<br> learning
- .base3__item.flexi
- img.base3__image(src="/img/features/08-services.svg", alt="acid")
- .base3__subtext Services
- p.base3__text Execute logic close to the data, thus eliminating expensive data shuffling over the network.
- .base3__block
- h3.base3__h3 Real-Time Streaming APIs
- .base3__images.flexi
- .base3__item.flexi
- img.base3__image(src="/img/features/09-streaming.svg", alt="sql")
- .base3__subtext Streaming
- .base3__item.flexi
- img.base3__image(src="/img/features/10-continuous-queries.svg", alt="apis")
- .base3__subtext Continuous<br> Queries
- .base3__item.flexi
- img.base3__image(src="/img/features/11-messaging.svg", alt="acid")
- .base3__subtext Messaging
- p.base3__text.base3__textend Allow the seamless implementation of event-driven architectures.
+ .base3__block
+ h3.base3__h3 Essential Developer APIs
+ .base3__images.flexi
+ .base3__item.flexi
+ img.base3__image(src="/img/features/03-distributed-SQL.svg", alt="sql")
+ .base3__subtext SQL
+ .base3__item.flexi
+ img.base3__image(src="/img/features/05-key-value-APIs.svg", alt="apis")
+ .base3__subtext Key-value
+ .base3__item.flexi
+ img.base3__image(src="/img/features/04-ACID-transactions.svg", alt="acid")
+ .base3__subtext ACID<br> transactions
+ p.base3__text Enable you to request, join, and group distributed datasets.
+ .base3__block
+ h3.base3__h3 High-Performance Computing APIs
+ .base3__images.flexi
+ .base3__item.flexi
+ img.base3__image(src="/img/features/06-compute-APIs.svg", alt="sql")
+ .base3__subtext Compute
+ .base3__item.flexi
+ img.base3__image(src="/img/features/07-machine-learning.svg", alt="apis")
+ .base3__subtext Machine<br> learning
+ .base3__item.flexi
+ img.base3__image(src="/img/features/08-services.svg", alt="acid")
+ .base3__subtext Services
+ p.base3__text Execute logic close to the data, thus eliminating expensive data shuffling over the network.
+ .base3__block
+ h3.base3__h3 Real-Time Streaming APIs
+ .base3__images.flexi
+ .base3__item.flexi
+ img.base3__image(src="/img/features/09-streaming.svg", alt="sql")
+ .base3__subtext Streaming
+ .base3__item.flexi
+ img.base3__image(src="/img/features/10-continuous-queries.svg", alt="apis")
+ .base3__subtext Continuous<br> Queries
+ .base3__item.flexi
+ img.base3__image(src="/img/features/11-messaging.svg", alt="acid")
+ .base3__subtext Messaging
+ p.base3__text.base3__textend Allow the seamless implementation of event-driven architectures.
@@ -152,7 +150,7 @@
"comvideo__txt--white hub5__video"
)
.h4.hub5__title BNP Paribas
- p.hub5__text.base5__text with the help of Apache Ignite managed to design, build, and optimize a hybrid transactional-analytical processing (HTAP) solution. This enabled the bank to make key business decisions in real-time.
+ p.hub5__text.base5__text with the help of Apache Ignite managed to design, build, and optimize a hybrid transactional-analytical processing (HTAP) solution. This enabled the bank to make key business decisions in real time.
.hub5__item
+powvideo(
"https://www.youtube.com/watch?v=B8A8yR_e6VM&t=2s",
@@ -162,7 +160,7 @@
"comvideo__txt--white hub5__video"
)
.h4.hub5__title JP MorganChase
- p.hub5__text.base5__text faced an increasing need to apply transformations to large datasets in real-time. To meet this need, their team selected Ignite to achieve persistence, caching and integrated compute.
+ p.hub5__text.base5__text faced an increasing need to apply transformations to large datasets in real time. To meet this need, their team selected Ignite to achieve persistence, caching and integrated compute.
diff --git a/_src/use-cases/key-value-store.pug b/_src/use-cases/key-value-store.pug
index 785959c..e88f05d 100644
--- a/_src/use-cases/key-value-store.pug
+++ b/_src/use-cases/key-value-store.pug
@@ -76,7 +76,7 @@
.compute2-points__item.fz20
.compute2item__block
h3.fz20.compute2item__title Horizontal scalability
- p.compute2__text.base2__text Key-value stores can keep and process large volumes of data by scaling horizontally
+ p.compute2__text.base2__text Key-value stores can keep and process large volumes of data by scaling horizontally
// /.compute2
@@ -87,7 +87,7 @@
h2.grid4__h2.h5.key4__h2 With Apache Ignite, a key-value store can cache data in memory and persist it on disk
.grid4__block
p.grid4__text The <a href="/arch/native-persistence.html">native persistence</a> feature eliminates the time-consuming cache warm-up step as well as the data reloading phase from external databases.
- p.grid4__text.pt-1 Since the native persistence always keeps a full copy of data on disk, you are free to cache a subset of records in memory.
+ p.grid4__text.pt-1 Since native persistence always keeps a full copy of data on disk, you are free to cache a subset of records in memory.
p.grid4__text.pt-1 If a required data record is missing in memory, then Ignite reads it from disk automatically, regardless of the API you use.
// /.grid4
@@ -103,7 +103,7 @@
p.grid5__text.key5__text Applications can collect user preferences and behavioral patterns to offer better services. The records can be stored in a key-value database to enable fast customer data lookups.
article.native2item.grid5__item
h3.key5__h3 Back-end systems acceleration
- p.grid5__text.key5__text Developers use key-value stores to cache specific records that don’t require a regular update. This reduces load on core back-end systems and databases.
+ p.grid5__text.key5__text Developers use key-value stores to cache specific records that don’t require a regular update. This reduces the load on core back-end systems and databases.
// /.key5
diff --git a/_src/use-cases/spark-acceleration.pug b/_src/use-cases/spark-acceleration.pug
index 3b01408..853b3eb 100644
--- a/_src/use-cases/spark-acceleration.pug
+++ b/_src/use-cases/spark-acceleration.pug
@@ -47,13 +47,13 @@
.spark1__block
.spark1__item
h3.spark1__h3.fz20 Horizontally scalable and shared in-memory layer
- p.spark1__text Ignite is designed to store data sets in memory across a cluster of nodes reducing latency of Spark operations that usually need to pull date from disk-based systems.
+ p.spark1__text Ignite is designed to store data sets in memory across a cluster of nodes, reducing latency of Spark operations that usually need to pull date from disk-based systems.
.spark1__item
h3.spark1__h3.fz20 Minimal data shuffling over the network
- p.spark1__text Ignite tries to minimize data shuffling over the network between its store and Spark applications by running certain Spark tasks, produced by RDDs or DataFrames APIs, in-place on Ignite nodes.
+ p.spark1__text Ignite tries to minimize data shuffling over the network between its store and Spark applications by running certain Spark tasks, produced by RDDs or DataFrames APIs in-place on Ignite nodes.
.spark1__item
h3.spark1__h3.fz20 Extra performance boost with native Ignite APIs
- p.spark1__text Use native Ignite APIs, such as SQL from Spark applications directly and eliminate data shuffling completely between Spark and Ignite.
+ p.spark1__text Use native Ignite APIs such as SQL from Spark applications directly and eliminate data shuffling completely between Spark and Ignite.
img.spark1__image(src="/img/usecases/spark/image.svg", alt="image")
// /.spark1
@@ -71,7 +71,7 @@
.spark2__block
.spark2__item
p.spark2__text The Apache Spark DataFrame API introduced the concept of a schema to describe the data, allowing Spark to manage the schema and organize the data into a tabular format.
- p.spark2__text.pt-2 To put it simply, a DataFrame is a distributed collection of data organized into named columns. It is conceptually equivalent to a table in a relational database and allows Spark to leverage the Catalyst query optimizer to produce much more efficient query execution plans in comparison to RDDs, which are collections of elements partitioned across the nodes of the cluster.
+ p.spark2__text.pt-2 To put it simply, a DataFrame is a distributed collection of data organized into named columns. Conceptually, it is the equivalent of a table in a relational database. It allows Spark to leverage the Catalyst query optimizer to produce much more efficient query execution plans in comparison to RDDs, which are collections of elements partitioned across the nodes of the cluster.
.spark2__item
p.spark2__text Ignite supports DataFrame APIs allowing Spark to write to and read from Ignite through that interface.
p.spark2__text.pt-1 Furthermore, Ignite analyzes execution plans produced by Spark's Catalyst engine and can execute parts of the plan on Ignite nodes directly, which will reduce data shuffling and consequently make your SparkSQL perform better.
diff --git a/arch/clustering.html b/arch/clustering.html
index 25f1a16..385f834 100644
--- a/arch/clustering.html
+++ b/arch/clustering.html
@@ -4,12 +4,12 @@
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1" />
<title>Deployment Options</title>
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/native-persistence.css?ver=0.7" />
- <link rel="stylesheet" href="../css/deployment-opts.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/native-persistence.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/deployment-opts.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -456,6 +456,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/arch/multi-tier-storage.html b/arch/multi-tier-storage.html
index 912d03c..43b6352 100644
--- a/arch/multi-tier-storage.html
+++ b/arch/multi-tier-storage.html
@@ -17,12 +17,12 @@
property="og:description"
content="Apache Ignite multi-tier storage uses memory, disk, and Intel Optane as active storage tiers to provide the speed of memory with the consistency of disk-based databases without the need for memory warm-ups on restarts."
/>
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/native-persistence.css?ver=0.7" />
- <link rel="stylesheet" href="../css/multi-tier.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/native-persistence.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/multi-tier.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -365,7 +365,7 @@
<div class="innerhero__main">
<div class="innerhero__pre pb-3">Apache Ignite</div>
<h1 class="h1 innerhero__h1">Multi-Tier Storage</h1>
- <div class="innerhero__descr pt-2 h5">Store and access your data across memory <br />and disk with no compromises</div>
+ <div class="innerhero__descr pt-2 h5">Store and access your data across memory <br />and disk without compromise</div>
<div class="innerhero__action"><a class="button innerhero__button" href="https://ignite.apache.org/docs/latest/index">Start Coding</a></div>
</div>
<img class="innerhero__pic innerhero__pic--multitier" src="/img/usecases/in-memory-hero.svg" alt="Distributed In-Memory Cache" />
@@ -454,7 +454,7 @@
</div>
<div class="multitiers__right multitiers__text">
<h4 class="multitier3__h4 fz20 pb-1x">How It Works</h4>
- <p>100% of data is persisted to Ignite native persistence, and the same or smaller amount is cached in memory. The more data cached, the faster the performance.</p>
+ <p>100% of data is persisted to Ignite native persistence,and the same amount or less is cached in memory. The more data cached, the faster the performance.</p>
<p>Applications can query both in-memory and disk-only records transparently scaling beyond available memory capacity.</p>
<p>There is no need for memory warm-ups on restarts since Ignite can serve data from disk. SSD, Flash, HDD or Intel® Optane™ operating in the AppDirect Mode can be used as a storage device.</p>
<h4 class="multitier3__h4 fz20 pt-3 pb-2">Use-Cases</h4>
@@ -547,6 +547,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/arch/native-persistence.html b/arch/native-persistence.html
index e95db68..d213605 100644
--- a/arch/native-persistence.html
+++ b/arch/native-persistence.html
@@ -14,14 +14,14 @@
property="og:description"
content="Apache Ignite native persistence is a distributed, ACID, and SQL-compliant disk-based store. It let Ignite store more data on disk than it can cache in memory and to enable fast cluster restarts."
/>
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/native-persistence.css?ver=0.7" />
- <link rel="stylesheet" href="../js/vendor/highlight/default.min.css?ver=0.7" />
- <link rel="stylesheet" href="../js/vendor/highlight/night-owl.css?ver=0.7" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/native-persistence.css?ver=0.8" />
+ <link rel="stylesheet" href="../js/vendor/highlight/default.min.css?ver=0.8" />
+ <link rel="stylesheet" href="../js/vendor/highlight/night-owl.css?ver=0.8" />
<script src="../js/vendor/highlight/highlight.min.js"></script>
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -378,7 +378,7 @@
<div class="native1__block native1__block--bad">
<img class="native1__icon" src="/img/features/smile-doesnt-have.svg" alt="" />
<div class="native1__title fz20 pt-1x">Usually, in-memory caches and databases provide limited persistence capabilities.</div>
- <p class="pt-2">For instance, some solutions just do a backup copy of <br />the in-memory data purely for restart purposes.</p>
+ <p class="pt-2">For instance, some solutions create a backup copy of <br />the in-memory data purely for restart purposes.</p>
</div>
<div class="native1__block">
<img class="native1__icon" src="/img/features/smile-done.svg" alt="" />
@@ -395,7 +395,7 @@
<p class="pt-1x">100% of data is always stored on disk. You decide how much memory to allocate to your data.</p>
</article>
<article class="native2item">
- <h3 class="fz20 native2item__title">Seconds needed <br />for recovery</h3>
+ <h3 class="fz20 native2item__title">Just seconds needed <br />for recovery</h3>
<p class="pt-1x">Ignite becomes operational from disk instantaneously. There is no need to wait for the data to get preloaded on restarts.</p>
</article>
<article class="native2item">
@@ -455,7 +455,7 @@
<a href="https://ignite.apache.org/docs/latest/persistence/native-persistence.html#checkpointing">Checkpointing</a> is the process of copying dirty pages from the memory tier to the partition files
on disk.
</p>
- <p class="nativestepitem__small">A dirty page is a page that was updated in memory, was appended to the WAL, but was not written to the respective partition file on disk yet.</p>
+ <p class="nativestepitem__small">A dirty page is a page that has been updated in memory and appended to the WAL, but has not yet been written to the respective partition file on disk.</p>
</div>
</article>
<article class="nativestepitem">
@@ -593,6 +593,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/community.html b/community.html
index 6b976a0..999006f 100644
--- a/community.html
+++ b/community.html
@@ -11,11 +11,11 @@
<meta property="og:url" content="https://ignite.apache.org/community.html" />
<meta property="og:image" content="/img/og-pic.png" />
<meta property="og:description" content="Meet an Apache Ignite community and get help. Contribute to Ignite by helping answer user questions, coding, changing technical documentation, or becoming a committer and PMC member." />
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/communnity.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/communnity.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -1441,6 +1441,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/css/frontpage.css b/css/frontpage.css
index d628c23..c4f0701 100644
--- a/css/frontpage.css
+++ b/css/frontpage.css
@@ -1,19 +1,34 @@
.fronttop{
overflow: hidden;
- background: url(../img/frontpage/hero.svg) var(--dark) calc(50% + 405px) top no-repeat;
+ background: url(../img/frontpage/blue-grad.jpg) center top no-repeat;
+ background-size: 100% 100%;
+ position: relative;
+ /* background: url(../img/frontpage/hero.svg) var(--dark) calc(50% + 405px) top no-repeat; */
+}
+.fronttop__pic{
+ position: absolute;
+ left: calc(50% + 80px);
+ top: 0;
+ height: 100%;
}
@media (min-width:1600px){
.fronttop{
background-position: right top;
}
+ .fronttop__pic{
+ right: 0;
+ left: auto;
+ }
}
.fronttop .hdr{
background: none;
+ border-bottom-color: transparent;
}
.fronthero {
background: none;
padding-bottom: 19rem;
padding-top: 9rem;
+ color:#000;
}
.fronthero__button{
width: 190px;
@@ -497,9 +512,6 @@
@media (max-width:1199px){
- .fronttop{
- background-position-x: calc(50% + 260px);
- }
.frontcard__prises{
align-items: flex-start;
margin-bottom: -2rem;
@@ -599,6 +611,10 @@
@media (max-width:767px){
+ .fronttop__pic{
+ left: 0;
+ opacity: 0.3;
+ }
.fronthero{
padding-top: 7rem;
padding-bottom: 17rem;
diff --git a/download.html b/download.html
index 5397fbb..7336a57 100644
--- a/download.html
+++ b/download.html
@@ -11,16 +11,16 @@
<meta property="og:url" content="https://ignite.apache.org/download.html" />
<meta property="og:image" content="/img/og-pic.png" />
<meta property="og:description" content="Download Apache Ignite here and install in your environment. It’s for free – just select from one of the available options and download." />
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/native-persistence.css?ver=0.7" />
- <link rel="stylesheet" href="../css/download.css?ver=0.7" />
- <link rel="stylesheet" href="../js/vendor/highlight/default.min.css?ver=0.7" />
- <link rel="stylesheet" href="../js/vendor/highlight/night-owl.css?ver=0.7" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/native-persistence.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/download.css?ver=0.8" />
+ <link rel="stylesheet" href="../js/vendor/highlight/default.min.css?ver=0.8" />
+ <link rel="stylesheet" href="../js/vendor/highlight/night-owl.css?ver=0.8" />
<script src="../js/vendor/highlight/highlight.min.js"></script>
<script src="../js/vendor/highlight/xml.min.js"></script>
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -992,6 +992,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/events.html b/events.html
index f5ae289..1a92f8f 100644
--- a/events.html
+++ b/events.html
@@ -11,11 +11,11 @@
<meta property="og:url" content="https://ignite.apache.org/events.html" />
<meta property="og:image" content="/img/og-pic.png" />
<meta property="og:description" content="Join our upcoming events: in-memory computing meetups, Apache Ignite summits or conferences. Find an Apache Ignite meetup/group near you." />
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/events.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/events.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -3476,6 +3476,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/faq.html b/faq.html
index 6381eda..9216aea 100644
--- a/faq.html
+++ b/faq.html
@@ -11,12 +11,12 @@
<meta property="og:url" content="https://ignite.apache.org/faq.html" />
<meta property="og:image" content="/img/og-pic.png" />
<meta property="og:description" content="What is Apache Ignite? What is in-memory computing? Read the answers on our FAQ page." />
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/faq.css?ver=0.7" />
- <link rel="stylesheet" href="../css/tooling.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/faq.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/tooling.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -359,7 +359,7 @@
<div class="innerhero__main innerhero__main--long">
<h1 class="h1 innerhero__h1">Frequently Asked Questions <br />About Apache Ignite</h1>
<div class="innerhero__descr pt-5 h4">
- Ignite’s rich feature set enables it for a myriad of use cases. <br />
+ Ignite’s rich feature set means it has a myriad of use cases.<br />
Is Ignite a cache, transactional database, key-value store? <br />Find the answers below.
</div>
</div>
@@ -482,7 +482,7 @@
servers.
</p>
<p>
- At SQL level, Ignite supports atomic, but not yet transactional consistency. SQL transactions implementation is already
+ At SQL level, Ignite supports atomic but not yet transactional consistency. A SQL transactions implementation is already
<a href="https://cwiki.apache.org/confluence/display/IGNITE/IEP-3%3A+Transactional+SQL" target="_blank">in the works</a> and will be released in Ignite 3.
</p>
</div>
@@ -500,7 +500,7 @@
<article class="faqbox cardsimple">
<h3 class="faqbox__itemtitle h5">Is Ignite A Key-Value Store?</h3>
<div class="faqbox__anwser h5 pt-3">Yes</div>
- <div class="faqbox__text pt-3"><p>Ignite provides a feature-rich key-value API, that is JCache (JSR-107) compliant and supports Java, C++, .NET, and other programming languages.</p></div>
+ <div class="faqbox__text pt-3"><p>Ignite provides a feature-rich key-value API that is JCache (JSR-107) compliant and supports Java, C++, .NET, and other programming languages.</p></div>
<div class="cardsimple__bottom"><a class="cardsimple__button button button--shadow" href="/use-cases/key-value-store.html">Learn More: Distributed Key-Value Store</a></div>
</article>
</section>
@@ -572,6 +572,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/features/acid-transactions.html b/features/acid-transactions.html
index bbbabef..67df51d 100644
--- a/features/acid-transactions.html
+++ b/features/acid-transactions.html
@@ -17,12 +17,12 @@
property="og:description"
content="Apache Ignite can operate in a strongly consistent mode with full support for distributed ACID transactions. Ignite is an ACID compliant storage engine which can handle possible distributed failures properly to avoid data inconsistencies cluster-wide."
/>
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/native-persistence.css?ver=0.7" />
- <link rel="stylesheet" href="../css/acid-transactions.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/native-persistence.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/acid-transactions.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -381,28 +381,28 @@
</div>
<div class="acid1__item">
<div class="acid1__title fz20">Durability</div>
- <div class="acid1__text pt-3"><p>Multi-tier storage persists changes durably to disk. Committed transactions always survive failures, incomplete transactions are rolled back.</p></div>
+ <div class="acid1__text pt-3"><p>Multi-tier storage persists changes durably to disk. Committed transactions always survive failures, and incomplete transactions are rolled back.</p></div>
</div>
<div class="acid1__item">
<div class="acid1__title fz20">Fault-Tolerance</div>
- <div class="acid1__text pt-3"><p>The transactional engine avoids inconsistencies even if your transaction is failed in the middle of a commit.</p></div>
+ <div class="acid1__text pt-3"><p>The transactional engine avoids inconsistencies even if your transaction fails halfway through.</p></div>
</div>
</div>
</section>
<!-- /.acid1-->
<section class="acid2 container">
<h2 class="acid2__h2">
- To guarantee data consistency, durability and fault-tolerance<br />
+ To guarantee data consistency, durability and fault-tolerance,<br />
<strong>Ignite implements a two-phase commit protocol</strong>
</h2>
<div class="acid2__wrap flexi pt-5">
<div class="acid2__main">
- <p>In distributed systems, a transaction usually spans across multiple cluster nodes.</p>
+ <p>In distributed systems, a transaction usually spans multiple cluster nodes.</p>
<p>To handle possible distributed failures properly and avoid data inconsistencies cluster-wide, a two-phase commit protocol (2PC) is used.</p>
<h3 class="acid2__subtitle h5 pb-2">How ACID transactions work</h3>
<p>Whenever the records get updated within a transaction, Ignite keeps the transactional state in a local transaction map until the changes are committed.</p>
<p>From here, the data is transferred to the participating remote nodes. Only the nodes that hold primary or backup copies of the data participate in the transaction.</p>
- <p>If a transaction is mapped to a single node, then, Ignite optimizes the transaction execution by switching to the one-phase-commit (1PC) protocol.</p>
+ <p>If a transaction is mapped to a single node, then Ignite optimizes the transaction execution by switching to the one-phase-commit (1PC) protocol.</p>
</div>
<aside class="acid2__right"><img class="acid2__funcimg" src="/img/features/acid/acid-func.svg" alt="" /></aside>
</div>
@@ -437,7 +437,7 @@
</div>
<div class="acid3__col">
<h3 class="h5 pb-2">Transactions with external databases</h3>
- <p class="fz20 acid3__collead">Your transactions will be updated both in external database and in Apache Ignite</p>
+ <p class="fz20 acid3__collead">Your transactions will be updated both in the external database and in Apache Ignite</p>
<div class="acid3__small pt-4">
<p>
When Apache Ignite is used as a caching layer for an external database, such as RDBMS, transactions span the cached data in Ignite as well as the data persisted in a database
@@ -524,6 +524,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/features/compute-apis.html b/features/compute-apis.html
index c7de221..7001b7a 100644
--- a/features/compute-apis.html
+++ b/features/compute-apis.html
@@ -11,17 +11,17 @@
<meta property="og:url" content="https://ignite.apache.org/features/compute-apis.html" />
<meta property="og:image" content="/img/og-pic.png" />
<meta property="og:description" content="Apache Ignite compute APIs allow you to perform computations at high speeds. Achieve high performance, low latency, and linear scalability in data-intensive computing." />
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/native-persistence.css?ver=0.7" />
- <link rel="stylesheet" href="../css/compute-apis.css?ver=0.7" />
- <link rel="stylesheet" href="../js/vendor/highlight/night-owl.css?ver=0.7" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/native-persistence.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/compute-apis.css?ver=0.8" />
+ <link rel="stylesheet" href="../js/vendor/highlight/night-owl.css?ver=0.8" />
<script src="../js/vendor/highlight/highlight.min.js"></script>
<script src="../js/vendor/highlight/java.min.js"></script>
<script src="../js/vendor/highlight/xml.min.js"></script>
<script src="../js/vendor/highlight/csharp.min.js"></script>
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -618,6 +618,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/features/index.html b/features/index.html
index a980529..e6d86fa 100644
--- a/features/index.html
+++ b/features/index.html
@@ -11,11 +11,11 @@
<meta property="og:url" content="https://ignite.apache.org/features/" />
<meta property="og:image" content="/img/og-pic.png" />
<meta property="og:description" content="Apache Ignite set of components. Learn more about Apache Ignite product features on our website." />
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/features.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/features.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -553,6 +553,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/features/key-value-apis.html b/features/key-value-apis.html
index 446b54c..c3f8694 100644
--- a/features/key-value-apis.html
+++ b/features/key-value-apis.html
@@ -17,12 +17,12 @@
property="og:description"
content="Apache Ignite as a distributed key-value store is supported for different caching techniques. Ignite key-value APIs allow to create database key-value tables on-chain and increase processing performance."
/>
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/native-persistence.css?ver=0.7" />
- <link rel="stylesheet" href="../css/key-value-api.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/native-persistence.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/key-value-api.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -428,7 +428,7 @@
</div>
<div class="keyvalue__title">How it works</div>
<div class="keyvaluetext pt-2 pb-5">
- <p>It is applied for applications that require a consistent response time ranging <strong>in microseconds.</strong> Ignite automatically invalidates and updates the near cache.</p>
+ <p>It is applied to applications that require a consistent response time of a few <strong>microseconds.</strong> Ignite automatically invalidates and updates the near cache.</p>
<p>
Whenever the primary copy of a record gets updated on a server node, Ignite propagates the change to all the nodes that store the record’s backup copy, as well as to the applications
that keep the record’s copy in their near caches.
@@ -450,7 +450,7 @@
<section class="keyvalue4 container flexi pb-1">
<div class="keyvalue4__left">
<h3 class="keyvalue__title">ACID Transactions To Update Your Distributed Records Consistently</h3>
- <div class="keyvaluetext pt-2 pb-5"><p>Apache Ignite key-value APIs are fully transactional which means that data can be updated consistently and reliably.</p></div>
+ <div class="keyvaluetext pt-2 pb-5"><p>Apache Ignite key-value APIs are fully transactional, which means that data can be updated consistently and reliably.</p></div>
<div class="keyvalue__title">How it works</div>
<div class="keyvaluetext pt-2 pb-5">
<p>
@@ -536,6 +536,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/features/machinelearning.html b/features/machinelearning.html
index f3f04e2..19ede49 100644
--- a/features/machinelearning.html
+++ b/features/machinelearning.html
@@ -17,13 +17,13 @@
property="og:description"
content="Apache Ignite Machine Learning is a set of simple and efficient APIs to enable continuous learning. It relies on Ignite's multi-tier storage that bring massive scalability for machine learning and deep learning tasks."
/>
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/native-persistence.css?ver=0.7" />
- <link rel="stylesheet" href="../css/compute-apis.css?ver=0.7" />
- <link rel="stylesheet" href="../css/machinelearning.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/native-persistence.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/compute-apis.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/machinelearning.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -516,6 +516,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/features/multilanguage.html b/features/multilanguage.html
index af623a0..57ec822 100644
--- a/features/multilanguage.html
+++ b/features/multilanguage.html
@@ -4,13 +4,13 @@
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1" />
<title>Multi-language Support</title>
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/native-persistence.css?ver=0.7" />
- <link rel="stylesheet" href="../css/compute-apis.css?ver=0.7" />
- <link rel="stylesheet" href="../css/multilanguage.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/native-persistence.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/compute-apis.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/multilanguage.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -457,6 +457,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/features/service-apis.html b/features/service-apis.html
index 122cf22..c43fe20 100644
--- a/features/service-apis.html
+++ b/features/service-apis.html
@@ -17,18 +17,18 @@
property="og:description"
content="Apache Ignite Service Grid allows to deploy various types of singleton services in the cluster or multiple service instances. Build a fault-tolerant, scalable, high-performant, microservice-based solution with Apache Ignite."
/>
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/native-persistence.css?ver=0.7" />
- <link rel="stylesheet" href="../css/service.css?ver=0.7" />
- <link rel="stylesheet" href="../css/compute-apis.css?ver=0.7" />
- <link rel="stylesheet" href="../js/vendor/highlight/night-owl.css?ver=0.7" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/native-persistence.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/service.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/compute-apis.css?ver=0.8" />
+ <link rel="stylesheet" href="../js/vendor/highlight/night-owl.css?ver=0.8" />
<script src="../js/vendor/highlight/highlight.min.js"></script>
<script src="../js/vendor/highlight/java.min.js"></script>
<script src="../js/vendor/highlight/xml.min.js"></script>
<script src="../js/vendor/highlight/csharp.min.js"></script>
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -549,6 +549,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/features/sql.html b/features/sql.html
index 8093589..ce8df23 100644
--- a/features/sql.html
+++ b/features/sql.html
@@ -17,13 +17,13 @@
property="og:description"
content="Apache Ignite comes with an ANSI-99 compliant, horizontally scalable, and fault-tolerant SQL engine that allows you to interact with Ignite as with a regular SQL database. Ignite can function in a pure in-memory mode in which it shows the highest performance."
/>
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/native-persistence.css?ver=0.7" />
- <link rel="stylesheet" href="../css/compute-apis.css?ver=0.7" />
- <link rel="stylesheet" href="../css/sql.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/native-persistence.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/compute-apis.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/sql.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -381,7 +381,7 @@
<div class="dist__block flexi">
<div class="dist__info">
<h2 class="dist__h2 h4">Apache Ignite as a SQL Database</h2>
- <p class="dist__text">The native support for SQL let’s you work with Ignite as with a standard SQL database. Literally, you can use just SQL if your applications need nothing else:</p>
+ <p class="dist__text">The native support for SQL let’s you work with Ignite as with a standard SQL database. You can use simply SQL if your applications need nothing else:</p>
<div class="dist__items flexi">
<div class="dist__item">
<h3 class="dist__item-title">DDL commands</h3>
@@ -424,7 +424,7 @@
<section class="dist1">
<div class="container">
<h2 class="dist1__h2 h4">Join, Group and Aggregate Distributed Data Sets</h2>
- <div class="dist1__subtext">Whether you use a two or thousand-node cluster, you always can do the following:</div>
+ <div class="dist1__subtext">Whether you use a two or thousand-node cluster, you can always do the following:</div>
<div class="dist1__parts flexi">
<div class="dist1__part">group data</div>
<div class="dist1__part">join data</div>
@@ -437,18 +437,18 @@
<div class="dist1__blocks flexi">
<div class="dist1__block">
<h4 class="dist1__h4">Co-located joins</h4>
- <p class="dist1__texts">this is the most performant type of joins that avoids data shuffling between nodes and minimize network usage.</p>
+ <p class="dist1__texts">These are the most performant types of joins that avoid data shuffling between nodes and minimize network usage.</p>
<p class="dist1__texts pt-1">
This type of join is used if you join <a class="dist1__link" href="https://ignite.apache.org/docs/latest/data-modeling/affinity-collocation" target="_blank">partitioned and replicated tables</a> or partitioned tables that are
co-located with each other.
</p>
</div>
<div class="dist1__block">
- <h4 class="dist1__h4">Non-colocated joins:</h4>
- <p class="dist1__texts">less performant type of joins that join data of non-colocated tables. Ignite needs to shuffle data over the network to produce a correct result set.</p>
+ <h4 class="dist1__h4">Non-colocated joins</h4>
+ <p class="dist1__texts">A less performant type of join that joins data of non‑colocated tables. Ignite needs to shuffle data over the network to produce a correct result set.</p>
</div>
<div class="dist1__block">
- <h4 class="dist1__h4">Hash joins:</h4>
+ <h4 class="dist1__h4">Hash joins</h4>
<p class="dist1__texts">Ignite supports classic hash join algorithm that is more efficient than nested loop joins for many scenarios.</p>
</div>
</div>
@@ -465,7 +465,7 @@
<p class="dist2__text dist2__text1">Ignite caches data only in memory</p>
<details class="dist2__details">
<summary class="dist2__active"><img src="/img/features/sql/plus.svg" alt="sql-hero" /></summary>
- <div class="dist2__subtext"><p>In this mode, Ignite SQL performs the fastest way possible as long as all the data is served from memory with no usage of the disk tier at all.</p></div>
+ <div class="dist2__subtext"><p>In this mode, Ignite SQL carries out tasks as quickly as possible, as long as all the data is served from memory, with no usage of the disk tier at all.</p></div>
</details>
</div>
<div class="dist2__block">
@@ -478,7 +478,7 @@
<summary class="dist2__active"><img src="/img/features/sql/plus.svg" alt="sql-hero" /></summary>
<div class="dist2__subtext">
<p>Ignite persists 100% of data and indexes in the <a href="/arch/native-persistence.html">native persistence</a> while caching as much as possible in memory.</p>
- <p class="pt-1">Ignite SQL engine does not require to cache an entire data set in memory to operate correctly.</p>
+ <p class="pt-1">Ignite SQL engine does not require the caching of entire data set in memory to operate correctly.</p>
<p class="pt-1">If the engine finds that a record is not cached, then it will read the record from disk. Your application only executes SQL queries, and Ignite gets the records from both memory and disk automatically.</p>
<p class="pt-1">On cluster restarts, Ignite reads data and indexes from disk, eliminating the need for memory warm-up, which significantly decreases downtime.</p>
</div>
@@ -493,9 +493,9 @@
<details class="dist2__details">
<summary class="dist2__active"><img src="/img/features/sql/plus.svg" alt="sql-hero" /></summary>
<div class="dist2__subtext">
- <p>In this mode, the Ignite SQL engine requires caching all the data needed for distributed queries in memory since the engine currently does not support federated queries.</p>
+ <p>In this mode, the Ignite SQL engine requires caching of all the data needed for distributed queries in memory, since the engine does not currently support federated queries.</p>
<p class="pt-1">
- If federated queries between Ignite and an external database are required, then you can consider Ignite integration for Spark, where the DataFrames API can join the data stored in Ignite and other systems.
+ If federated queries between Ignite and an external database are required, then you can consider Ignite integration for Spark, where the DataFrames API can combine the data stored in Ignite and other systems.
</p>
</div>
</details>
@@ -580,6 +580,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/features/streaming.html b/features/streaming.html
index 195f7d4..f0801d6 100644
--- a/features/streaming.html
+++ b/features/streaming.html
@@ -14,13 +14,13 @@
property="og:description"
content="Apache Ignite data loading, streaming, and real-time processing capabilities allow to inject large amounts of data into an Ignite cluster in a scalable and fault-tolerant way. Learn more here."
/>
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/native-persistence.css?ver=0.7" />
- <link rel="stylesheet" href="../css/compute-apis.css?ver=0.7" />
- <link rel="stylesheet" href="../css/streaming.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/native-persistence.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/compute-apis.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/streaming.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -539,6 +539,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/features/tooling.html b/features/tooling.html
index 00833f7..5bffd1b 100644
--- a/features/tooling.html
+++ b/features/tooling.html
@@ -4,11 +4,11 @@
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1" />
<title>Tooling</title>
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/tooling.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/tooling.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -560,6 +560,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/img/frontpage/background.jpg b/img/frontpage/background.jpg
new file mode 100644
index 0000000..37d52e8
--- /dev/null
+++ b/img/frontpage/background.jpg
Binary files differ
diff --git a/img/frontpage/blue-grad.jpg b/img/frontpage/blue-grad.jpg
new file mode 100644
index 0000000..37d52e8
--- /dev/null
+++ b/img/frontpage/blue-grad.jpg
Binary files differ
diff --git a/img/frontpage/hero-white.svg b/img/frontpage/hero-white.svg
new file mode 100644
index 0000000..9ddefa0
--- /dev/null
+++ b/img/frontpage/hero-white.svg
@@ -0,0 +1,102 @@
+<svg width="786" height="888" viewBox="0 0 786 888" fill="none" xmlns="http://www.w3.org/2000/svg">
+<mask id="mask0_1_46" style="mask-type:alpha" maskUnits="userSpaceOnUse" x="0" y="-2" width="786" height="890">
+<rect y="-2" width="786" height="890" fill="#2D2D2D"/>
+</mask>
+<g mask="url(#mask0_1_46)">
+<path d="M839.593 132.633L185.433 833.478" stroke="url(#paint0_linear_1_46)" stroke-width="2"/>
+<path d="M427.898 -2.16699C427.898 -2.16699 793.003 155.1 483.335 483.056C173.667 811.011 156.255 833.478 156.255 833.478" stroke="url(#paint1_linear_1_46)" stroke-width="2"/>
+<path d="M398.72 -2.16699C398.72 -2.16699 763.825 155.1 454.157 483.056C144.489 811.011 127.077 833.478 127.077 833.478" stroke="url(#paint2_linear_1_46)" stroke-width="2"/>
+<path d="M369.548 -2.16699C369.548 -2.16699 734.653 155.1 424.985 483.056C115.317 811.011 97.9046 833.478 97.9046 833.478" stroke="url(#paint3_linear_1_46)" stroke-width="2"/>
+<path d="M334.531 -2.16699C334.531 -2.16699 699.636 155.1 389.968 483.056C80.2999 811.011 62.8877 833.478 62.8877 833.478" stroke="url(#paint4_linear_1_46)" stroke-width="2"/>
+<path d="M859.431 138.469L205.271 839.314" stroke="url(#paint5_linear_1_46)" stroke-width="2"/>
+<path d="M879.275 144.304L225.114 845.149" stroke="url(#paint6_linear_1_46)" stroke-width="2"/>
+<path d="M899.118 150.139L244.958 850.984" stroke="url(#paint7_linear_1_46)" stroke-width="2"/>
+<path d="M918.962 155.975L264.801 856.82" stroke="url(#paint8_linear_1_46)" stroke-width="2"/>
+<path d="M938.805 161.811L284.645 862.655" stroke="url(#paint9_linear_1_46)" stroke-width="2"/>
+<path d="M958.637 167.646L304.477 868.491" stroke="url(#paint10_linear_1_46)" stroke-width="2"/>
+<path d="M978.481 173.482L324.32 874.327" stroke="url(#paint11_linear_1_46)" stroke-width="2"/>
+<path d="M998.324 179.318L344.164 880.163" stroke="url(#paint12_linear_1_46)" stroke-width="2"/>
+<path d="M1018.16 185.153L363.996 885.997" stroke="url(#paint13_linear_1_46)" stroke-width="2"/>
+<path d="M1038 190.988L383.839 891.833" stroke="url(#paint14_linear_1_46)" stroke-width="2"/>
+<path d="M358.103 511.218L363.86 516.236L365.307 508.875L358.103 511.218Z" fill="#ED1C24"/>
+<path d="M446.285 486.796L452.433 491.326L453.273 483.872L446.285 486.796Z" fill="#ED1C24"/>
+<path d="M502.444 514.921L508.194 519.946L509.65 512.587L502.444 514.921Z" fill="#ED1C24"/>
+<path d="M510.047 642.102L515.75 647.179L517.274 639.834L510.047 642.102Z" fill="#ED1C24"/>
+<path d="M493.55 752.356L487.71 747.435L486.387 754.819L493.55 752.356Z" fill="#ED1C24"/>
+<path d="M675.066 526.497L667.746 528.672L673.188 533.835L675.066 526.497Z" fill="#ED1C24"/>
+<path d="M482.707 407.442L489.324 411.255L489.324 403.753L482.707 407.442Z" fill="#ED1C24"/>
+</g>
+<defs>
+<linearGradient id="paint0_linear_1_46" x1="512.513" y1="132.633" x2="512.513" y2="833.478" gradientUnits="userSpaceOnUse">
+<stop stop-color="white"/>
+<stop offset="0.928773" stop-color="#E8F2FA"/>
+<stop offset="1" stop-color="white"/>
+</linearGradient>
+<linearGradient id="paint1_linear_1_46" x1="483.335" y1="132.633" x2="483.335" y2="833.478" gradientUnits="userSpaceOnUse">
+<stop stop-color="white"/>
+<stop offset="1" stop-color="#E8F2FA"/>
+</linearGradient>
+<linearGradient id="paint2_linear_1_46" x1="454.157" y1="132.633" x2="454.157" y2="833.478" gradientUnits="userSpaceOnUse">
+<stop stop-color="white"/>
+<stop offset="1" stop-color="#E8F2FA"/>
+</linearGradient>
+<linearGradient id="paint3_linear_1_46" x1="424.985" y1="132.633" x2="424.985" y2="833.478" gradientUnits="userSpaceOnUse">
+<stop stop-color="white"/>
+<stop offset="1" stop-color="#E8F2FA"/>
+</linearGradient>
+<linearGradient id="paint4_linear_1_46" x1="389.968" y1="132.633" x2="389.968" y2="833.478" gradientUnits="userSpaceOnUse">
+<stop stop-color="white"/>
+<stop offset="1" stop-color="#E8F2FA"/>
+</linearGradient>
+<linearGradient id="paint5_linear_1_46" x1="532.351" y1="138.469" x2="532.351" y2="839.314" gradientUnits="userSpaceOnUse">
+<stop stop-color="white"/>
+<stop offset="0.928773" stop-color="#E8F2FA"/>
+<stop offset="1" stop-color="white"/>
+</linearGradient>
+<linearGradient id="paint6_linear_1_46" x1="552.194" y1="144.304" x2="552.194" y2="845.149" gradientUnits="userSpaceOnUse">
+<stop stop-color="white"/>
+<stop offset="0.928773" stop-color="#E8F2FA"/>
+<stop offset="1" stop-color="white"/>
+</linearGradient>
+<linearGradient id="paint7_linear_1_46" x1="572.038" y1="150.139" x2="572.038" y2="850.984" gradientUnits="userSpaceOnUse">
+<stop stop-color="white"/>
+<stop offset="0.928773" stop-color="#E8F2FA"/>
+<stop offset="1" stop-color="white"/>
+</linearGradient>
+<linearGradient id="paint8_linear_1_46" x1="591.881" y1="155.975" x2="591.881" y2="856.82" gradientUnits="userSpaceOnUse">
+<stop stop-color="white"/>
+<stop offset="0.928773" stop-color="#E8F2FA"/>
+<stop offset="1" stop-color="white"/>
+</linearGradient>
+<linearGradient id="paint9_linear_1_46" x1="611.725" y1="161.811" x2="611.725" y2="862.655" gradientUnits="userSpaceOnUse">
+<stop stop-color="white"/>
+<stop offset="0.928773" stop-color="#E8F2FA"/>
+<stop offset="1" stop-color="white"/>
+</linearGradient>
+<linearGradient id="paint10_linear_1_46" x1="631.557" y1="167.646" x2="631.557" y2="868.491" gradientUnits="userSpaceOnUse">
+<stop stop-color="white"/>
+<stop offset="0.928773" stop-color="#E8F2FA"/>
+<stop offset="1" stop-color="white"/>
+</linearGradient>
+<linearGradient id="paint11_linear_1_46" x1="651.401" y1="173.482" x2="651.401" y2="874.327" gradientUnits="userSpaceOnUse">
+<stop stop-color="white"/>
+<stop offset="0.928773" stop-color="#E8F2FA"/>
+<stop offset="1" stop-color="white"/>
+</linearGradient>
+<linearGradient id="paint12_linear_1_46" x1="671.244" y1="179.318" x2="671.244" y2="880.163" gradientUnits="userSpaceOnUse">
+<stop stop-color="white"/>
+<stop offset="0.928773" stop-color="#E8F2FA"/>
+<stop offset="1" stop-color="white"/>
+</linearGradient>
+<linearGradient id="paint13_linear_1_46" x1="691.076" y1="185.153" x2="691.076" y2="885.997" gradientUnits="userSpaceOnUse">
+<stop stop-color="white"/>
+<stop offset="0.928773" stop-color="#E8F2FA"/>
+<stop offset="1" stop-color="white"/>
+</linearGradient>
+<linearGradient id="paint14_linear_1_46" x1="710.92" y1="190.988" x2="710.92" y2="891.833" gradientUnits="userSpaceOnUse">
+<stop stop-color="white"/>
+<stop offset="0.928773" stop-color="#E8F2FA"/>
+<stop offset="1" stop-color="white"/>
+</linearGradient>
+</defs>
+</svg>
diff --git a/index.html b/index.html
index 65f2148..1d4dc32 100644
--- a/index.html
+++ b/index.html
@@ -11,19 +11,19 @@
<meta property="og:url" content="https://ignite.apache.org/" />
<meta property="og:image" content="/img/og-pic.png" />
<meta property="og:description" content="Apache Ignite is a best distributed database management system for high-performance computing with in-memory speed. Learn how to use the Ignite decentralized database system and get started." />
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../js/vendor/highlight/default.min.css?ver=0.7" />
- <link rel="stylesheet" href="../js/vendor/highlight/night-owl.css?ver=0.7" />
- <link rel="stylesheet" href="../js/vendor/swiper/swiper-bundle.min.css?ver=0.7" />
- <link rel="stylesheet" href="../css/native-persistence.css?ver=0.7" />
- <link rel="stylesheet" href="../css/events.css?ver=0.7" />
- <link rel="stylesheet" href="../css/tooling.css?ver=0.7" />
- <link rel="stylesheet" href="../css/frontpage.css?ver=0.7" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../js/vendor/highlight/default.min.css?ver=0.8" />
+ <link rel="stylesheet" href="../js/vendor/highlight/night-owl.css?ver=0.8" />
+ <link rel="stylesheet" href="../js/vendor/swiper/swiper-bundle.min.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/native-persistence.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/events.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/tooling.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/frontpage.css?ver=0.8" />
<script src="../js/vendor/highlight/highlight.min.js"></script>
<script src="../js/vendor/swiper/swiper-bundle.min.js"></script>
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -179,7 +179,7 @@
</div>
</div>
<!-- MOBILE MENU END -->
- <header class="hdr hdr__dark jsHdrBase">
+ <header class="hdr hdr__white jsHdrBase">
<div class="hdr__wrap flexi jsHdrLine">
<button class="hdr__burger" data-menumodal="#jsMenuModal"><img src="/img/menu.svg" alt="" /></button
><a class="hdr__logo" href="/"><img class="hdr__logoimg hdr__logo--white" src="/img/logo-white.svg" alt="" /><img class="hdr__logoimg hdr__logo--black" src="/img/logo.svg" alt="" /></a
@@ -362,11 +362,12 @@
</header>
<div class="dropmenu__back"></div>
<header class="hdrfloat hdr__white jsHdrFloatBase"></header>
+ <img class="fronttop__pic" src="/img/frontpage/hero-white.svg" alt="" />
<section class="innerhero fronthero">
<div class="container innerhero__cont">
<div class="innerhero__main innerhero__main--long">
<h1 class="h1 innerhero__h1 innerhero__mega">Distributed Database For <br />High‑Performance Applications <br />With In‑Memory Speed</h1>
- <div class="innerhero__h2 h4 pt-2">Scale Across Memory And Disk With No Compromises</div>
+ <div class="innerhero__h2 h4 pt-2">Scale Across Memory And Disk Without Compromise</div>
<div class="innerhero__action pt-5"><a class="button fronthero__button" href="https://ignite.apache.org/docs/latest/index">Start Coding</a></div>
</div>
</div>
@@ -393,7 +394,7 @@
</div></a
><!-- /.frontcard--><a class="frontcard" href="/use-cases/provenusecases.html"
><div class="frontcard__network"><img src="/img/frontpage/b1-planet.svg" alt="" /></div>
- <div class="frontcard__title h5 pt-3">Leading companies around the world select Ignite to speed and scale applications used by millions of people daily</div></a
+ <div class="frontcard__title h5 pt-3">Leading companies around the world select Ignite to speed up and scale applications used by millions of people daily</div></a
><!-- /.frontcard-->
</aside>
<!-- /.fronttopcards-->
@@ -665,7 +666,7 @@
<li>Financial Services</li>
<li>Retail</li>
<li>Biotech</li>
- <li>And others</li>
+ <li>Others</li>
</ul>
<div class="frontstories__sliderwrap">
<button class="ctrl ctrl--prev"><img src="/img/frontpage/icon-slider-arrow.svg" alt="" /></button><button class="ctrl ctrl--next"><img src="/img/frontpage/icon-slider-arrow.svg" alt="" /></button>
@@ -774,7 +775,7 @@
<a class="frontconfcard frontconfcard--red" href="https://www.meetup.com/Apache-Ignite-Virtual-Meetup/" target="_blank"
><div class="frontconfs__iconwrap pb-3"><img src="/img/frontpage/events/001.svg" alt="" /></div>
<h4 class="h5 frontconfcard__title pb-2">Ignite Virtual Meetup</h4>
- <p>Experts and practitioners give <strong>online-talks and presentations</strong> and share their Apache Ignite experience.</p>
+ <p>Experts and practitioners give <strong>online talks and presentations</strong> and share their Apache Ignite experience.</p>
<div class="frontconfcard__bottom">
<p class="capstext">Online</p>
<div class="frontconfcard__cal">Regularly</div>
@@ -834,10 +835,10 @@
<div class="frontresitem__text">Dozens of essential videos and webinar <br />recordings</div></a
><a class="frontresitem flexi frontresitem--rose" href="/resources.html#training"
><div class="frontresitem__icon"><img src="/img/frontpage/res-vebinar.svg" alt="" /></div>
- <div class="frontresitem__text">Trainings and courses that help building high-performance and data-intensive applications with the Apache Ignite</div></a
+ <div class="frontresitem__text">Trainings and courses that help with building high‑performance and data-intensive applications with the Apache Ignite</div></a
><a class="frontresitem flexi frontresitem--rose" href="https://www.shamimbhuiyan.com/ignitebook" target="_blank"
><div class="frontresitem__icon"><img src="/img/frontpage/res-book.svg" alt="" /></div>
- <div class="frontresitem__text">Apache Ignite book to expand your knowledge <br />in in-memory computing and distributed databases</div></a
+ <div class="frontresitem__text">Apache Ignite book to expand your knowledge <br />in in‑memory computing and distributed databases</div></a
>
</div>
</div>
@@ -910,6 +911,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/resources.html b/resources.html
index c5584d9..4e3d0a2 100644
--- a/resources.html
+++ b/resources.html
@@ -11,12 +11,12 @@
<meta property="og:url" content="https://ignite.apache.org/resources.html" />
<meta property="og:image" content="/img/og-pic.png" />
<meta property="og:description" content="Explore our collection of videos, webinar recordings, examples, and other Ignite resources. Download the Apache Ignite book." />
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/communnity.css?ver=0.7" />
- <link rel="stylesheet" href="../css/resources.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/communnity.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/resources.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -464,7 +464,7 @@
><span class="comvideo__txt comvideo__txt--medium">Distributed Computing <br />With Apache Ignite</span><span class="comvideo__sub undefined">Webinar <br />recording</span><img src="/img/resourses/video.png" alt=""
/></a>
</div>
- <div class="comvideo__descr pt-2"><p>In this video, we show how to design and execute distributed computations considering all the pros and cons.</p></div>
+ <div class="comvideo__descr pt-2"><p>In this video, we demonstrate how to design and execute distributed computations, and consider all the pros and cons.</p></div>
</article>
<article class="comvideo">
<div class="comvideo__box">
@@ -504,8 +504,8 @@
</section>
<!-- /.resvideos-->
<section class="rescourses container" id="training">
- <h2 class="h4 resicontitle flexi"><img src="/img/resourses/icon-training.svg" alt="" /><span>Trainings and Courses</span></h2>
- <p class="pt-2 h5">Enhance your knowledge in building high-performance and <br />data-intensive applications with the Apache Ignite capabilities.</p>
+ <h2 class="h4 resicontitle flexi"><img src="/img/resourses/icon-training.svg" alt="" /><span>Training and Courses</span></h2>
+ <p class="pt-2 h5">Enhance your knowledge of building high-performance and <br />data-intensive applications with the Apache Ignite capabilities.</p>
<div class="rescourses__wrap pt-5">
<article class="rescourse cardsimple">
<p class="fz20 rescourse__title pb-2 maxline3">Apache Ignite Management <br />And Monitoring Guide</p>
@@ -613,7 +613,7 @@
<!-- /.faqblock-->
<article class="faqblock flexi">
<h3 class="faqblock__title faqblock__title--simple h5">
- <span>Report about bugs, possible <br />improvements and ctr.</span>
+ <span>Report bugs, possible <br />improvements and ctr.</span>
</h3>
<div class="faqblock__right">
<p class="faqblock__rightitle">By e-mail</p>
@@ -698,6 +698,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/use-cases.html b/use-cases.html
index 6da01b7..7ca444e 100644
--- a/use-cases.html
+++ b/use-cases.html
@@ -11,11 +11,11 @@
<meta property="og:url" content="https://ignite.apache.org/use-cases.html" />
<meta property="og:image" content="/img/og-pic.png" />
<meta property="og:description" content="The most common use-cases for Apache Ignite. Learn more how companies deploy Apache Ignite in production." />
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="/css/usecases.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/usecases.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -503,6 +503,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/use-cases/digital-integration-hub.html b/use-cases/digital-integration-hub.html
index 7d57f08..6652a91 100644
--- a/use-cases/digital-integration-hub.html
+++ b/use-cases/digital-integration-hub.html
@@ -17,13 +17,13 @@
property="og:description"
content="Apache Ignite functions as a low-latency and shared store of the digital integration hub architecture that caches and persists data sets scattered across many disjointed back-end databases and systems."
/>
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/native-persistence.css?ver=0.7" />
- <link rel="stylesheet" href="../css/compute-apis.css?ver=0.7" />
- <link rel="stylesheet" href="../css/digital-hub.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/native-persistence.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/compute-apis.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/digital-hub.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -610,6 +610,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/use-cases/hadoop-acceleration.html b/use-cases/hadoop-acceleration.html
index 1df9a94..4a96de5 100644
--- a/use-cases/hadoop-acceleration.html
+++ b/use-cases/hadoop-acceleration.html
@@ -17,14 +17,14 @@
property="og:description"
content="Achieve the performance acceleration of Hadoop-based systems by deploying Ignite as an in-memory computing platform designated for low-latency, high-throughput and real-time operations while Hadoop continues to be used for long-running OLAP workloads."
/>
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/native-persistence.css?ver=0.7" />
- <link rel="stylesheet" href="../css/compute-apis.css?ver=0.7" />
- <link rel="stylesheet" href="../css/digital-hub.css?ver=0.7" />
- <link rel="stylesheet" href="../css/hadoop.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/native-persistence.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/compute-apis.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/digital-hub.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/hadoop.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -414,7 +414,7 @@
Depending on the data volume and available memory capacity, you can enable<a href="/arch/native-persistence.html" target="_blank"> Ignite native persistence</a> to store historical data sets on disk while dedicating a memory
space for operational records.
</p>
- <p class="doop3__subtext pt-1">You can continue to use Hadoop as storage for less frequently used data or for long-running and ad-hoc analytical queries.</p>
+ <p class="doop3__subtext pt-1">You can continue to use Hadoop as storage for less frequently-used data or for long-running and ad-hoc analytical queries.</p>
<div class="fz20 doop3__number">02</div>
<p class="doop3__subtext">
Your applications and services should use Ignite native APIs to process the data residing in the in-memory cluster. Ignite provides SQL, compute (aka. map-reduce), and machine learning APIs for various data processing needs.
@@ -565,6 +565,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/use-cases/high-performance-computing.html b/use-cases/high-performance-computing.html
index 1ef4a8d..42513c8 100644
--- a/use-cases/high-performance-computing.html
+++ b/use-cases/high-performance-computing.html
@@ -17,12 +17,12 @@
property="og:description"
content="Apache Ignite enables high-performance computing by providing APIs for data and compute-intensive calculations. Using Ignite as a HPC cluster, you can turn your commodity hardware or cloud environment into a distributed supercomputer."
/>
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/native-persistence.css?ver=0.7" />
- <link rel="stylesheet" href="../css/high-performance-computing.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/native-persistence.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/high-performance-computing.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -378,12 +378,12 @@
<h3 class="h5 high1__title">What is high-performance computing?</h3>
<div class="high1__text pt-3 pb-5">
<p>High-performance computing is the ability to process data and perform complex calculations at high speeds.</p>
- <p>You keep all your data on the cluster node and execute your kilobyte-size custom code over petabytes of data avoiding network-like utilization.</p>
+ <p>You keep all your data on the cluster node and execute your kilobyte-size custom code over petabytes of data, avoiding network-like utilization.</p>
</div>
<h3 class="h5 high1__title">How it works</h3>
<div class="high1__text pt-2">
<div class="high1__sub pb-2">In traditional disk-based systems, <br />such as relational or NoSQL databases</div>
- <p>Client applications usually bring data from servers, use the records for local calculations, and discard the data as soon as the business task is complete.</p>
+ <p>Client applications usually bring data from servers, use the records for local calculations, and discard the data as soon as the business task is completed.</p>
<p>This approach does not scale well if a significant volume of data gets transferred over the network.</p>
<div class="high1__sub pt-2 pb-2">In in-memory computing systems, <br />such as Apache Ignite</div>
<p>
@@ -464,7 +464,7 @@
<div class="highicons__item">
<div class="highicons__iconwrap flexi"><img class="highicons__icon" src="/img/usecases/high-peformance/icon-perf5.svg" alt="" /></div>
<div class="highicons__title">Biotech</div>
- <div class="highicons__descr">e.g. drugs and vaccines discovery, sequencing DNA</div>
+ <div class="highicons__descr">e.g. drug and vaccine discovery, sequencing DNA</div>
</div>
</div>
</section>
@@ -476,8 +476,8 @@
<div class="highcases__subtitle pb-2">Personalized websites with dynamically changing content</div>
<p class="pb-3">Whenever you visit Amazon, Walmart, Booking, or other websites, you see personalized content, such as relevant deals made especially for you.</p>
<p>
- Personalized content considering your age, location, preferences, and previous interactions is being processed and displayed in few seconds thanks to high-performance computing tasks that process gigabytes of data within a
- second.
+ Personalized content that takes your age, location, preferences, and previous interactions into consideration is processed and displayed in just a few seconds thanks to high-performance computing tasks that process gigabytes of
+ data within a second.
</p>
</div>
<div class="highcases__topright">
@@ -516,7 +516,7 @@
/></a>
</div>
<div class="comvideo__descr pt-1">
- <p><strong>nference.ai:</strong> high-performance compute APIs used to define different statistical analyses and execute numerical data in real-time.</p>
+ <p><strong>nference.ai:</strong> high-performance compute APIs used to define different statistical analyses and execute numerical data in real time.</p>
</div>
</article>
</div>
@@ -543,7 +543,7 @@
</div>
<div class="highcases__two pt-4">
<div class="highcases__subtitle pb-2">Real-time analytics enables fast and precise decisions</div>
- <p>High-performance computing allows the processing of unlimited data sets, <br />with analyzation taking only seconds.</p>
+ <p>High-performance computing allows the processing of unlimited data sets, <br />with analysis taking only seconds.</p>
<div class="highcases__twowrap flexi pt-5">
<div class="highcases__twoitem">
<article class="comvideo">
@@ -641,6 +641,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/use-cases/in-memory-cache.html b/use-cases/in-memory-cache.html
index 7271f88..6c2210a 100644
--- a/use-cases/in-memory-cache.html
+++ b/use-cases/in-memory-cache.html
@@ -17,13 +17,13 @@
property="og:description"
content="Apache Ignite enables high-performance computing by providing APIs for data and compute-intensive calculations. Using Ignite as a HPC cluster, you can turn your commodity hardware or cloud environment into a distributed supercomputer."
/>
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/native-persistence.css?ver=0.7" />
- <link rel="stylesheet" href="../css/digital-hub.css?ver=0.7" />
- <link rel="stylesheet" href="../css/in-memory-cache.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/native-persistence.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/digital-hub.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/in-memory-cache.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -377,7 +377,7 @@
<!-- /.innerhero-->
<section class="inmememor1 container">
<header class="blockheader blockheader--spl flexi">
- <h2 class="capstext pb-3">What Is In-Memory Cache</h2>
+ <h2 class="capstext pb-3">What Is In-Memory Cache?</h2>
<div class="inmememor1__text">
<p>In-memory cache is a storage layer placed between applications and databases. The cache keeps your hot data in memory to offload existing databases and accelerate applications.</p>
</div>
@@ -397,7 +397,7 @@
</div>
<div class="inmememor-adv__item">
<h3 class="h4">Scale</h3>
- <div class="inmememor-adv__text">Horizontal scalability lets you grow the cluster unlimitedly to accommodate <br />data size and throughput.</div>
+ <div class="inmememor-adv__text">Horizontal scalability lets you grow the cluster size to an unlimited extent to accommodate data size and throughput.</div>
</div>
</div>
</div>
@@ -483,16 +483,16 @@
</div>
</div>
<div class="inmememor3__bottom">
- <h3 class="fz20">Cach-Aside Deployment And Native Persistence</h3>
+ <h3 class="fz20">Cache-Aside Deployment And Native Persistence</h3>
<div class="inmememor3__botwrap flexi pt-3">
<div class="inmememor2__left">
<p>
When Apache Ignite is deployed in a cache-aside configuration, its native persistence can be used as a disk store for Ignite datasets.
- <a href="/arch/native-persistence.html">Native persistence</a> allows for elimination of the time-consuming cache warm-up step.
+ <a href="/arch/native-persistence.html">Native persistence</a> allows for the elimination of the time-consuming cache warm-up step.
</p>
<p>
As native persistence maintains a full copy of data on disk, you can cache a subset of records in memory. If a required data record is missing from memory, then Ignite reads
- the record from the disk automatically, regardless of which API you use — whether SQL, key-value, or scan queries.
+ the record from the disk automatically, regardless of which API you use — be it SQL, key-value, or scan queries.
</p>
</div>
<div class="inmememor2__right">
@@ -599,6 +599,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/use-cases/in-memory-data-grid.html b/use-cases/in-memory-data-grid.html
index 70e88b7..13a998b 100644
--- a/use-cases/in-memory-data-grid.html
+++ b/use-cases/in-memory-data-grid.html
@@ -11,15 +11,15 @@
<meta property="og:url" content="https://ignite.apache.org/use-cases/in-memory-data-grid.html" />
<meta property="og:image" content="/img/og-pic.png" />
<meta property="og:description" content="The Apache Ignite in-memory data grid accelerates and scales out distributed databases, services, and APIs. Learn more about an IMDG with Apache Ignite." />
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/native-persistence.css?ver=0.7" />
- <link rel="stylesheet" href="../css/compute-apis.css?ver=0.7" />
- <link rel="stylesheet" href="../css/digital-hub.css?ver=0.7" />
- <link rel="stylesheet" href="../css/database.css?ver=0.7" />
- <link rel="stylesheet" href="../css/datagrid.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/native-persistence.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/compute-apis.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/digital-hub.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/database.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/datagrid.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -385,7 +385,7 @@
<h2 class="compute2__h2">In-Memory Data Grid Overview</h2>
<div class="hub1__block flexi">
<div class="hub1__info">
- <h3 class="h5 hub1__title">What is an in-memory data-grid?</h3>
+ <h3 class="h5 hub1__title">What is an in-memory data grid?</h3>
<p class="hub1__text">An in-memory data grid (IMDG) is an advanced read-through/write-through cache that is deployed on top of multiple databases.</p>
<p class="hub1__text">Applications write to and read from the grid, and the grid propagates changes to the underlying data stores in a consistent way.</p>
<h3 class="h5 hub1__title hub1__titleend">How does an in-memory data grid work?</h3>
@@ -609,6 +609,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/use-cases/in-memory-database.html b/use-cases/in-memory-database.html
index 82360f5..8e8a356 100644
--- a/use-cases/in-memory-database.html
+++ b/use-cases/in-memory-database.html
@@ -17,14 +17,14 @@
property="og:description"
content="Apache Ignite, as the best open source in-memory database, is a high-performance system-of-records that can store and query large data sets from memory and disk without requiring to warm up the memory tier on cluster restarts."
/>
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/native-persistence.css?ver=0.7" />
- <link rel="stylesheet" href="../css/compute-apis.css?ver=0.7" />
- <link rel="stylesheet" href="../css/digital-hub.css?ver=0.7" />
- <link rel="stylesheet" href="../css/database.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/native-persistence.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/compute-apis.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/digital-hub.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/database.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -386,7 +386,7 @@
<div class="hub1__info">
<h3 class="h5 hub1__title">What is an in-memory database?</h3>
<p class="hub1__text">An in-memory database (IMDB) is a data management system that stores data primarily in the computer’s main memory.</p>
- <h3 class="h5 hub1__title hub1__titleend">How an in-memory database works?</h3>
+ <h3 class="h5 hub1__title hub1__titleend">How does an in-memory database work?</h3>
<p class="hub1__text">In-memory databases rely on spinning disks for data storage. IMDBs allow mission-critical applications to benefit from faster response times than disk-based databases.</p>
</div>
<img class="hub1__image" src="/img/usecases/database/image.svg" alt="image" />
@@ -396,11 +396,11 @@
<!-- /.hub1 -->
<section class="base1">
<div class="container">
- <h2 class="base1__h2 h5">Apache Ignite as a distributed in-memory database scales horizontally across memory and disk with no compromises</h2>
+ <h2 class="base1__h2 h5">Apache Ignite as a distributed in-memory database scales horizontally across memory and disk without compromise</h2>
<div class="base1__blocks flexi">
<div class="base1__block">
<p class="base1__text">Apache Ignite works with memory, disk, and Intel Optane as active storage tiers.</p>
- <p class="base1__text pt-1">This <a href="/arch/multi-tier-storage.html">multi-tier</a> architecture combines, in one system, the advantages of in-memory computing with disk durability and strong consistency.</p>
+ <p class="base1__text pt-1">This <a href="/arch/multi-tier-storage.html">multi-tier</a> architecture combines the advantages of in-memory computing with disk durability and strong consistency, all in one system.</p>
</div>
<div class="base1__block">
<div class="base1__item flexi">
@@ -428,7 +428,7 @@
<div class="compute2-points__item fz20"></div>
<div class="compute2item__block">
<h3 class="fz20 compute2item__title">Instantaneous cluster restarts</h3>
- <p class="compute2__text base2__text">Ignite becomes fully operational from disk upon a cluster startup or restarts without requiring to preload or warm up the memory tier.</p>
+ <p class="compute2__text base2__text">Ignite becomes fully operational from disk upon a cluster startup or restarts without requiring a preload or a warm-up the memory tier.</p>
</div>
</div>
<div class="compute2item hub2item">
@@ -529,7 +529,7 @@
</article>
<div class="h4 hub5__title">BNP Paribas</div>
<p class="hub5__text base5__text">
- with the help of Apache Ignite managed to design, build, and optimize a hybrid transactional-analytical processing (HTAP) solution. This enabled the bank to make key business decisions in real-time.
+ with the help of Apache Ignite managed to design, build, and optimize a hybrid transactional-analytical processing (HTAP) solution. This enabled the bank to make key business decisions in real time.
</p>
</div>
<div class="hub5__item">
@@ -542,7 +542,7 @@
<div class="comvideo__descr pt-1"></div>
</article>
<div class="h4 hub5__title">JP MorganChase</div>
- <p class="hub5__text base5__text">faced an increasing need to apply transformations to large datasets in real-time. To meet this need, their team selected Ignite to achieve persistence, caching and integrated compute.</p>
+ <p class="hub5__text base5__text">faced an increasing need to apply transformations to large datasets in real time. To meet this need, their team selected Ignite to achieve persistence, caching and integrated compute.</p>
</div>
</div>
</div>
@@ -623,6 +623,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/use-cases/key-value-store.html b/use-cases/key-value-store.html
index 337e6d5..c8582a4 100644
--- a/use-cases/key-value-store.html
+++ b/use-cases/key-value-store.html
@@ -11,16 +11,16 @@
<meta property="og:url" content="https://ignite.apache.org/use-cases/key-value-store.html" />
<meta property="og:image" content="/img/og-pic.png" />
<meta property="og:description" content="Apache Ignite is the best and fastest key-value database that stores data both in memory and on disk with support for key-value, SQL, ACID transactions, compute, and machine learning APIs." />
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/native-persistence.css?ver=0.7" />
- <link rel="stylesheet" href="../css/compute-apis.css?ver=0.7" />
- <link rel="stylesheet" href="../css/digital-hub.css?ver=0.7" />
- <link rel="stylesheet" href="../css/datagrid.css?ver=0.7" />
- <link rel="stylesheet" href="../css/hadoop.css?ver=0.7" />
- <link rel="stylesheet" href="../css/key-value-store.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/native-persistence.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/compute-apis.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/digital-hub.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/datagrid.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/hadoop.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/key-value-store.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -402,7 +402,7 @@
<div class="compute2-points__item fz20"></div>
<div class="compute2item__block">
<h3 class="fz20 compute2item__title">Horizontal scalability</h3>
- <p class="compute2__text base2__text">Key-value stores can keep and process large volumes of data by scaling horizontally</p>
+ <p class="compute2__text base2__text">Key-value stores can keep and process large volumes of data by scaling horizontally</p>
</div>
</div>
</div>
@@ -416,7 +416,7 @@
<h2 class="grid4__h2 h5 key4__h2">With Apache Ignite, a key-value store can cache data in memory and persist it on disk</h2>
<div class="grid4__block">
<p class="grid4__text">The <a href="/arch/native-persistence.html">native persistence</a> feature eliminates the time-consuming cache warm-up step as well as the data reloading phase from external databases.</p>
- <p class="grid4__text pt-1">Since the native persistence always keeps a full copy of data on disk, you are free to cache a subset of records in memory.</p>
+ <p class="grid4__text pt-1">Since native persistence always keeps a full copy of data on disk, you are free to cache a subset of records in memory.</p>
<p class="grid4__text pt-1">If a required data record is missing in memory, then Ignite reads it from disk automatically, regardless of the API you use.</p>
</div>
</div>
@@ -437,7 +437,7 @@
</article>
<article class="native2item grid5__item">
<h3 class="key5__h3">Back-end systems acceleration</h3>
- <p class="grid5__text key5__text">Developers use key-value stores to cache specific records that don’t require a regular update. This reduces load on core back-end systems and databases.</p>
+ <p class="grid5__text key5__text">Developers use key-value stores to cache specific records that don’t require a regular update. This reduces the load on core back-end systems and databases.</p>
</article>
</div>
</div>
@@ -518,6 +518,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/use-cases/provenusecases.html b/use-cases/provenusecases.html
index ee3820d..ea7007a 100644
--- a/use-cases/provenusecases.html
+++ b/use-cases/provenusecases.html
@@ -11,11 +11,11 @@
<meta property="og:url" content="https://ignite.apache.org/use-cases/provenusecases.html" />
<meta property="og:image" content="/img/og-pic.png" />
<meta property="og:description" content="All publicly disclosed business cases of Apache Ignite. Explore dozens of Ignite case-studies across various industries." />
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/usecases.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/usecases.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -784,6 +784,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
diff --git a/use-cases/spark-acceleration.html b/use-cases/spark-acceleration.html
index a08fcd6..34f98f2 100644
--- a/use-cases/spark-acceleration.html
+++ b/use-cases/spark-acceleration.html
@@ -11,14 +11,14 @@
<meta property="og:url" content="https://ignite.apache.org/use-cases/spark-acceleration.html" />
<meta property="og:image" content="/img/og-pic.png" />
<meta property="og:description" content="Ignite integrates with Apache Spark to accelerate the performance of Spark applications and APIs by keeping data in a shared in-memory cluster." />
- <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.7" />
- <link rel="stylesheet" href="/css/utils.css?ver=0.7" />
- <link rel="stylesheet" href="/css/site.css?ver=0.7" />
- <link rel="stylesheet" href="../css/native-persistence.css?ver=0.7" />
- <link rel="stylesheet" href="../css/compute-apis.css?ver=0.7" />
- <link rel="stylesheet" href="../css/digital-hub.css?ver=0.7" />
- <link rel="stylesheet" href="../css/spark.css?ver=0.7" />
- <link rel="stylesheet" href="/css/media.css?ver=0.7" media="only screen and (max-width:1199px)" />
+ <link rel="stylesheet" href="/js/vendor/hystmodal/hystmodal.min.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/utils.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/site.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/native-persistence.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/compute-apis.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/digital-hub.css?ver=0.8" />
+ <link rel="stylesheet" href="../css/spark.css?ver=0.8" />
+ <link rel="stylesheet" href="/css/media.css?ver=0.8" media="only screen and (max-width:1199px)" />
<link rel="icon" type="image/png" href="/img/favicon.png" />
</head>
<body>
@@ -379,15 +379,15 @@
<div class="spark1__block">
<div class="spark1__item">
<h3 class="spark1__h3 fz20">Horizontally scalable and shared in-memory layer</h3>
- <p class="spark1__text">Ignite is designed to store data sets in memory across a cluster of nodes reducing latency of Spark operations that usually need to pull date from disk-based systems.</p>
+ <p class="spark1__text">Ignite is designed to store data sets in memory across a cluster of nodes, reducing latency of Spark operations that usually need to pull date from disk-based systems.</p>
</div>
<div class="spark1__item">
<h3 class="spark1__h3 fz20">Minimal data shuffling over the network</h3>
- <p class="spark1__text">Ignite tries to minimize data shuffling over the network between its store and Spark applications by running certain Spark tasks, produced by RDDs or DataFrames APIs, in-place on Ignite nodes.</p>
+ <p class="spark1__text">Ignite tries to minimize data shuffling over the network between its store and Spark applications by running certain Spark tasks, produced by RDDs or DataFrames APIs in-place on Ignite nodes.</p>
</div>
<div class="spark1__item">
<h3 class="spark1__h3 fz20">Extra performance boost with native Ignite APIs</h3>
- <p class="spark1__text">Use native Ignite APIs, such as SQL from Spark applications directly and eliminate data shuffling completely between Spark and Ignite.</p>
+ <p class="spark1__text">Use native Ignite APIs such as SQL from Spark applications directly and eliminate data shuffling completely between Spark and Ignite.</p>
</div>
</div>
<img class="spark1__image" src="/img/usecases/spark/image.svg" alt="image" />
@@ -416,8 +416,8 @@
<div class="spark2__item">
<p class="spark2__text">The Apache Spark DataFrame API introduced the concept of a schema to describe the data, allowing Spark to manage the schema and organize the data into a tabular format.</p>
<p class="spark2__text pt-2">
- To put it simply, a DataFrame is a distributed collection of data organized into named columns. It is conceptually equivalent to a table in a relational database and allows Spark to leverage the Catalyst query optimizer to
- produce much more efficient query execution plans in comparison to RDDs, which are collections of elements partitioned across the nodes of the cluster.
+ To put it simply, a DataFrame is a distributed collection of data organized into named columns. Conceptually, it is the equivalent of a table in a relational database. It allows Spark to leverage the Catalyst query optimizer
+ to produce much more efficient query execution plans in comparison to RDDs, which are collections of elements partitioned across the nodes of the cluster.
</p>
</div>
<div class="spark2__item">
@@ -501,6 +501,6 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
- <script src="/js/main.js?ver=0.7"></script>
+ <script src="/js/main.js?ver=0.8"></script>
</body>
</html>
