You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ignite.apache.org by sk...@apache.org on 2025/12/17 16:32:27 UTC
(ignite-website) branch master updated: IGNITE-27383 Fixed the blogs index pages (#300)
This is an automated email from the ASF dual-hosted git repository.
sk0x50 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ignite-website.git
The following commit(s) were added to refs/heads/master by this push:
new 29a3c7b8b7 IGNITE-27383 Fixed the blogs index pages (#300)
29a3c7b8b7 is described below
commit 29a3c7b8b77bcd1fb3e112b6ad73bd2fa6ef3264
Author: Alexey Alexandrov <fi...@gmail.com>
AuthorDate: Wed Dec 17 18:32:22 2025 +0200
IGNITE-27383 Fixed the blogs index pages (#300)
---
blog/.NET/index.html | 1 +
blog/1/index.html | 286 ++++++++++---------
blog/2/index.html | 255 ++++++++++++-----
blog/{apache/1 => 3}/index.html | 37 ++-
blog/CET/index.html | 1 +
blog/Intel/index.html | 1 +
blog/SQL/index.html | 92 +------
blog/apache-ignite-1-9-released.html | 1 +
blog/apache-ignite-2-0-redesigned.html | 1 +
blog/apache-ignite-2-1-a.html | 1 +
blog/apache-ignite-2-10-thin.html | 1 +
blog/apache-ignite-2-11-1.html | 1 +
blog/apache-ignite-2-11-stabilization.html | 1 +
blog/apache-ignite-2-12-0.html | 1 +
blog/apache-ignite-2-13-0.html | 1 +
blog/apache-ignite-2-16-0.html | 1 +
blog/apache-ignite-2-17-0.html | 1 +
blog/apache-ignite-2-3-more.html | 1 +
blog/apache-ignite-2-4-brings.html | 1 +
blog/apache-ignite-2-5-scaling.html | 1 +
blog/apache-ignite-2-7-deep.html | 1 +
blog/apache-ignite-2-9-released.html | 1 +
blog/apache-ignite-3-architecture-part-2.html | 3 +-
blog/apache-ignite-community-news-september.html | 1 +
blog/apache-ignite-community-update-august.html | 1 +
blog/apache-ignite-essentials-series-for.html | 1 +
blog/apache-ignite-momentum-highlights-from.html | 1 +
blog/apache-ignite-net-dynamic-linq.html | 1 +
blog/apache-ignite-net-intel-cet-fix.html | 1 +
blog/apache/1/index.html | 224 +++++++++++++--
blog/{biodata => apache/2}/index.html | 36 +--
blog/apache/index.html | 24 +-
blog/bigdata/index.html | 1 +
blog/biodata/index.html | 1 +
blog/computing/index.html | 1 +
blog/csharp/index.html | 1 +
blog/data/index.html | 1 +
blog/database/1/index.html | 1 +
blog/database/index.html | 1 +
blog/fast/index.html | 1 +
blog/getting-to-know-apache-ignite-3.html | 3 +-
blog/grid/index.html | 1 +
blog/ignite-2-8-released-less.html | 1 +
blog/ignite/1/index.html | 303 ++++++++++-----------
blog/ignite/2/index.html | 203 ++++++++++++++
blog/ignite/index.html | 13 -
blog/imdb/index.html | 1 +
blog/in-memory/index.html | 1 +
blog/in/index.html | 1 +
blog/index.html | 35 +--
blog/key-value/index.html | 1 +
blog/learning/index.html | 1 +
blog/linq/index.html | 1 +
blog/log4j2/index.html | 1 +
blog/machine/index.html | 1 +
blog/meetup/index.html | 1 +
blog/meltdown-and-spectre-patches-show.html | 1 +
blog/meltdown/index.html | 1 +
blog/memory/index.html | 1 +
blog/nodal/index.html | 1 +
blog/open-source/index.html | 1 +
blog/open/index.html | 1 +
blog/performance/index.html | 1 +
blog/presenting-apache-ignite-sql-grid.html | 1 +
blog/protecting-apache-ignite-from-meltdown.html | 1 +
blog/rdbms/index.html | 1 +
blog/release/index.html | 3 +-
.../schema-design-for-distributed-systems-ai3.html | 3 +-
blog/security/index.html | 1 +
blog/source/index.html | 1 +
blog/spark/index.html | 1 +
blog/spectre/index.html | 1 +
blog/sql/index.html | 1 +
blog/store/index.html | 1 +
blog/two/index.html | 1 +
blog/whats-new-in-apache-ignite-3-0.html | 1 +
blog/whats-new-in-apache-ignite-3-1.html | 1 +
77 files changed, 1024 insertions(+), 558 deletions(-)
diff --git a/blog/.NET/index.html b/blog/.NET/index.html
index 5492499ead..eae73e4e5c 100644
--- a/blog/.NET/index.html
+++ b/blog/.NET/index.html
@@ -472,6 +472,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/1/index.html b/blog/1/index.html
index 1c18a92bf1..ede22e1909 100644
--- a/blog/1/index.html
+++ b/blog/1/index.html
@@ -343,253 +343,249 @@
<section class="blog__posts">
<article class="post">
<div class="post__header">
- <h2><a href="/blog/apache-ignite-2-10-thin.html">Apache Ignite 2.10: Thin Client Expansion</a></h2>
+ <h2><a href="/blog/apache-ignite-net-intel-cet-fix.html">Ignite on .NET 9 and Intel CET</a></h2>
<div>
- March 18, 2021 by Maxim Muzafarov. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-10-thin.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite 2.10: Thin Client Expansion%20https://ignite.apache.org/blog/apache-ignite-2-10-thin.html">Twitter</a>
+ November 22, 2024 by Pavel Tupitsyn. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-net-intel-cet-fix.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Ignite on .NET 9 and Intel CET%20https://ignite.apache.org/blog/apache-ignite-net-intel-cet-fix.html">Twitter</a>
</div>
</div>
<div class="post__content">
- <p class="entryContent">
- As of March 15, 2021, <a href="https://ignite.apache.org/">Apache Ignite</a> 2.10 has been released. You can directly check the full list of resolved <a href="https://s.apache.org/i3ny6">Important JIRA's</a> but here
- let’s briefly overview some valuable improvements.
- </p>
- <h3 id="thin-clients">Thin Clients</h3>
- Thin clients now support several important features which, previously were available only on the thick clients. Thin clients are always backward and forward compatible with the server nodes of the cluster, so the cluster
- upgrade process will be more convenient if the lack of these features prevented you from doing that.
- <p>See the list of what is changed for thin clients below:</p>
- <ul>
- <li>Transactions</li>
- <li>Service invocations</li>
- <li>Continuous Queries</li>
- <li>SQL API</li>
- <li>Cluster API</li>
- <li>Cache Async API</li>
- <li>Kubernetes Discovery (<em>ThinClientKubernetesAddressFinder</em>)</li>
- </ul>
- You may check the <a href="https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features">List of Thin Client Features</a> that supported by platforms you are interested in or see the
- <a href="https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-2.10/">What's new in Apache Ignite.NET 2.10</a>.
+ <p>Old JDK code meets new Intel security feature, JVM + CLR in one process, and a mysterious crash.</p>
+ <p><a href="https://ptupitsyn.github.io/Ignite-on-NET-9/">Read More...</a></p>
</div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-10-thin.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/apache-ignite-2-9-released.html">Apache Ignite 2.9 Released: Cluster snapshots and tracing</a></h2>
+ <h2><a href="/blog/apache-ignite-2-16-0.html">Apache Ignite 2.16.0: Cache dumps, Calcite engine stabilization, JDK 14+ bug fixes</a></h2>
<div>
- November 5, 2020 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-9-released.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite 2.9 Released: Cluster snapshots and tracing%20https://ignite.apache.org/blog/apache-ignite-2-9-released.html">Twitter</a>
+ December 25, 2023 by Nikita Amelchev. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-16-0.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.16.0: Cache dumps, Calcite engine stabilization, JDK 14+ bug fixes%20https://ignite.apache.org/blog/apache-ignite-2-16-0.html">Twitter</a>
</div>
</div>
<div class="post__content">
- <p>As of October 23, 2020, Apache Ignite 2.9 is available. Like every other Ignite release, release 2.9 includes many changes. Let's take a look at the major features of release 2.9.</p>
- <p></p>
- <h3>Cluster Snapshots</h3>
- <p></p>
<p>
- Ignite 2.9 provides the ability to create full cluster snapshots for deployments that use Ignite Persistence. Snapshots can be taken online, when the cluster is active and accessible to users. An Ignite snapshot includes a
- cluster-wide copy of all data records that exist at the moment the snapshot is started. All snapshots are consistent — in terms of concurrent, cluster-wide operations as well as in terms of ongoing changes in Ignite
- Persistence data, index, schema, binary metadata, marshaller, and other files on nodes. See <a href="https://ignite.apache.org/docs/latest/persistence/snapshots">Ignite documentation</a> to learn about this feature.
+ As of December 25, 2023, <a href="https://ignite.apache.org/">Apache Ignite </a>2.16 has been released. You can directly check the full list of resolved <a href="https://s.apache.org/j3brc">Important JIRA tasks </a>but
+ let's briefly overview some valuable improvements.
+ </p>
+ <h3 id="cache-dumps">Cache dumps</h3>
+ <p>
+ Ignite has persistent cache <a href="https://ignite.apache.org/docs/latest/snapshots/snapshots">snapshots </a>and this feature is highly appreciated by Ignite users. This release introduces another way to make a copy of
+ user data - a cache dump.
+ </p>
+ <p>
+ The cache dump is essentially a file that contains all entries of a cache group at the time of dump creation. Dump is consistent like a snapshot, which means all entries that existed in the cluster at the moment of dump
+ creation will be included in the dump file. Meta information of dumped caches and binary meta are also included in the dump.
</p>
+ <p>Main differences from cache snapshots:</p>
+ <ul>
+ <li>Supports in-memory caches that a snapshot feature does not support.</li>
+ <li>Takes up less disk space. The dump contains only the cache entries as-is.</li>
+ <li>Can be used for offline data processing.</li>
+ </ul>
</div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-9-released.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-16-0.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/ignite-2-8-released-less.html">Ignite 2.8 Released: Less Stress in Production and Advances in Machine Learning</a></h2>
+ <h2><a href="/blog/apache-ignite-net-dynamic-linq.html">Dynamic LINQ performance and usability with Ignite.NET and System.Linq.Dynamic</a></h2>
<div>
- March 11, 2020 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/ignite-2-8-released-less.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Ignite 2.8 Released: Less Stress in Production and Advances in Machine Learning%20https://ignite.apache.org/blog/ignite-2-8-released-less.html">Twitter</a>
+ May 22, 2023 by Pavel Tupitsyn. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-net-dynamic-linq.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Dynamic LINQ performance and usability with Ignite.NET and System.Linq.Dynamic%20https://ignite.apache.org/blog/apache-ignite-net-dynamic-linq.html">Twitter</a>
</div>
</div>
<div class="post__content">
- <p>
- With thousands of changes contributed to Apache Ignite 2.8 that enhanced almost all the components of the platform, it’s possible to overlook some of the improvements that can convince you to upgrade to this version
- sooner than later. While a quick check of the <a href="https://ignite.apache.org/releases/ignite2/2.8.0/release_notes.html" target="_blank">release notes</a> will help to discover anticipated bug fixes, this article aims
- to guide through enhancements every Ignite developer should be aware of.
- </p>
- <h3>New Subsystem for Production Monitoring and Tracing</h3>
- <p>
- Several months of constant work on <a href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=112820392" target="_blank">IEP-35: Monitoring & Profiling</a> has resulted in the creation of a robust and
- elastic subsystem for production monitoring and diagnostic (aka. profiling). This was influenced by the needs of many developers who deployed Ignite in critical environments and were asking for a foundation that can be
- integrated with many external monitoring tools and be expanded easily.
- </p>
- <p>
- The <a href="https://apacheignite.readme.io/docs/new-metrics#section-exporters" target="_blank">new subsystem</a> consists of several registries that group individual metrics related to a specific Ignite component. For
- instance, you will find registries for cache, compute, or service grid APIs. Since the registries are designed to be generic, specific exporters can observe the state of Ignite via a myriad of tools supporting various
- protocols. By default, Ignite 2.8 introduces exporters for monitoring interfaces such as log files, JMX and SQL views, and contemporary ones such as OpenCensus.
- </p>
+ <p>Dynamically building database queries can be necessary for some use cases, such as UI-defined filtering. This can get challenging with LINQ frameworks like EF Core and Ignite.NET.</p>
+ <p><a href="https://ptupitsyn.github.io/Dynamic-LINQ-With-Ignite/">Read More...</a></p>
</div>
- <div class="post__footer"><a class="more" href="/blog/ignite-2-8-released-less.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/apache-ignite-2-7-deep.html">Apache Ignite 2.7: Deep Learning and Extended Languages Support</a></h2>
+ <h2><a href="/blog/apache-ignite-2-13-0.html">Apache Ignite 2.13.0: new Apache Calcite-based SQL engine</a></h2>
<div>
- December 13, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-7-deep.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite 2.7: Deep Learning and Extended Languages Support%20https://ignite.apache.org/blog/apache-ignite-2-7-deep.html">Twitter</a>
+ April 28, 2022 by Nikita Amelchev. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-13-0.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.13.0: new Apache Calcite-based SQL engine%20https://ignite.apache.org/blog/apache-ignite-2-13-0.html">Twitter</a>
</div>
</div>
<div class="post__content">
- <h3>Deep Learning With TensorFlow</h3>
- <p></p>
- <p>
- Even though it was natural to provide machine learning algorithms in Ignite out of the box, another direction was taken for deep learning capabilities. Primarily because machine learning approaches have already been
- adopted in businesses from big to small -- while deep learning is still being used for narrow and specific use cases.
- </p>
<p>
- Thus, Ignite 2.7 can boast about an <a href="https://ignite.apache.org/features/tensorflow.html" target="_blank">official integration</a> with TensorFlow deep learning framework that gives a way to use Ignite as a
- distributed storage for TensorFlow calculations. With Ignite, data scientists can store unlimited data sets across a cluster, gain performance improvements and rely on fault-tolerance of both products if an algorithm fails
- in the middle of an execution.
+ As of April 26, 2022, <a href="https://ignite.apache.org/">Apache Ignite</a> 2.13 has been released. You can directly check the full list of resolved <a href="https://s.apache.org/x8u49">Important JIRA tasks</a> but here
+ let's briefly overview some valuable improvements.
</p>
+ <h4>This is a breaking change release: The legacy service grid implementation was removed.</h4>
+ <h3 id="new-apache-calcite-based-sql-engine">New Apache Calcite-based SQL engine</h3>
+ <p>We've implemented a new experimental SQL engine based on Apache Calcite. Now it's possible to:</p>
+ <ul>
+ <li>Get rid of some <a href="https://cwiki.apache.org/confluence/display/IGNITE/IEP-37%3A+New+query+execution+engine#IEP37:Newqueryexecutionengine-Motivation">H2 limitations</a>;</li>
+ <li><a href="https://cwiki.apache.org/confluence/display/IGNITE/IEP-37%3A+New+query+execution+engine#IEP37:Newqueryexecutionengine-Implementationdetails">Optimize</a> some query execution.</li>
+ </ul>
+ <p>The current H2-based engine has fundamental limitations. For example:</p>
+ <ul>
+ <li>some queries should be splitted into 2 phases (map subquery and reduce subquery), but some of them cannot be effectively executed in 2 phases.</li>
+ <li>H2 is a third-party database product with not-ASF license.</li>
+ <li>The optimizer and other internal things are not supposed to work in a distributed environment.</li>
+ <li>It's hard to make Ignite-specific changes to the H2 code, patches are often declined.</li>
+ </ul>
</div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-7-deep.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-13-0.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/apache-ignite-2-5-scaling.html">Apache Ignite 2.5: Scaling to 1000s Nodes Clusters</a></h2>
+ <h2><a href="/blog/apache-ignite-2-12-0.html">Apache Ignite 2.12.0: CDC, Index Query API, Vulnerabilities Fixes</a></h2>
<div>
- May 31, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-5-scaling.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite 2.5: Scaling to 1000s Nodes Clusters%20https://ignite.apache.org/blog/apache-ignite-2-5-scaling.html">Twitter</a>
+ January 14, 2022 by Nikita Amelchev. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-12-0.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.12.0: CDC, Index Query API, Vulnerabilities Fixes%20https://ignite.apache.org/blog/apache-ignite-2-12-0.html">Twitter</a>
</div>
</div>
<div class="post__content">
<p>
- Apache Ignite was always appreciated by its users for two primary things it delivers - scalability and performance. Throughout the lifetime many distributed systems tend to do performance optimizations from a release to
- release while making scalability related improvements just a couple of times. It's not because the scalability is of no interest. Usually, scalability requirements are set and solved once by a distributed system and
- don't require significant additional interventions by engineers.
+ As of January 14, 2022, <a href="https://ignite.apache.org/">Apache Ignite</a> 2.12 has been released. You can directly check the full list of resolved <a href="https://s.apache.org/0zyi2">Important JIRA tasks</a> but here
+ let’s briefly overview some valuable improvements.
</p>
+ <h3 id="vulnerability-updates">Vulnerability Updates</h3>
<p>
- However, Apache Ignite grew to the point when the community decided to revisit its discovery subsystem that influences how well and far Ignite scales out. The goal was pretty clear - Ignite has to scale to 1000s of nodes
- as good as it scales to 100s now.
+ The Apache Ignite versions lower than 2.11.1 are vulnerable to <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44832">CVE-2021-44832</a> which is related to the <code>ignite-log4j2</code> module usage.
</p>
+ <p>The release also fixes 10+ CVE’s of various modules. See <a href="https://ignite.apache.org/releases/ignite2/2.12.0/release_notes.html">release notes</a> for more details.</p>
+ <h3 id="change-data-capture">Change Data Capture</h3>
<p>
- It took many months to get the task implemented. So, please join me in welcoming Apache Ignite 2.5 that now can be scaled easily to 1000s of nodes and goes with other exciting capabilities. Let's check out the most
- prominent ones.
+ Change Data Capture (<a href="https://en.wikipedia.org/wiki/Change_data_capture">CDC</a>) is a data processing pattern used to asynchronously receive entries that have been changed on the local node so that action can be
+ taken using the changed entry.
</p>
</div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-5-scaling.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-12-0.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/apache-ignite-2-4-brings.html">Apache Ignite 2.4 ings Advanced Machine Learning and Spark DataFrames Capabilities</a></h2>
+ <h2><a href="/blog/apache-ignite-2-11-1.html">Apache Ignite 2.11.1: Emergency Log4j2 Update</a></h2>
<div>
- March 15, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-4-brings.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite 2.4 ings Advanced Machine Learning and Spark DataFrames Capabilities%20https://ignite.apache.org/blog/apache-ignite-2-4-brings.html">Twitter</a>
+ December 21, 2021 by Maxim Muzafarov. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-11-1.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.11.1: Emergency Log4j2 Update%20https://ignite.apache.org/blog/apache-ignite-2-11-1.html">Twitter</a>
</div>
</div>
<div class="post__content">
<p>
- Usually, Ignite community rolls out a new version once in 3 months, but we had to make an exception for Apache Ignite 2.4 that consumed five months in total. We could easily blame Thanksgiving, Christmas and New Year
- holidays for the delay and would be forgiven, but, in fact, we were forging the release you can't simply pass by.
- </p>
- <p>Let's dive in and search for a big fish.</p>
- <h3>Machine Learning General Availability</h3>
- <p>
- Eight months ago, at the time of Apache Ignite 2.0, we put out the first APIs that formed the foundation of the Ignite's machine learning component of today. Since that time, Ignite machine learning experts and
- enthusiasts have been moving the liary to the general availability condition meticulously. And Ignite 2.4 became a milestone that let us consider the
- <a href="https://apacheignite.readme.io/docs/machine-learning" target="_blank">ML Grid</a> to be production ready.
+ The new <a href="https://ignite.apache.org/">Apache Ignite</a> 2.11.1 is an emergency release that fixes <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228">CVE-2021-44228</a>,
+ <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046">CVE-2021-45046</a>,<a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45105">CVE-2021-45105</a> related to the ignite-log4j2 module
+ usage.
</p>
+ <h3 id="apache-ignite-with-log4j-vulnerability">Apache Ignite with Log4j Vulnerability</h3>
+ <p>All the following conditions must be met:</p>
+ <ul>
+ <li>The Apache Ignite version lower than 2.11.0 is used (since these vulnerabilities are already fixed in 2.11.1, 2.12, and upper versions);</li>
+ <li>The <code>ignite-logj42</code> is used by Apache Ignite and located in the <code>libs</code> directory (by default it is located in the <code>libs/optional</code>directory, so these deployments are not affected);</li>
+ <li>
+ The Java version in use is older than the following versions: <code>8u191</code>, <code>11.0.1</code>. This is due to the fact that later versions set the JVM property
+ <code>com.sun.jndi.ldap.object.trustURLCodebase</code> to <code>false</code> by default, which disables JNDI loading of classes from arbitrary URL code bases.
+ </li>
+ </ul>
+ <p>NOTE: Relying only on the Java version as a protection against these vulnerabilities is very risky and has not been tested.</p>
</div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-4-brings.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-11-1.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/meltdown-and-spectre-patches-show.html">Meltdown and Spectre patches show negligible impact to Apache Ignite performance</a></h2>
+ <h2><a href="/blog/apache-ignite-2-11-stabilization.html">Apache Ignite 2.11: Stabilization First</a></h2>
<div>
- January 30, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/meltdown-and-spectre-patches-show.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Meltdown and Spectre patches show negligible impact to Apache Ignite performance%20https://ignite.apache.org/blog/meltdown-and-spectre-patches-show.html">Twitter</a>
+ September 20, 2021 by Maxim Muzafarov. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-11-stabilization.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.11: Stabilization First%20https://ignite.apache.org/blog/apache-ignite-2-11-stabilization.html">Twitter</a>
</div>
</div>
<div class="post__content">
<p>
- As promised in my <a href="https://blogs.apache.org/ignite/entry/protecting-apache-ignite-from-meltdown">initial blog post</a> on this matter, Apache Ignite community applied security patches against the
- notorious Meltdown Spectre vulnerabilities and completed performance testing of general operations and workloads that are typical for Ignite deployments.
+ The new <a href="https://ignite.apache.org/">Apache Ignite</a> 2.11 was released on September 17, 2021. It can be considered to be a greater extent as a stabilization release that closed a number of technical debts of the
+ internal architecture and bugs. Out of more than 200 completed tasks, 120 are bug fixes. However, some valuable improvements still exist, so let's take a quick look at them together.
+ </p>
+ <h3 id="thin-clients">Thin Clients</h3>
+ <p>
+ Partition awareness is enabled by default in the 2.11 release and allows thin clients to send query requests directly to the node that owns the queried data. Without partition awareness, an application executes all queries
+ and operations via a single server node that acts as a proxy for the incoming requests.
</p>
<p>
- The security patches were applied only for <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5754" target="_blank">CVE-2017-5754</a> (Meltdown) and <a
- href="https://nvd.nist.gov/vuln/detail/CVE-2017-5753"
- target="_blank"
- >CVE-2017-5753</a
- > (Spectre Variant 1) vulnerabilities. The patches for <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5715" target="_blank">CVE-2017-5715</a> (Spectre Variant 2) for the hardware the community used for
- testing are not stable yet an can
- <a href="https://newsroom.intel.com/news/root-cause-of-reboot-issue-identified-updated-guidance-for-customers-and-partners/" target="_blank">cause system reboot issues or another unpredictable behavior</a>.
+ The support of <a href="https://ignite.apache.org/docs/latest/thin-clients/java-thin-client#cache-entry-listening">Continuous Queries</a>added to the java thin client. For the other supported features, you can check - the
+ <a href="https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features">List of Thin Client Features</a>.
</p>
- <p>The applied patches have shown that the performance implications are negligible - the performance drop is just in the 0 - 7% range as the figure shows:</p>
</div>
- <div class="post__footer"><a class="more" href="/blog/meltdown-and-spectre-patches-show.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-11-stabilization.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/protecting-apache-ignite-from-meltdown.html">Protecting Apache Ignite from 'Meltdown' and 'Spectre' vulnerabilities</a></h2>
+ <h2><a href="/blog/apache-ignite-momentum-highlights-from.html">Apache Ignite Momentum: Highlights from 2020-2021</a></h2>
<div>
- January 8, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/protecting-apache-ignite-from-meltdown.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Protecting Apache Ignite from 'Meltdown' and 'Spectre' vulnerabilities%20https://ignite.apache.org/blog/protecting-apache-ignite-from-meltdown.html">Twitter</a>
+ September 14, 2021 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-momentum-highlights-from.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite Momentum: Highlights from 2020-2021%20https://ignite.apache.org/blog/apache-ignite-momentum-highlights-from.html">Twitter</a>
</div>
</div>
<div class="post__content">
<p>
- The world was rocked after the recent disclosure of the
- <a href="https://www.vox.com/business-and-finance/2018/1/4/16850004/meltdown-spectre-intel-security-flaw-update" target="_blank">Meltdown and Spectre</a> vulnerabilities that literally affect almost all software ever
- developed. Both issues are related to the way all modern CPUs are designed and this is why they have opened unprecedented security breaches -- making the software, including Apache Ignite, vulnerable to
- hacker attacks.
+ When Apache Ignite entered the Apache Software Foundation (ASF) Incubator in 2014, it took less than a year for the project and its community to graduate from the Incubator and become a top-level project for the ASF. Since
+ then, Ignite has experienced a significant and steady growth in popularity, and it has been used by thousands of application developers and architects to create high-performance and scalable applications used by millions
+ of people daily. In this article, we’ll recap the achievements of Ignite in 2020-2021.
+ </p>
+ <p></p>
+ <h3><br />Ignite is Ranked as a Top 5 Project<br /></h3>
+ <p></p>
+ <p>
+ The ASF has ranked Apache ignite as a Top 5 project in various categories since 2017. <a href="https://blogs.apache.org/foundation/entry/apache-in-2017-by-the" target="_blank">That year</a>, Ignite was in the Top 5 of
+ Apache Project Repositories by Commits and most active Apache mailing lists. <a href="https://www.apache.org/foundation/docs/FY2021AnnualReport.pdf" target="_blank">Today</a>, the momentum continues, and Ignite continues
+ to be ranked as a Top 5 project in multiple categories: second on the Top 5 big data user lists, third on the Top 5 big data dev lists, second on the Top 5 of all user lists, third on the Top 5 repos by size.
+ </p>
+ <p>
+ <a href="/img/blog/463ae37d-866d-4c15-8ebf-6b88499daa81.jpeg"><img src="/img/blog/463ae37d-866d-4c15-8ebf-6b88499daa81.jpeg" width="30%" /></a>
</p>
- <p>The vulnerabilities are registered in the National Vulnerability Database under the following CVEs:</p>
- <ul>
- <li><a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5753" target="_blank">CVE-2017-5753</a> — Spectre variant 1</li>
- <li><a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5715" target="_blank">CVE-2017-5715</a> — Spectre variant 2</li>
- <li><a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5754" target="_blank">CVE-2017-5754</a> — Meltdown</li>
- </ul>
</div>
- <div class="post__footer"><a class="more" href="/blog/protecting-apache-ignite-from-meltdown.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-momentum-highlights-from.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/apache-ignite-essentials-series-for.html">Apache Ignite Essentials: 2-part Webinar Series for Architects and Java Developers</a></h2>
+ <h2><a href="/blog/apache-ignite-2-10-thin.html">Apache Ignite 2.10: Thin Client Expansion</a></h2>
<div>
- November 17, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-essentials-series-for.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite Essentials: 2-part Webinar Series for Architects and Java Developers%20https://ignite.apache.org/blog/apache-ignite-essentials-series-for.html">Twitter</a>
+ March 18, 2021 by Maxim Muzafarov. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-10-thin.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.10: Thin Client Expansion%20https://ignite.apache.org/blog/apache-ignite-2-10-thin.html">Twitter</a>
</div>
</div>
<div class="post__content">
<p class="entryContent">
- We finally made this happen! I’m happy to invite all of the software architects and engineers out there to a series of webinars that will introduce you to the fundamental capabilities of in-memory computing platforms
- such as Apache Ignite.
+ As of March 15, 2021, <a href="https://ignite.apache.org/">Apache Ignite</a> 2.10 has been released. You can directly check the full list of resolved <a href="https://s.apache.org/i3ny6">Important JIRA's</a> but here
+ let’s briefly overview some valuable improvements.
</p>
- <p>There will also be a mix of theory and practice. A lot of code examples are waiting to be shown so that you can apply the theory in practice right away.</p>
- <p>The series consists of two parts.</p>
- <h3><a href="https://ignite.apache.org/events.html#in-memory-computing-essentials-architects-and-developers-part-1" target="_blank">Part 1: Tuesday, November 21, 2017, 11:00am PT / 2:00pm ET</a></h3>
- To be covered:
+ <h3 id="thin-clients">Thin Clients</h3>
+ Thin clients now support several important features which, previously were available only on the thick clients. Thin clients are always backward and forward compatible with the server nodes of the cluster, so the cluster
+ upgrade process will be more convenient if the lack of these features prevented you from doing that.
+ <p>See the list of what is changed for thin clients below:</p>
<ul>
- <li>Cluster configuration and deployment.</li>
- <li>Distributed database internals (partitioning, replication).</li>
- <li>Data processing with key-value APIs.</li>
- <li>Affinity Collocation.</li>
- <li>Data processing with SQL.</li>
+ <li>Transactions</li>
+ <li>Service invocations</li>
+ <li>Continuous Queries</li>
+ <li>SQL API</li>
+ <li>Cluster API</li>
+ <li>Cache Async API</li>
+ <li>Kubernetes Discovery (<em>ThinClientKubernetesAddressFinder</em>)</li>
</ul>
+ You may check the <a href="https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features">List of Thin Client Features</a> that supported by platforms you are interested in or see the
+ <a href="https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-2.10/">What's new in Apache Ignite.NET 2.10</a>.
</div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-essentials-series-for.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-10-thin.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/apache-ignite-2-3-more.html">Apache Ignite 2.3 - More SQL and Persistence Capabilities</a></h2>
+ <h2><a href="/blog/apache-ignite-2-9-released.html">Apache Ignite 2.9 Released: Cluster snapshots and tracing</a></h2>
<div>
- November 1, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-3-more.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite 2.3 - More SQL and Persistence Capabilities%20https://ignite.apache.org/blog/apache-ignite-2-3-more.html">Twitter</a>
+ November 5, 2020 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-9-released.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.9 Released: Cluster snapshots and tracing%20https://ignite.apache.org/blog/apache-ignite-2-9-released.html">Twitter</a>
</div>
</div>
<div class="post__content">
- <p>Putting aside the regular bug fixes and performance optimizations, the Apache Ignite 2.3 release brings new SQL capabilities and Ignite persistence improvements that are worth mentioning.</p>
+ <p>As of October 23, 2020, Apache Ignite 2.9 is available. Like every other Ignite release, release 2.9 includes many changes. Let's take a look at the major features of release 2.9.</p>
<p></p>
- <h3>SQL</h3>
+ <h3>Cluster Snapshots</h3>
<p></p>
- <p>Let's start with SQL first.</p>
- <p>Apache Ignite users have consistently told us that despite all of Ignite’s SQL capabilities, it’s been at times challenging trying to figure out how to start using Ignite as an SQL database.</p>
<p>
- This was mostly caused by scattered documentation pages, lack of “getting started” guides and tutorials. We’ve remedied this oversight! All related SQL knowledge has been curated in a
- <a href="https://apacheignite-sql.readme.io/docs" target="_blank">single documentation domain</a>.
+ Ignite 2.9 provides the ability to create full cluster snapshots for deployments that use Ignite Persistence. Snapshots can be taken online, when the cluster is active and accessible to users. An Ignite snapshot includes a
+ cluster-wide copy of all data records that exist at the moment the snapshot is started. All snapshots are consistent — in terms of concurrent, cluster-wide operations as well as in terms of ongoing changes in Ignite
+ Persistence data, index, schema, binary metadata, marshaller, and other files on nodes. See <a href="https://ignite.apache.org/docs/latest/persistence/snapshots">Ignite documentation</a> to learn about this feature.
</p>
</div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-3-more.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-9-released.html">↓ Read all</a></div>
</article>
</section>
<section class="blog__footer">
@@ -597,6 +593,7 @@
<li><a class="item" href="/blog/">1</a></li>
<li><a class="current" href="/blog/1/">2</a></li>
<li><a class="item" href="/blog/2/">3</a></li>
+ <li><a class="item" href="/blog/3/">4</a></li>
</ul>
</section>
</main>
@@ -702,6 +699,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/2/index.html b/blog/2/index.html
index 0c55878164..a36d9517bd 100644
--- a/blog/2/index.html
+++ b/blog/2/index.html
@@ -343,141 +343,256 @@
<section class="blog__posts">
<article class="post">
<div class="post__header">
- <h2><a href="/blog/apache-ignite-community-news-september.html">Apache Ignite Community News (Issue 3)</a></h2>
+ <h2><a href="/blog/ignite-2-8-released-less.html">Ignite 2.8 Released: Less Stress in Production and Advances in Machine Learning</a></h2>
<div>
- September 15, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-community-news-september.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite Community News (Issue 3)%20https://ignite.apache.org/blog/apache-ignite-community-news-september.html">Twitter</a>
+ March 11, 2020 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/ignite-2-8-released-less.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Ignite 2.8 Released: Less Stress in Production and Advances in Machine Learning%20https://ignite.apache.org/blog/ignite-2-8-released-less.html">Twitter</a>
</div>
</div>
<div class="post__content">
- <p><b>by Tom Diederich</b></p>
- <p>This is our third community update – there’s a lot going on, so let's get started.</p>
- <p>Apache Ignite experts have already spoken at two meetups this month, both in Silicon Valley, but there are several more scheduled this month around the world.</p>
- <p></p>
- <p style="margin-bottom: 15pt">
- <span style="line-height: 19.5pt"
- ><span style="font-family: Helvetica"
- ><span style="color: #333333"
- >On <b>Sept. 9</b> Apache Ignite PMC chair Denis Magda was the featured presenter at the<b> </b
- ><a href="https://www.meetup.com/datariders/events/242523245/"
- ><b><span style="color: #467d76">Big Data and Cloud Meetup</span></b></a
- >
- in Santa Clara, Calif. His talk, titled "Apache Spark and Apache Ignite: Where Fast Data Meets the IoT," was highly rated and we’re planning a hands-on workshop with meetup organizers for
- November.</span
- ></span
- ></span
- >
+ <p>
+ With thousands of changes contributed to Apache Ignite 2.8 that enhanced almost all the components of the platform, it’s possible to overlook some of the improvements that can convince you to upgrade to this version
+ sooner than later. While a quick check of the <a href="https://ignite.apache.org/releases/ignite2/2.8.0/release_notes.html" target="_blank">release notes</a> will help to discover anticipated bug fixes, this article aims
+ to guide through enhancements every Ignite developer should be aware of.
+ </p>
+ <h3>New Subsystem for Production Monitoring and Tracing</h3>
+ <p>
+ Several months of constant work on <a href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=112820392" target="_blank">IEP-35: Monitoring & Profiling</a> has resulted in the creation of a robust and
+ elastic subsystem for production monitoring and diagnostic (aka. profiling). This was influenced by the needs of many developers who deployed Ignite in critical environments and were asking for a foundation that can be
+ integrated with many external monitoring tools and be expanded easily.
+ </p>
+ <p>
+ The <a href="https://apacheignite.readme.io/docs/new-metrics#section-exporters" target="_blank">new subsystem</a> consists of several registries that group individual metrics related to a specific Ignite component. For
+ instance, you will find registries for cache, compute, or service grid APIs. Since the registries are designed to be generic, specific exporters can observe the state of Ignite via a myriad of tools supporting various
+ protocols. By default, Ignite 2.8 introduces exporters for monitoring interfaces such as log files, JMX and SQL views, and contemporary ones such as OpenCensus.
</p>
</div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-community-news-september.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/ignite-2-8-released-less.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/apache-ignite-community-update-august.html">Apache Ignite Community Update (August 2017 Issue)</a></h2>
+ <h2><a href="/blog/apache-ignite-2-7-deep.html">Apache Ignite 2.7: Deep Learning and Extended Languages Support</a></h2>
<div>
- August 30, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-community-update-august.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite Community Update (August 2017 Issue)%20https://ignite.apache.org/blog/apache-ignite-community-update-august.html">Twitter</a>
+ December 13, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-7-deep.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.7: Deep Learning and Extended Languages Support%20https://ignite.apache.org/blog/apache-ignite-2-7-deep.html">Twitter</a>
</div>
</div>
<div class="post__content">
+ <h3>Deep Learning With TensorFlow</h3>
+ <p></p>
<p>
- <b><i>by Tom Diederich</i></b>
+ Even though it was natural to provide machine learning algorithms in Ignite out of the box, another direction was taken for deep learning capabilities. Primarily because machine learning approaches have already been
+ adopted in businesses from big to small -- while deep learning is still being used for narrow and specific use cases.
</p>
<p>
- Igniters, here are some community highlights from the last couple week. If I missed anything, please share it here. Meetups! Did you know that Apache Ignite experts are available to speak at your meetup? And we also have
- spots open for YOU to speak at the following meetups that some of us co-organize:
+ Thus, Ignite 2.7 can boast about an <a href="https://ignite.apache.org/features/tensorflow.html" target="_blank">official integration</a> with TensorFlow deep learning framework that gives a way to use Ignite as a
+ distributed storage for TensorFlow calculations. With Ignite, data scientists can store unlimited data sets across a cluster, gain performance improvements and rely on fault-tolerance of both products if an algorithm fails
+ in the middle of an execution.
</p>
- <ul>
- <li><a href="https://www.meetup.com/Apache-Ignite-London/" target="_blank">Apache Ignite London</a></li>
- <li><a href="https://www.meetup.com/Bay-Area-In-Memory-Computing/" target="_blank">Bay Area In-Memory Computing Meetup</a></li>
- <li><a href="https://www.meetup.com/NYC-In-Memory-Computing-Meetup/" target="_blank">NYC In-Memory Computing Meetup</a></li>
- <li><a href="https://www.meetup.com/Moscow-Apache-Ignite-Meetup/" target="_blank">Moscow Apache Ignite Meetup</a></li>
- </ul>
</div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-community-update-august.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-7-deep.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/apache-ignite-2-1-a.html">Apache Ignite 2.1 - A Leap from In-Memory to Memory-Centric Architecture</a></h2>
+ <h2><a href="/blog/apache-ignite-2-5-scaling.html">Apache Ignite 2.5: Scaling to 1000s Nodes Clusters</a></h2>
<div>
- July 27, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-1-a.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite 2.1 - A Leap from In-Memory to Memory-Centric Architecture%20https://ignite.apache.org/blog/apache-ignite-2-1-a.html">Twitter</a>
+ May 31, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-5-scaling.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.5: Scaling to 1000s Nodes Clusters%20https://ignite.apache.org/blog/apache-ignite-2-5-scaling.html">Twitter</a>
</div>
</div>
<div class="post__content">
<p>
- The power and beauty of in-memory computing projects are that they truly do what they state -- deliver outstanding performance improvements by moving data closer to the CPU, using RAM as a storage and spreading the data
- sets out across a cluster of machines relying on horizontal scalability.
+ Apache Ignite was always appreciated by its users for two primary things it delivers - scalability and performance. Throughout the lifetime many distributed systems tend to do performance optimizations from a release to
+ release while making scalability related improvements just a couple of times. It's not because the scalability is of no interest. Usually, scalability requirements are set and solved once by a distributed system and
+ don't require significant additional interventions by engineers.
+ </p>
+ <p>
+ However, Apache Ignite grew to the point when the community decided to revisit its discovery subsystem that influences how well and far Ignite scales out. The goal was pretty clear - Ignite has to scale to 1000s of nodes
+ as good as it scales to 100s now.
</p>
<p>
- However, there is an unspoken side of the story. No matter how fast a platform is, we do not want to lose the data and encounter cluster restarts or other outages. To guarantee this we need to somehow make data persistent
- on the disk.
+ It took many months to get the task implemented. So, please join me in welcoming Apache Ignite 2.5 that now can be scaled easily to 1000s of nodes and goes with other exciting capabilities. Let's check out the most
+ prominent ones.
+ </p>
+ </div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-5-scaling.html">↓ Read all</a></div>
+ </article>
+ <article class="post">
+ <div class="post__header">
+ <h2><a href="/blog/apache-ignite-2-4-brings.html">Apache Ignite 2.4 ings Advanced Machine Learning and Spark DataFrames Capabilities</a></h2>
+ <div>
+ March 15, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-4-brings.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.4 ings Advanced Machine Learning and Spark DataFrames Capabilities%20https://ignite.apache.org/blog/apache-ignite-2-4-brings.html">Twitter</a>
+ </div>
+ </div>
+ <div class="post__content">
+ <p>
+ Usually, Ignite community rolls out a new version once in 3 months, but we had to make an exception for Apache Ignite 2.4 that consumed five months in total. We could easily blame Thanksgiving, Christmas and New Year
+ holidays for the delay and would be forgiven, but, in fact, we were forging the release you can't simply pass by.
</p>
+ <p>Let's dive in and search for a big fish.</p>
+ <h3>Machine Learning General Availability</h3>
<p>
- Most in-memory computing projects address the persistence dilemma by giving a way to sync data back to a relational database (RDBMS). That sounds reasonable and undoubtedly works pretty well in practice, but if we dig
- deeper, you’ll likely encounter the following limitations:
+ Eight months ago, at the time of Apache Ignite 2.0, we put out the first APIs that formed the foundation of the Ignite's machine learning component of today. Since that time, Ignite machine learning experts and
+ enthusiasts have been moving the liary to the general availability condition meticulously. And Ignite 2.4 became a milestone that let us consider the
+ <a href="https://apacheignite.readme.io/docs/machine-learning" target="_blank">ML Grid</a> to be production ready.
</p>
</div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-1-a.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-4-brings.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/apache-ignite-2-0-redesigned.html">Apache Ignite 2.0: Redesigned Off-heap Memory, DDL and Machine Learning</a></h2>
+ <h2><a href="/blog/meltdown-and-spectre-patches-show.html">Meltdown and Spectre patches show negligible impact to Apache Ignite performance</a></h2>
<div>
- May 5, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-0-redesigned.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite 2.0: Redesigned Off-heap Memory, DDL and Machine Learning%20https://ignite.apache.org/blog/apache-ignite-2-0-redesigned.html">Twitter</a>
+ January 30, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/meltdown-and-spectre-patches-show.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Meltdown and Spectre patches show negligible impact to Apache Ignite performance%20https://ignite.apache.org/blog/meltdown-and-spectre-patches-show.html">Twitter</a>
</div>
</div>
<div class="post__content">
<p>
- We released the long-awaited Apache Ignite version 2.0 on May 5. The community spent almost a year incorporating tremendous changes to the legacy Apache Ignite 1.x architecture. And all of that effort paid off. Our
- collective blood, sweat (and perhaps even a few tears) opened up new and exciting opportunities for the Apache Ignite project.
+ As promised in my <a href="https://blogs.apache.org/ignite/entry/protecting-apache-ignite-from-meltdown">initial blog post</a> on this matter, Apache Ignite community applied security patches against the
+ notorious Meltdown Spectre vulnerabilities and completed performance testing of general operations and workloads that are typical for Ignite deployments.
</p>
- <p>Have I piqued your interest about this new release yet? Let's walk through some of the main new features that have appeared under the hood of Apache Ignite 2.0.</p>
+ <p>
+ The security patches were applied only for <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5754" target="_blank">CVE-2017-5754</a> (Meltdown) and <a
+ href="https://nvd.nist.gov/vuln/detail/CVE-2017-5753"
+ target="_blank"
+ >CVE-2017-5753</a
+ > (Spectre Variant 1) vulnerabilities. The patches for <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5715" target="_blank">CVE-2017-5715</a> (Spectre Variant 2) for the hardware the community used for
+ testing are not stable yet an can
+ <a href="https://newsroom.intel.com/news/root-cause-of-reboot-issue-identified-updated-guidance-for-customers-and-partners/" target="_blank">cause system reboot issues or another unpredictable behavior</a>.
+ </p>
+ <p>The applied patches have shown that the performance implications are negligible - the performance drop is just in the 0 - 7% range as the figure shows:</p>
</div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-0-redesigned.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/meltdown-and-spectre-patches-show.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/presenting-apache-ignite-sql-grid.html">Presenting Apache Ignite SQL Grid at Big Data Bootcamp</a></h2>
+ <h2><a href="/blog/protecting-apache-ignite-from-meltdown.html">Protecting Apache Ignite from 'Meltdown' and 'Spectre' vulnerabilities</a></h2>
<div>
- March 13, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/presenting-apache-ignite-sql-grid.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Presenting Apache Ignite SQL Grid at Big Data Bootcamp%20https://ignite.apache.org/blog/presenting-apache-ignite-sql-grid.html">Twitter</a>
+ January 8, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/protecting-apache-ignite-from-meltdown.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Protecting Apache Ignite from 'Meltdown' and 'Spectre' vulnerabilities%20https://ignite.apache.org/blog/protecting-apache-ignite-from-meltdown.html">Twitter</a>
</div>
</div>
<div class="post__content">
<p>
- Apache Ignite community welcomes you to attend <a href="http://globalbigdataconference.com/santa-clara/big-data-bootcamp/event-79.html" target="_blank">Big Data Bootcamp</a> on March 27th, 28th and 29th 2017 in Santa
- Clara, USA.
+ The world was rocked after the recent disclosure of the
+ <a href="https://www.vox.com/business-and-finance/2018/1/4/16850004/meltdown-spectre-intel-security-flaw-update" target="_blank">Meltdown and Spectre</a> vulnerabilities that literally affect almost all software ever
+ developed. Both issues are related to the way all modern CPUs are designed and this is why they have opened unprecedented security breaches -- making the software, including Apache Ignite, vulnerable to
+ hacker attacks.
+ </p>
+ <p>The vulnerabilities are registered in the National Vulnerability Database under the following CVEs:</p>
+ <ul>
+ <li><a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5753" target="_blank">CVE-2017-5753</a> — Spectre variant 1</li>
+ <li><a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5715" target="_blank">CVE-2017-5715</a> — Spectre variant 2</li>
+ <li><a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5754" target="_blank">CVE-2017-5754</a> — Meltdown</li>
+ </ul>
+ </div>
+ <div class="post__footer"><a class="more" href="/blog/protecting-apache-ignite-from-meltdown.html">↓ Read all</a></div>
+ </article>
+ <article class="post">
+ <div class="post__header">
+ <h2><a href="/blog/apache-ignite-essentials-series-for.html">Apache Ignite Essentials: 2-part Webinar Series for Architects and Java Developers</a></h2>
+ <div>
+ November 17, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-essentials-series-for.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite Essentials: 2-part Webinar Series for Architects and Java Developers%20https://ignite.apache.org/blog/apache-ignite-essentials-series-for.html">Twitter</a>
+ </div>
+ </div>
+ <div class="post__content">
+ <p class="entryContent">
+ We finally made this happen! I’m happy to invite all of the software architects and engineers out there to a series of webinars that will introduce you to the fundamental capabilities of in-memory computing platforms
+ such as Apache Ignite.
</p>
+ <p>There will also be a mix of theory and practice. A lot of code examples are waiting to be shown so that you can apply the theory in practice right away.</p>
+ <p>The series consists of two parts.</p>
+ <h3><a href="https://ignite.apache.org/events.html#in-memory-computing-essentials-architects-and-developers-part-1" target="_blank">Part 1: Tuesday, November 21, 2017, 11:00am PT / 2:00pm ET</a></h3>
+ To be covered:
+ <ul>
+ <li>Cluster configuration and deployment.</li>
+ <li>Distributed database internals (partitioning, replication).</li>
+ <li>Data processing with key-value APIs.</li>
+ <li>Affinity Collocation.</li>
+ <li>Data processing with SQL.</li>
+ </ul>
+ </div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-essentials-series-for.html">↓ Read all</a></div>
+ </article>
+ <article class="post">
+ <div class="post__header">
+ <h2><a href="/blog/apache-ignite-2-3-more.html">Apache Ignite 2.3 - More SQL and Persistence Capabilities</a></h2>
+ <div>
+ November 1, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-3-more.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.3 - More SQL and Persistence Capabilities%20https://ignite.apache.org/blog/apache-ignite-2-3-more.html">Twitter</a>
+ </div>
+ </div>
+ <div class="post__content">
+ <p>Putting aside the regular bug fixes and performance optimizations, the Apache Ignite 2.3 release brings new SQL capabilities and Ignite persistence improvements that are worth mentioning.</p>
+ <p></p>
+ <h3>SQL</h3>
+ <p></p>
+ <p>Let's start with SQL first.</p>
+ <p>Apache Ignite users have consistently told us that despite all of Ignite’s SQL capabilities, it’s been at times challenging trying to figure out how to start using Ignite as an SQL database.</p>
<p>
- The conference gathers experts and vendors from Big Data realm in sunny California who will be covering a variety of Big Data products and technologies, including, but not limited to, Hadoop, Spark, NoSQL, Data Science,
- Machine Learning, Artificial Intelligence & Deep Learning.
+ This was mostly caused by scattered documentation pages, lack of “getting started” guides and tutorials. We’ve remedied this oversight! All related SQL knowledge has been curated in a
+ <a href="https://apacheignite-sql.readme.io/docs" target="_blank">single documentation domain</a>.
+ </p>
+ </div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-3-more.html">↓ Read all</a></div>
+ </article>
+ <article class="post">
+ <div class="post__header">
+ <h2><a href="/blog/apache-ignite-community-news-september.html">Apache Ignite Community News (Issue 3)</a></h2>
+ <div>
+ September 15, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-community-news-september.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite Community News (Issue 3)%20https://ignite.apache.org/blog/apache-ignite-community-news-september.html">Twitter</a>
+ </div>
+ </div>
+ <div class="post__content">
+ <p><b>by Tom Diederich</b></p>
+ <p>This is our third community update – there’s a lot going on, so let's get started.</p>
+ <p>Apache Ignite experts have already spoken at two meetups this month, both in Silicon Valley, but there are several more scheduled this month around the world.</p>
+ <p></p>
+ <p style="margin-bottom: 15pt">
+ <span style="line-height: 19.5pt"
+ ><span style="font-family: Helvetica"
+ ><span style="color: #333333"
+ >On <b>Sept. 9</b> Apache Ignite PMC chair Denis Magda was the featured presenter at the<b> </b
+ ><a href="https://www.meetup.com/datariders/events/242523245/"
+ ><b><span style="color: #467d76">Big Data and Cloud Meetup</span></b></a
+ >
+ in Santa Clara, Calif. His talk, titled "Apache Spark and Apache Ignite: Where Fast Data Meets the IoT," was highly rated and we’re planning a hands-on workshop with meetup organizers for
+ November.</span
+ ></span
+ ></span
+ >
</p>
- <p>Apache Ignite will be introduced at the conference by its PMC chair and committer - Denis Magda.</p>
</div>
- <div class="post__footer"><a class="more" href="/blog/presenting-apache-ignite-sql-grid.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-community-news-september.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/apache-ignite-1-9-released.html">Apache Ignite 1.9 Released</a></h2>
+ <h2><a href="/blog/apache-ignite-community-update-august.html">Apache Ignite Community Update (August 2017 Issue)</a></h2>
<div>
- March 7, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-1-9-released.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite 1.9 Released%20https://ignite.apache.org/blog/apache-ignite-1-9-released.html">Twitter</a>
+ August 30, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-community-update-august.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite Community Update (August 2017 Issue)%20https://ignite.apache.org/blog/apache-ignite-community-update-august.html">Twitter</a>
</div>
</div>
<div class="post__content">
<p>
- Apache Ignite community is pleased to announce Apache Ignite 1.9 - the next minor release of a well-known in-memory data fabric. The release, as usual, encompasses many bug fixes, performance improvements and fresh
- features. Below you can see a description of the most significant updates.
+ <b><i>by Tom Diederich</i></b>
</p>
- <p><b>Kubernetes Support</b></p>
<p>
- Apache Ignite was integrated with Kubernetes which is a modern open source container cluster manager. The integration helps to simplify a deployment of an Apache Ignite cluster in environments managed by Kubernetes and let
- the latter care of resources management, cluster's scalability and lifecycle.
+ Igniters, here are some community highlights from the last couple week. If I missed anything, please share it here. Meetups! Did you know that Apache Ignite experts are available to speak at your meetup? And we also have
+ spots open for YOU to speak at the following meetups that some of us co-organize:
</p>
+ <ul>
+ <li><a href="https://www.meetup.com/Apache-Ignite-London/" target="_blank">Apache Ignite London</a></li>
+ <li><a href="https://www.meetup.com/Bay-Area-In-Memory-Computing/" target="_blank">Bay Area In-Memory Computing Meetup</a></li>
+ <li><a href="https://www.meetup.com/NYC-In-Memory-Computing-Meetup/" target="_blank">NYC In-Memory Computing Meetup</a></li>
+ <li><a href="https://www.meetup.com/Moscow-Apache-Ignite-Meetup/" target="_blank">Moscow Apache Ignite Meetup</a></li>
+ </ul>
</div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-1-9-released.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-community-update-august.html">↓ Read all</a></div>
</article>
</section>
<section class="blog__footer">
@@ -485,6 +600,7 @@
<li><a class="item" href="/blog/">1</a></li>
<li><a class="item" href="/blog/1/">2</a></li>
<li><a class="current" href="/blog/2/">3</a></li>
+ <li><a class="item" href="/blog/3/">4</a></li>
</ul>
</section>
</main>
@@ -590,6 +706,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache/1/index.html b/blog/3/index.html
similarity index 92%
copy from blog/apache/1/index.html
copy to blog/3/index.html
index 772d8c4c5b..0490ff0c32 100644
--- a/blog/apache/1/index.html
+++ b/blog/3/index.html
@@ -3,8 +3,8 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1" />
- <title>Entries tagged [apache]</title>
- <meta property="og:title" content="Entries tagged [apache]" />
+ <title>Apache Ignite Blog</title>
+ <meta property="og:title" content="Apache Ignite Blog" />
<link rel="canonical" href="https://ignite.apache.org/blog" />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://ignite.apache.org/blog" />
@@ -337,10 +337,34 @@
<div class="dropmenu__back"></div>
<header class="hdrfloat hdr__white jsHdrFloatBase"></header>
<div class="container blog">
- <section class="blog__header"><h1>Entries tagged [apache]</h1></section>
+ <section class="blog__header"><h1>Apache Ignite Blog</h1></section>
<div class="blog__content">
<main class="blog_main">
<section class="blog__posts">
+ <article class="post">
+ <div class="post__header">
+ <h2><a href="/blog/apache-ignite-2-1-a.html">Apache Ignite 2.1 - A Leap from In-Memory to Memory-Centric Architecture</a></h2>
+ <div>
+ July 27, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-1-a.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.1 - A Leap from In-Memory to Memory-Centric Architecture%20https://ignite.apache.org/blog/apache-ignite-2-1-a.html">Twitter</a>
+ </div>
+ </div>
+ <div class="post__content">
+ <p>
+ The power and beauty of in-memory computing projects are that they truly do what they state -- deliver outstanding performance improvements by moving data closer to the CPU, using RAM as a storage and spreading the data
+ sets out across a cluster of machines relying on horizontal scalability.
+ </p>
+ <p>
+ However, there is an unspoken side of the story. No matter how fast a platform is, we do not want to lose the data and encounter cluster restarts or other outages. To guarantee this we need to somehow make data persistent
+ on the disk.
+ </p>
+ <p>
+ Most in-memory computing projects address the persistence dilemma by giving a way to sync data back to a relational database (RDBMS). That sounds reasonable and undoubtedly works pretty well in practice, but if we dig
+ deeper, you’ll likely encounter the following limitations:
+ </p>
+ </div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-1-a.html">↓ Read all</a></div>
+ </article>
<article class="post">
<div class="post__header">
<h2><a href="/blog/apache-ignite-2-0-redesigned.html">Apache Ignite 2.0: Redesigned Off-heap Memory, DDL and Machine Learning</a></h2>
@@ -403,8 +427,10 @@
</section>
<section class="blog__footer">
<ul class="pagination">
- <li><a class="item" href="/blog/apache">1</a></li>
- <li><a class="current" href="/blog/apache/1/">2</a></li>
+ <li><a class="item" href="/blog/">1</a></li>
+ <li><a class="item" href="/blog/1/">2</a></li>
+ <li><a class="item" href="/blog/2/">3</a></li>
+ <li><a class="current" href="/blog/3/">4</a></li>
</ul>
</section>
</main>
@@ -510,6 +536,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/CET/index.html b/blog/CET/index.html
index 57dfbdc88c..42dd6e3d3f 100644
--- a/blog/CET/index.html
+++ b/blog/CET/index.html
@@ -459,6 +459,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/Intel/index.html b/blog/Intel/index.html
index c535fbf7c7..cbe6045b02 100644
--- a/blog/Intel/index.html
+++ b/blog/Intel/index.html
@@ -459,6 +459,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/SQL/index.html b/blog/SQL/index.html
index b733e7edd5..d4e2ac5769 100644
--- a/blog/SQL/index.html
+++ b/blog/SQL/index.html
@@ -3,8 +3,8 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1" />
- <title>Entries tagged [sql]</title>
- <meta property="og:title" content="Entries tagged [sql]" />
+ <title>Entries tagged [SQL]</title>
+ <meta property="og:title" content="Entries tagged [SQL]" />
<link rel="canonical" href="https://ignite.apache.org/blog" />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://ignite.apache.org/blog" />
@@ -337,97 +337,22 @@
<div class="dropmenu__back"></div>
<header class="hdrfloat hdr__white jsHdrFloatBase"></header>
<div class="container blog">
- <section class="blog__header"><h1>Entries tagged [sql]</h1></section>
+ <section class="blog__header"><h1>Entries tagged [SQL]</h1></section>
<div class="blog__content">
<main class="blog_main">
<section class="blog__posts">
<article class="post">
<div class="post__header">
- <h2><a href="/blog/apache-ignite-2-5-scaling.html">Apache Ignite 2.5: Scaling to 1000s Nodes Clusters</a></h2>
+ <h2><a href="/blog/apache-ignite-net-dynamic-linq.html">Dynamic LINQ performance and usability with Ignite.NET and System.Linq.Dynamic</a></h2>
<div>
- May 31, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-5-scaling.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite 2.5: Scaling to 1000s Nodes Clusters%20https://ignite.apache.org/blog/apache-ignite-2-5-scaling.html">Twitter</a>
+ May 22, 2023 by Pavel Tupitsyn. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-net-dynamic-linq.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Dynamic LINQ performance and usability with Ignite.NET and System.Linq.Dynamic%20https://ignite.apache.org/blog/apache-ignite-net-dynamic-linq.html">Twitter</a>
</div>
</div>
<div class="post__content">
- <p>
- Apache Ignite was always appreciated by its users for two primary things it delivers - scalability and performance. Throughout the lifetime many distributed systems tend to do performance optimizations from a release to
- release while making scalability related improvements just a couple of times. It's not because the scalability is of no interest. Usually, scalability requirements are set and solved once by a distributed system and
- don't require significant additional interventions by engineers.
- </p>
- <p>
- However, Apache Ignite grew to the point when the community decided to revisit its discovery subsystem that influences how well and far Ignite scales out. The goal was pretty clear - Ignite has to scale to 1000s of nodes
- as good as it scales to 100s now.
- </p>
- <p>
- It took many months to get the task implemented. So, please join me in welcoming Apache Ignite 2.5 that now can be scaled easily to 1000s of nodes and goes with other exciting capabilities. Let's check out the most
- prominent ones.
- </p>
+ <p>Dynamically building database queries can be necessary for some use cases, such as UI-defined filtering. This can get challenging with LINQ frameworks like EF Core and Ignite.NET.</p>
+ <p><a href="https://ptupitsyn.github.io/Dynamic-LINQ-With-Ignite/">Read More...</a></p>
</div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-5-scaling.html">↓ Read all</a></div>
- </article>
- <article class="post">
- <div class="post__header">
- <h2><a href="/blog/apache-ignite-2-3-more.html">Apache Ignite 2.3 - More SQL and Persistence Capabilities</a></h2>
- <div>
- November 1, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-3-more.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite 2.3 - More SQL and Persistence Capabilities%20https://ignite.apache.org/blog/apache-ignite-2-3-more.html">Twitter</a>
- </div>
- </div>
- <div class="post__content">
- <p>Putting aside the regular bug fixes and performance optimizations, the Apache Ignite 2.3 release brings new SQL capabilities and Ignite persistence improvements that are worth mentioning.</p>
- <p></p>
- <h3>SQL</h3>
- <p></p>
- <p>Let's start with SQL first.</p>
- <p>Apache Ignite users have consistently told us that despite all of Ignite’s SQL capabilities, it’s been at times challenging trying to figure out how to start using Ignite as an SQL database.</p>
- <p>
- This was mostly caused by scattered documentation pages, lack of “getting started” guides and tutorials. We’ve remedied this oversight! All related SQL knowledge has been curated in a
- <a href="https://apacheignite-sql.readme.io/docs" target="_blank">single documentation domain</a>.
- </p>
- </div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-3-more.html">↓ Read all</a></div>
- </article>
- <article class="post">
- <div class="post__header">
- <h2><a href="/blog/apache-ignite-2-1-a.html">Apache Ignite 2.1 - A Leap from In-Memory to Memory-Centric Architecture</a></h2>
- <div>
- July 27, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-1-a.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite 2.1 - A Leap from In-Memory to Memory-Centric Architecture%20https://ignite.apache.org/blog/apache-ignite-2-1-a.html">Twitter</a>
- </div>
- </div>
- <div class="post__content">
- <p>
- The power and beauty of in-memory computing projects are that they truly do what they state -- deliver outstanding performance improvements by moving data closer to the CPU, using RAM as a storage and spreading the data
- sets out across a cluster of machines relying on horizontal scalability.
- </p>
- <p>
- However, there is an unspoken side of the story. No matter how fast a platform is, we do not want to lose the data and encounter cluster restarts or other outages. To guarantee this we need to somehow make data persistent
- on the disk.
- </p>
- <p>
- Most in-memory computing projects address the persistence dilemma by giving a way to sync data back to a relational database (RDBMS). That sounds reasonable and undoubtedly works pretty well in practice, but if we dig
- deeper, you’ll likely encounter the following limitations:
- </p>
- </div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-1-a.html">↓ Read all</a></div>
- </article>
- <article class="post">
- <div class="post__header">
- <h2><a href="/blog/apache-ignite-2-0-redesigned.html">Apache Ignite 2.0: Redesigned Off-heap Memory, DDL and Machine Learning</a></h2>
- <div>
- May 5, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-0-redesigned.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite 2.0: Redesigned Off-heap Memory, DDL and Machine Learning%20https://ignite.apache.org/blog/apache-ignite-2-0-redesigned.html">Twitter</a>
- </div>
- </div>
- <div class="post__content">
- <p>
- We released the long-awaited Apache Ignite version 2.0 on May 5. The community spent almost a year incorporating tremendous changes to the legacy Apache Ignite 1.x architecture. And all of that effort paid off. Our
- collective blood, sweat (and perhaps even a few tears) opened up new and exciting opportunities for the Apache Ignite project.
- </p>
- <p>Have I piqued your interest about this new release yet? Let's walk through some of the main new features that have appeared under the hood of Apache Ignite 2.0.</p>
- </div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-0-redesigned.html">↓ Read all</a></div>
</article>
</section>
<section class="blog__footer"><ul class="pagination"></ul></section>
@@ -534,6 +459,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache-ignite-1-9-released.html b/blog/apache-ignite-1-9-released.html
index 0dd64d0694..b7e1661b2c 100644
--- a/blog/apache-ignite-1-9-released.html
+++ b/blog/apache-ignite-1-9-released.html
@@ -508,6 +508,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache-ignite-2-0-redesigned.html b/blog/apache-ignite-2-0-redesigned.html
index 660d84bf04..56aed9c419 100644
--- a/blog/apache-ignite-2-0-redesigned.html
+++ b/blog/apache-ignite-2-0-redesigned.html
@@ -543,6 +543,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache-ignite-2-1-a.html b/blog/apache-ignite-2-1-a.html
index 004e8087bd..adf31d5431 100644
--- a/blog/apache-ignite-2-1-a.html
+++ b/blog/apache-ignite-2-1-a.html
@@ -546,6 +546,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache-ignite-2-10-thin.html b/blog/apache-ignite-2-10-thin.html
index cd0fff676d..f82f95197d 100644
--- a/blog/apache-ignite-2-10-thin.html
+++ b/blog/apache-ignite-2-10-thin.html
@@ -537,6 +537,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache-ignite-2-11-1.html b/blog/apache-ignite-2-11-1.html
index 0a2a45a0ed..53b306a9cc 100644
--- a/blog/apache-ignite-2-11-1.html
+++ b/blog/apache-ignite-2-11-1.html
@@ -496,6 +496,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache-ignite-2-11-stabilization.html b/blog/apache-ignite-2-11-stabilization.html
index 80c817fdb8..566ec30aa6 100644
--- a/blog/apache-ignite-2-11-stabilization.html
+++ b/blog/apache-ignite-2-11-stabilization.html
@@ -536,6 +536,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache-ignite-2-12-0.html b/blog/apache-ignite-2-12-0.html
index 398e2970ad..978a0c7ea5 100644
--- a/blog/apache-ignite-2-12-0.html
+++ b/blog/apache-ignite-2-12-0.html
@@ -541,6 +541,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache-ignite-2-13-0.html b/blog/apache-ignite-2-13-0.html
index 17d6f93342..3287f25a4a 100644
--- a/blog/apache-ignite-2-13-0.html
+++ b/blog/apache-ignite-2-13-0.html
@@ -532,6 +532,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache-ignite-2-16-0.html b/blog/apache-ignite-2-16-0.html
index 3051b07181..c86eb4cdaa 100644
--- a/blog/apache-ignite-2-16-0.html
+++ b/blog/apache-ignite-2-16-0.html
@@ -545,6 +545,7 @@ new DumpReader(cfg, log).run();</pre
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache-ignite-2-17-0.html b/blog/apache-ignite-2-17-0.html
index d316da3752..13c81c7a9e 100644
--- a/blog/apache-ignite-2-17-0.html
+++ b/blog/apache-ignite-2-17-0.html
@@ -554,6 +554,7 @@ cache.invoke(0, new IncrementProcessor());</pre
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache-ignite-2-3-more.html b/blog/apache-ignite-2-3-more.html
index a2db70b1bf..fbf64f73a1 100644
--- a/blog/apache-ignite-2-3-more.html
+++ b/blog/apache-ignite-2-3-more.html
@@ -516,6 +516,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache-ignite-2-4-brings.html b/blog/apache-ignite-2-4-brings.html
index 1b1ea0e7ff..dc55f90f0e 100644
--- a/blog/apache-ignite-2-4-brings.html
+++ b/blog/apache-ignite-2-4-brings.html
@@ -522,6 +522,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache-ignite-2-5-scaling.html b/blog/apache-ignite-2-5-scaling.html
index 19cd838639..abc32579fb 100644
--- a/blog/apache-ignite-2-5-scaling.html
+++ b/blog/apache-ignite-2-5-scaling.html
@@ -568,6 +568,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache-ignite-2-7-deep.html b/blog/apache-ignite-2-7-deep.html
index 263851d977..1d9cb4e593 100644
--- a/blog/apache-ignite-2-7-deep.html
+++ b/blog/apache-ignite-2-7-deep.html
@@ -495,6 +495,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache-ignite-2-9-released.html b/blog/apache-ignite-2-9-released.html
index b54b19f535..aecf48c4ce 100644
--- a/blog/apache-ignite-2-9-released.html
+++ b/blog/apache-ignite-2-9-released.html
@@ -495,6 +495,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache-ignite-3-architecture-part-2.html b/blog/apache-ignite-3-architecture-part-2.html
index ca19ae087d..2e0433ab6b 100644
--- a/blog/apache-ignite-3-architecture-part-2.html
+++ b/blog/apache-ignite-3-architecture-part-2.html
@@ -449,7 +449,6 @@ long totalTime = System.nanoTime() - startTime;
<hr />
<br />
<h3>Memory-First Architecture Principles</h3>
- <br />
<h3>Off-Heap Memory Management</h3>
<p>Apache Ignite manages memory regions directly outside the JVM heap to eliminate garbage collection interference.</p>
<p><strong>Performance Benefits:</strong></p>
@@ -518,7 +517,7 @@ long totalTime = System.nanoTime() - startTime;
<hr />
<br />
<h3>Performance Characteristics at Event Scale</h3>
- <p>Memory-First Performance Profile</p>
+ <h3>Memory-First Performance Profile</h3>
<p><strong>Event Processing Characteristics</strong>:</p>
<ul>
<li><strong>Write Operations</strong>: Events commit to memory efficiently</li>
diff --git a/blog/apache-ignite-community-news-september.html b/blog/apache-ignite-community-news-september.html
index 468d04f76c..3bf9da7aa0 100644
--- a/blog/apache-ignite-community-news-september.html
+++ b/blog/apache-ignite-community-news-september.html
@@ -643,6 +643,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache-ignite-community-update-august.html b/blog/apache-ignite-community-update-august.html
index c270189202..3f82cd3f74 100644
--- a/blog/apache-ignite-community-update-august.html
+++ b/blog/apache-ignite-community-update-august.html
@@ -560,6 +560,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache-ignite-essentials-series-for.html b/blog/apache-ignite-essentials-series-for.html
index 64bc200315..ca9d6eda70 100644
--- a/blog/apache-ignite-essentials-series-for.html
+++ b/blog/apache-ignite-essentials-series-for.html
@@ -483,6 +483,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache-ignite-momentum-highlights-from.html b/blog/apache-ignite-momentum-highlights-from.html
index 2ecbdc7c72..ee0230f5c8 100644
--- a/blog/apache-ignite-momentum-highlights-from.html
+++ b/blog/apache-ignite-momentum-highlights-from.html
@@ -532,6 +532,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache-ignite-net-dynamic-linq.html b/blog/apache-ignite-net-dynamic-linq.html
index 3f4d222aca..cadda495fb 100644
--- a/blog/apache-ignite-net-dynamic-linq.html
+++ b/blog/apache-ignite-net-dynamic-linq.html
@@ -464,6 +464,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache-ignite-net-intel-cet-fix.html b/blog/apache-ignite-net-intel-cet-fix.html
index 931e9ec984..c50117f1b7 100644
--- a/blog/apache-ignite-net-intel-cet-fix.html
+++ b/blog/apache-ignite-net-intel-cet-fix.html
@@ -463,6 +463,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache/1/index.html b/blog/apache/1/index.html
index 772d8c4c5b..4434fbb361 100644
--- a/blog/apache/1/index.html
+++ b/blog/apache/1/index.html
@@ -341,6 +341,207 @@
<div class="blog__content">
<main class="blog_main">
<section class="blog__posts">
+ <article class="post">
+ <div class="post__header">
+ <h2><a href="/blog/apache-ignite-2-4-brings.html">Apache Ignite 2.4 ings Advanced Machine Learning and Spark DataFrames Capabilities</a></h2>
+ <div>
+ March 15, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-4-brings.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.4 ings Advanced Machine Learning and Spark DataFrames Capabilities%20https://ignite.apache.org/blog/apache-ignite-2-4-brings.html">Twitter</a>
+ </div>
+ </div>
+ <div class="post__content">
+ <p>
+ Usually, Ignite community rolls out a new version once in 3 months, but we had to make an exception for Apache Ignite 2.4 that consumed five months in total. We could easily blame Thanksgiving, Christmas and New Year
+ holidays for the delay and would be forgiven, but, in fact, we were forging the release you can't simply pass by.
+ </p>
+ <p>Let's dive in and search for a big fish.</p>
+ <h3>Machine Learning General Availability</h3>
+ <p>
+ Eight months ago, at the time of Apache Ignite 2.0, we put out the first APIs that formed the foundation of the Ignite's machine learning component of today. Since that time, Ignite machine learning experts and
+ enthusiasts have been moving the liary to the general availability condition meticulously. And Ignite 2.4 became a milestone that let us consider the
+ <a href="https://apacheignite.readme.io/docs/machine-learning" target="_blank">ML Grid</a> to be production ready.
+ </p>
+ </div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-4-brings.html">↓ Read all</a></div>
+ </article>
+ <article class="post">
+ <div class="post__header">
+ <h2><a href="/blog/meltdown-and-spectre-patches-show.html">Meltdown and Spectre patches show negligible impact to Apache Ignite performance</a></h2>
+ <div>
+ January 30, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/meltdown-and-spectre-patches-show.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Meltdown and Spectre patches show negligible impact to Apache Ignite performance%20https://ignite.apache.org/blog/meltdown-and-spectre-patches-show.html">Twitter</a>
+ </div>
+ </div>
+ <div class="post__content">
+ <p>
+ As promised in my <a href="https://blogs.apache.org/ignite/entry/protecting-apache-ignite-from-meltdown">initial blog post</a> on this matter, Apache Ignite community applied security patches against the
+ notorious Meltdown Spectre vulnerabilities and completed performance testing of general operations and workloads that are typical for Ignite deployments.
+ </p>
+ <p>
+ The security patches were applied only for <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5754" target="_blank">CVE-2017-5754</a> (Meltdown) and <a
+ href="https://nvd.nist.gov/vuln/detail/CVE-2017-5753"
+ target="_blank"
+ >CVE-2017-5753</a
+ > (Spectre Variant 1) vulnerabilities. The patches for <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5715" target="_blank">CVE-2017-5715</a> (Spectre Variant 2) for the hardware the community used for
+ testing are not stable yet an can
+ <a href="https://newsroom.intel.com/news/root-cause-of-reboot-issue-identified-updated-guidance-for-customers-and-partners/" target="_blank">cause system reboot issues or another unpredictable behavior</a>.
+ </p>
+ <p>The applied patches have shown that the performance implications are negligible - the performance drop is just in the 0 - 7% range as the figure shows:</p>
+ </div>
+ <div class="post__footer"><a class="more" href="/blog/meltdown-and-spectre-patches-show.html">↓ Read all</a></div>
+ </article>
+ <article class="post">
+ <div class="post__header">
+ <h2><a href="/blog/protecting-apache-ignite-from-meltdown.html">Protecting Apache Ignite from 'Meltdown' and 'Spectre' vulnerabilities</a></h2>
+ <div>
+ January 8, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/protecting-apache-ignite-from-meltdown.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Protecting Apache Ignite from 'Meltdown' and 'Spectre' vulnerabilities%20https://ignite.apache.org/blog/protecting-apache-ignite-from-meltdown.html">Twitter</a>
+ </div>
+ </div>
+ <div class="post__content">
+ <p>
+ The world was rocked after the recent disclosure of the
+ <a href="https://www.vox.com/business-and-finance/2018/1/4/16850004/meltdown-spectre-intel-security-flaw-update" target="_blank">Meltdown and Spectre</a> vulnerabilities that literally affect almost all software ever
+ developed. Both issues are related to the way all modern CPUs are designed and this is why they have opened unprecedented security breaches -- making the software, including Apache Ignite, vulnerable to
+ hacker attacks.
+ </p>
+ <p>The vulnerabilities are registered in the National Vulnerability Database under the following CVEs:</p>
+ <ul>
+ <li><a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5753" target="_blank">CVE-2017-5753</a> — Spectre variant 1</li>
+ <li><a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5715" target="_blank">CVE-2017-5715</a> — Spectre variant 2</li>
+ <li><a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5754" target="_blank">CVE-2017-5754</a> — Meltdown</li>
+ </ul>
+ </div>
+ <div class="post__footer"><a class="more" href="/blog/protecting-apache-ignite-from-meltdown.html">↓ Read all</a></div>
+ </article>
+ <article class="post">
+ <div class="post__header">
+ <h2><a href="/blog/apache-ignite-essentials-series-for.html">Apache Ignite Essentials: 2-part Webinar Series for Architects and Java Developers</a></h2>
+ <div>
+ November 17, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-essentials-series-for.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite Essentials: 2-part Webinar Series for Architects and Java Developers%20https://ignite.apache.org/blog/apache-ignite-essentials-series-for.html">Twitter</a>
+ </div>
+ </div>
+ <div class="post__content">
+ <p class="entryContent">
+ We finally made this happen! I’m happy to invite all of the software architects and engineers out there to a series of webinars that will introduce you to the fundamental capabilities of in-memory computing platforms
+ such as Apache Ignite.
+ </p>
+ <p>There will also be a mix of theory and practice. A lot of code examples are waiting to be shown so that you can apply the theory in practice right away.</p>
+ <p>The series consists of two parts.</p>
+ <h3><a href="https://ignite.apache.org/events.html#in-memory-computing-essentials-architects-and-developers-part-1" target="_blank">Part 1: Tuesday, November 21, 2017, 11:00am PT / 2:00pm ET</a></h3>
+ To be covered:
+ <ul>
+ <li>Cluster configuration and deployment.</li>
+ <li>Distributed database internals (partitioning, replication).</li>
+ <li>Data processing with key-value APIs.</li>
+ <li>Affinity Collocation.</li>
+ <li>Data processing with SQL.</li>
+ </ul>
+ </div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-essentials-series-for.html">↓ Read all</a></div>
+ </article>
+ <article class="post">
+ <div class="post__header">
+ <h2><a href="/blog/apache-ignite-2-3-more.html">Apache Ignite 2.3 - More SQL and Persistence Capabilities</a></h2>
+ <div>
+ November 1, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-3-more.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.3 - More SQL and Persistence Capabilities%20https://ignite.apache.org/blog/apache-ignite-2-3-more.html">Twitter</a>
+ </div>
+ </div>
+ <div class="post__content">
+ <p>Putting aside the regular bug fixes and performance optimizations, the Apache Ignite 2.3 release brings new SQL capabilities and Ignite persistence improvements that are worth mentioning.</p>
+ <p></p>
+ <h3>SQL</h3>
+ <p></p>
+ <p>Let's start with SQL first.</p>
+ <p>Apache Ignite users have consistently told us that despite all of Ignite’s SQL capabilities, it’s been at times challenging trying to figure out how to start using Ignite as an SQL database.</p>
+ <p>
+ This was mostly caused by scattered documentation pages, lack of “getting started” guides and tutorials. We’ve remedied this oversight! All related SQL knowledge has been curated in a
+ <a href="https://apacheignite-sql.readme.io/docs" target="_blank">single documentation domain</a>.
+ </p>
+ </div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-3-more.html">↓ Read all</a></div>
+ </article>
+ <article class="post">
+ <div class="post__header">
+ <h2><a href="/blog/apache-ignite-community-news-september.html">Apache Ignite Community News (Issue 3)</a></h2>
+ <div>
+ September 15, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-community-news-september.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite Community News (Issue 3)%20https://ignite.apache.org/blog/apache-ignite-community-news-september.html">Twitter</a>
+ </div>
+ </div>
+ <div class="post__content">
+ <p><b>by Tom Diederich</b></p>
+ <p>This is our third community update – there’s a lot going on, so let's get started.</p>
+ <p>Apache Ignite experts have already spoken at two meetups this month, both in Silicon Valley, but there are several more scheduled this month around the world.</p>
+ <p></p>
+ <p style="margin-bottom: 15pt">
+ <span style="line-height: 19.5pt"
+ ><span style="font-family: Helvetica"
+ ><span style="color: #333333"
+ >On <b>Sept. 9</b> Apache Ignite PMC chair Denis Magda was the featured presenter at the<b> </b
+ ><a href="https://www.meetup.com/datariders/events/242523245/"
+ ><b><span style="color: #467d76">Big Data and Cloud Meetup</span></b></a
+ >
+ in Santa Clara, Calif. His talk, titled "Apache Spark and Apache Ignite: Where Fast Data Meets the IoT," was highly rated and we’re planning a hands-on workshop with meetup organizers for
+ November.</span
+ ></span
+ ></span
+ >
+ </p>
+ </div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-community-news-september.html">↓ Read all</a></div>
+ </article>
+ <article class="post">
+ <div class="post__header">
+ <h2><a href="/blog/apache-ignite-community-update-august.html">Apache Ignite Community Update (August 2017 Issue)</a></h2>
+ <div>
+ August 30, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-community-update-august.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite Community Update (August 2017 Issue)%20https://ignite.apache.org/blog/apache-ignite-community-update-august.html">Twitter</a>
+ </div>
+ </div>
+ <div class="post__content">
+ <p>
+ <b><i>by Tom Diederich</i></b>
+ </p>
+ <p>
+ Igniters, here are some community highlights from the last couple week. If I missed anything, please share it here. Meetups! Did you know that Apache Ignite experts are available to speak at your meetup? And we also have
+ spots open for YOU to speak at the following meetups that some of us co-organize:
+ </p>
+ <ul>
+ <li><a href="https://www.meetup.com/Apache-Ignite-London/" target="_blank">Apache Ignite London</a></li>
+ <li><a href="https://www.meetup.com/Bay-Area-In-Memory-Computing/" target="_blank">Bay Area In-Memory Computing Meetup</a></li>
+ <li><a href="https://www.meetup.com/NYC-In-Memory-Computing-Meetup/" target="_blank">NYC In-Memory Computing Meetup</a></li>
+ <li><a href="https://www.meetup.com/Moscow-Apache-Ignite-Meetup/" target="_blank">Moscow Apache Ignite Meetup</a></li>
+ </ul>
+ </div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-community-update-august.html">↓ Read all</a></div>
+ </article>
+ <article class="post">
+ <div class="post__header">
+ <h2><a href="/blog/apache-ignite-2-1-a.html">Apache Ignite 2.1 - A Leap from In-Memory to Memory-Centric Architecture</a></h2>
+ <div>
+ July 27, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-1-a.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.1 - A Leap from In-Memory to Memory-Centric Architecture%20https://ignite.apache.org/blog/apache-ignite-2-1-a.html">Twitter</a>
+ </div>
+ </div>
+ <div class="post__content">
+ <p>
+ The power and beauty of in-memory computing projects are that they truly do what they state -- deliver outstanding performance improvements by moving data closer to the CPU, using RAM as a storage and spreading the data
+ sets out across a cluster of machines relying on horizontal scalability.
+ </p>
+ <p>
+ However, there is an unspoken side of the story. No matter how fast a platform is, we do not want to lose the data and encounter cluster restarts or other outages. To guarantee this we need to somehow make data persistent
+ on the disk.
+ </p>
+ <p>
+ Most in-memory computing projects address the persistence dilemma by giving a way to sync data back to a relational database (RDBMS). That sounds reasonable and undoubtedly works pretty well in practice, but if we dig
+ deeper, you’ll likely encounter the following limitations:
+ </p>
+ </div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-1-a.html">↓ Read all</a></div>
+ </article>
<article class="post">
<div class="post__header">
<h2><a href="/blog/apache-ignite-2-0-redesigned.html">Apache Ignite 2.0: Redesigned Off-heap Memory, DDL and Machine Learning</a></h2>
@@ -379,32 +580,12 @@
</div>
<div class="post__footer"><a class="more" href="/blog/presenting-apache-ignite-sql-grid.html">↓ Read all</a></div>
</article>
- <article class="post">
- <div class="post__header">
- <h2><a href="/blog/apache-ignite-1-9-released.html">Apache Ignite 1.9 Released</a></h2>
- <div>
- March 7, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-1-9-released.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite 1.9 Released%20https://ignite.apache.org/blog/apache-ignite-1-9-released.html">Twitter</a>
- </div>
- </div>
- <div class="post__content">
- <p>
- Apache Ignite community is pleased to announce Apache Ignite 1.9 - the next minor release of a well-known in-memory data fabric. The release, as usual, encompasses many bug fixes, performance improvements and fresh
- features. Below you can see a description of the most significant updates.
- </p>
- <p><b>Kubernetes Support</b></p>
- <p>
- Apache Ignite was integrated with Kubernetes which is a modern open source container cluster manager. The integration helps to simplify a deployment of an Apache Ignite cluster in environments managed by Kubernetes and let
- the latter care of resources management, cluster's scalability and lifecycle.
- </p>
- </div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-1-9-released.html">↓ Read all</a></div>
- </article>
</section>
<section class="blog__footer">
<ul class="pagination">
<li><a class="item" href="/blog/apache">1</a></li>
<li><a class="current" href="/blog/apache/1/">2</a></li>
+ <li><a class="item" href="/blog/apache/2/">3</a></li>
</ul>
</section>
</main>
@@ -510,6 +691,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/biodata/index.html b/blog/apache/2/index.html
similarity index 94%
copy from blog/biodata/index.html
copy to blog/apache/2/index.html
index da902ae6c7..11a1e31421 100644
--- a/blog/biodata/index.html
+++ b/blog/apache/2/index.html
@@ -3,8 +3,8 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1" />
- <title>Entries tagged [biodata]</title>
- <meta property="og:title" content="Entries tagged [biodata]" />
+ <title>Entries tagged [apache]</title>
+ <meta property="og:title" content="Entries tagged [apache]" />
<link rel="canonical" href="https://ignite.apache.org/blog" />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://ignite.apache.org/blog" />
@@ -337,36 +337,39 @@
<div class="dropmenu__back"></div>
<header class="hdrfloat hdr__white jsHdrFloatBase"></header>
<div class="container blog">
- <section class="blog__header"><h1>Entries tagged [biodata]</h1></section>
+ <section class="blog__header"><h1>Entries tagged [apache]</h1></section>
<div class="blog__content">
<main class="blog_main">
<section class="blog__posts">
<article class="post">
<div class="post__header">
- <h2><a href="/blog/apache-ignite-2-1-a.html">Apache Ignite 2.1 - A Leap from In-Memory to Memory-Centric Architecture</a></h2>
+ <h2><a href="/blog/apache-ignite-1-9-released.html">Apache Ignite 1.9 Released</a></h2>
<div>
- July 27, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-1-a.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite 2.1 - A Leap from In-Memory to Memory-Centric Architecture%20https://ignite.apache.org/blog/apache-ignite-2-1-a.html">Twitter</a>
+ March 7, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-1-9-released.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 1.9 Released%20https://ignite.apache.org/blog/apache-ignite-1-9-released.html">Twitter</a>
</div>
</div>
<div class="post__content">
<p>
- The power and beauty of in-memory computing projects are that they truly do what they state -- deliver outstanding performance improvements by moving data closer to the CPU, using RAM as a storage and spreading the data
- sets out across a cluster of machines relying on horizontal scalability.
+ Apache Ignite community is pleased to announce Apache Ignite 1.9 - the next minor release of a well-known in-memory data fabric. The release, as usual, encompasses many bug fixes, performance improvements and fresh
+ features. Below you can see a description of the most significant updates.
</p>
+ <p><b>Kubernetes Support</b></p>
<p>
- However, there is an unspoken side of the story. No matter how fast a platform is, we do not want to lose the data and encounter cluster restarts or other outages. To guarantee this we need to somehow make data persistent
- on the disk.
- </p>
- <p>
- Most in-memory computing projects address the persistence dilemma by giving a way to sync data back to a relational database (RDBMS). That sounds reasonable and undoubtedly works pretty well in practice, but if we dig
- deeper, you’ll likely encounter the following limitations:
+ Apache Ignite was integrated with Kubernetes which is a modern open source container cluster manager. The integration helps to simplify a deployment of an Apache Ignite cluster in environments managed by Kubernetes and let
+ the latter care of resources management, cluster's scalability and lifecycle.
</p>
</div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-1-a.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-1-9-released.html">↓ Read all</a></div>
</article>
</section>
- <section class="blog__footer"><ul class="pagination"></ul></section>
+ <section class="blog__footer">
+ <ul class="pagination">
+ <li><a class="item" href="/blog/apache">1</a></li>
+ <li><a class="item" href="/blog/apache/1/">2</a></li>
+ <li><a class="current" href="/blog/apache/2/">3</a></li>
+ </ul>
+ </section>
</main>
<aside class="blog__sidebar">
<ul>
@@ -470,6 +473,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/apache/index.html b/blog/apache/index.html
index 8039bb6d3b..3dd14e40bc 100644
--- a/blog/apache/index.html
+++ b/blog/apache/index.html
@@ -503,34 +503,12 @@
</div>
<div class="post__footer"><a class="more" href="/blog/apache-ignite-2-5-scaling.html">↓ Read all</a></div>
</article>
- <article class="post">
- <div class="post__header">
- <h2><a href="/blog/apache-ignite-2-4-brings.html">Apache Ignite 2.4 ings Advanced Machine Learning and Spark DataFrames Capabilities</a></h2>
- <div>
- March 15, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-4-brings.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite 2.4 ings Advanced Machine Learning and Spark DataFrames Capabilities%20https://ignite.apache.org/blog/apache-ignite-2-4-brings.html">Twitter</a>
- </div>
- </div>
- <div class="post__content">
- <p>
- Usually, Ignite community rolls out a new version once in 3 months, but we had to make an exception for Apache Ignite 2.4 that consumed five months in total. We could easily blame Thanksgiving, Christmas and New Year
- holidays for the delay and would be forgiven, but, in fact, we were forging the release you can't simply pass by.
- </p>
- <p>Let's dive in and search for a big fish.</p>
- <h3>Machine Learning General Availability</h3>
- <p>
- Eight months ago, at the time of Apache Ignite 2.0, we put out the first APIs that formed the foundation of the Ignite's machine learning component of today. Since that time, Ignite machine learning experts and
- enthusiasts have been moving the liary to the general availability condition meticulously. And Ignite 2.4 became a milestone that let us consider the
- <a href="https://apacheignite.readme.io/docs/machine-learning" target="_blank">ML Grid</a> to be production ready.
- </p>
- </div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-4-brings.html">↓ Read all</a></div>
- </article>
</section>
<section class="blog__footer">
<ul class="pagination">
<li><a class="current" href="/blog/apache">1</a></li>
<li><a class="item" href="/blog/apache/1/">2</a></li>
+ <li><a class="item" href="/blog/apache/2/">3</a></li>
</ul>
</section>
</main>
diff --git a/blog/bigdata/index.html b/blog/bigdata/index.html
index 0494d91f9b..dfc46ef43c 100644
--- a/blog/bigdata/index.html
+++ b/blog/bigdata/index.html
@@ -544,6 +544,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/biodata/index.html b/blog/biodata/index.html
index da902ae6c7..1a4cf249aa 100644
--- a/blog/biodata/index.html
+++ b/blog/biodata/index.html
@@ -470,6 +470,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/computing/index.html b/blog/computing/index.html
index ea2275b578..adeb05af7b 100644
--- a/blog/computing/index.html
+++ b/blog/computing/index.html
@@ -474,6 +474,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/csharp/index.html b/blog/csharp/index.html
index 35463a5257..8d6f22b3ab 100644
--- a/blog/csharp/index.html
+++ b/blog/csharp/index.html
@@ -459,6 +459,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/data/index.html b/blog/data/index.html
index 429f1bfd6b..0ec1b3597a 100644
--- a/blog/data/index.html
+++ b/blog/data/index.html
@@ -486,6 +486,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/database/1/index.html b/blog/database/1/index.html
index cdc29e097c..947b6aff6d 100644
--- a/blog/database/1/index.html
+++ b/blog/database/1/index.html
@@ -521,6 +521,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/database/index.html b/blog/database/index.html
index e60b43883c..b31a41ddb9 100644
--- a/blog/database/index.html
+++ b/blog/database/index.html
@@ -689,6 +689,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/fast/index.html b/blog/fast/index.html
index 53569e52fb..244b45506c 100644
--- a/blog/fast/index.html
+++ b/blog/fast/index.html
@@ -469,6 +469,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/getting-to-know-apache-ignite-3.html b/blog/getting-to-know-apache-ignite-3.html
index 3067223238..84f85dfa62 100644
--- a/blog/getting-to-know-apache-ignite-3.html
+++ b/blog/getting-to-know-apache-ignite-3.html
@@ -117,7 +117,7 @@
<nav class="hdrmenu">
<ul class="flexi">
<li class="js-hasdrop"><a class="hdrmenu--expanded" href="/" data-panel="getStarted">Get Started</a></li>
- <li class="js-hasdrop"><a class="hdrmenu__current hdrmenu--expanded" href="/features" data-panel="features">Features</a></li>
+ <li class="js-hasdrop"><a class="hdrmenu--expanded" href="/features" data-panel="features">Features</a></li>
<li class="js-hasdrop"><a class="hdrmenu--expanded" href="/community.html" data-panel="community">Community</a></li>
<li><a href="/use-cases/provenusecases.html" data-panel="">Powered By</a></li>
<li class="js-hasdrop"><a class="hdrmenu--expanded" href="/resources.html" data-panel="resources">Resources</a></li>
@@ -729,6 +729,7 @@ CompletableFuture<Void> streaming = ignite.sql()
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/grid/index.html b/blog/grid/index.html
index cf18c2be9f..8e9b7e3d63 100644
--- a/blog/grid/index.html
+++ b/blog/grid/index.html
@@ -463,6 +463,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/ignite-2-8-released-less.html b/blog/ignite-2-8-released-less.html
index 27586ce401..ccfb5f94fc 100644
--- a/blog/ignite-2-8-released-less.html
+++ b/blog/ignite-2-8-released-less.html
@@ -534,6 +534,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/ignite/1/index.html b/blog/ignite/1/index.html
index 622b0f099a..75b42f0a21 100644
--- a/blog/ignite/1/index.html
+++ b/blog/ignite/1/index.html
@@ -343,264 +343,256 @@
<section class="blog__posts">
<article class="post">
<div class="post__header">
- <h2><a href="/blog/apache-ignite-2-10-thin.html">Apache Ignite 2.10: Thin Client Expansion</a></h2>
+ <h2><a href="/blog/apache-ignite-net-intel-cet-fix.html">Ignite on .NET 9 and Intel CET</a></h2>
<div>
- March 18, 2021 by Maxim Muzafarov. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-10-thin.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite 2.10: Thin Client Expansion%20https://ignite.apache.org/blog/apache-ignite-2-10-thin.html">Twitter</a>
+ November 22, 2024 by Pavel Tupitsyn. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-net-intel-cet-fix.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Ignite on .NET 9 and Intel CET%20https://ignite.apache.org/blog/apache-ignite-net-intel-cet-fix.html">Twitter</a>
</div>
</div>
<div class="post__content">
- <p class="entryContent">
- As of March 15, 2021, <a href="https://ignite.apache.org/">Apache Ignite</a> 2.10 has been released. You can directly check the full list of resolved <a href="https://s.apache.org/i3ny6">Important JIRA's</a> but here
- let’s briefly overview some valuable improvements.
- </p>
- <h3 id="thin-clients">Thin Clients</h3>
- Thin clients now support several important features which, previously were available only on the thick clients. Thin clients are always backward and forward compatible with the server nodes of the cluster, so the cluster
- upgrade process will be more convenient if the lack of these features prevented you from doing that.
- <p>See the list of what is changed for thin clients below:</p>
- <ul>
- <li>Transactions</li>
- <li>Service invocations</li>
- <li>Continuous Queries</li>
- <li>SQL API</li>
- <li>Cluster API</li>
- <li>Cache Async API</li>
- <li>Kubernetes Discovery (<em>ThinClientKubernetesAddressFinder</em>)</li>
- </ul>
- You may check the <a href="https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features">List of Thin Client Features</a> that supported by platforms you are interested in or see the
- <a href="https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-2.10/">What's new in Apache Ignite.NET 2.10</a>.
+ <p>Old JDK code meets new Intel security feature, JVM + CLR in one process, and a mysterious crash.</p>
+ <p><a href="https://ptupitsyn.github.io/Ignite-on-NET-9/">Read More...</a></p>
</div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-10-thin.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/ignite-2-8-released-less.html">Ignite 2.8 Released: Less Stress in Production and Advances in Machine Learning</a></h2>
+ <h2><a href="/blog/apache-ignite-2-16-0.html">Apache Ignite 2.16.0: Cache dumps, Calcite engine stabilization, JDK 14+ bug fixes</a></h2>
<div>
- March 11, 2020 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/ignite-2-8-released-less.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Ignite 2.8 Released: Less Stress in Production and Advances in Machine Learning%20https://ignite.apache.org/blog/ignite-2-8-released-less.html">Twitter</a>
+ December 25, 2023 by Nikita Amelchev. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-16-0.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.16.0: Cache dumps, Calcite engine stabilization, JDK 14+ bug fixes%20https://ignite.apache.org/blog/apache-ignite-2-16-0.html">Twitter</a>
</div>
</div>
<div class="post__content">
<p>
- With thousands of changes contributed to Apache Ignite 2.8 that enhanced almost all the components of the platform, it’s possible to overlook some of the improvements that can convince you to upgrade to this version
- sooner than later. While a quick check of the <a href="https://ignite.apache.org/releases/ignite2/2.8.0/release_notes.html" target="_blank">release notes</a> will help to discover anticipated bug fixes, this article aims
- to guide through enhancements every Ignite developer should be aware of.
+ As of December 25, 2023, <a href="https://ignite.apache.org/">Apache Ignite </a>2.16 has been released. You can directly check the full list of resolved <a href="https://s.apache.org/j3brc">Important JIRA tasks </a>but
+ let's briefly overview some valuable improvements.
</p>
- <h3>New Subsystem for Production Monitoring and Tracing</h3>
+ <h3 id="cache-dumps">Cache dumps</h3>
<p>
- Several months of constant work on <a href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=112820392" target="_blank">IEP-35: Monitoring & Profiling</a> has resulted in the creation of a robust and
- elastic subsystem for production monitoring and diagnostic (aka. profiling). This was influenced by the needs of many developers who deployed Ignite in critical environments and were asking for a foundation that can be
- integrated with many external monitoring tools and be expanded easily.
+ Ignite has persistent cache <a href="https://ignite.apache.org/docs/latest/snapshots/snapshots">snapshots </a>and this feature is highly appreciated by Ignite users. This release introduces another way to make a copy of
+ user data - a cache dump.
</p>
<p>
- The <a href="https://apacheignite.readme.io/docs/new-metrics#section-exporters" target="_blank">new subsystem</a> consists of several registries that group individual metrics related to a specific Ignite component. For
- instance, you will find registries for cache, compute, or service grid APIs. Since the registries are designed to be generic, specific exporters can observe the state of Ignite via a myriad of tools supporting various
- protocols. By default, Ignite 2.8 introduces exporters for monitoring interfaces such as log files, JMX and SQL views, and contemporary ones such as OpenCensus.
+ The cache dump is essentially a file that contains all entries of a cache group at the time of dump creation. Dump is consistent like a snapshot, which means all entries that existed in the cluster at the moment of dump
+ creation will be included in the dump file. Meta information of dumped caches and binary meta are also included in the dump.
</p>
+ <p>Main differences from cache snapshots:</p>
+ <ul>
+ <li>Supports in-memory caches that a snapshot feature does not support.</li>
+ <li>Takes up less disk space. The dump contains only the cache entries as-is.</li>
+ <li>Can be used for offline data processing.</li>
+ </ul>
</div>
- <div class="post__footer"><a class="more" href="/blog/ignite-2-8-released-less.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-16-0.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/apache-ignite-2-5-scaling.html">Apache Ignite 2.5: Scaling to 1000s Nodes Clusters</a></h2>
+ <h2><a href="/blog/apache-ignite-net-dynamic-linq.html">Dynamic LINQ performance and usability with Ignite.NET and System.Linq.Dynamic</a></h2>
<div>
- May 31, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-5-scaling.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite 2.5: Scaling to 1000s Nodes Clusters%20https://ignite.apache.org/blog/apache-ignite-2-5-scaling.html">Twitter</a>
+ May 22, 2023 by Pavel Tupitsyn. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-net-dynamic-linq.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Dynamic LINQ performance and usability with Ignite.NET and System.Linq.Dynamic%20https://ignite.apache.org/blog/apache-ignite-net-dynamic-linq.html">Twitter</a>
</div>
</div>
<div class="post__content">
- <p>
- Apache Ignite was always appreciated by its users for two primary things it delivers - scalability and performance. Throughout the lifetime many distributed systems tend to do performance optimizations from a release to
- release while making scalability related improvements just a couple of times. It's not because the scalability is of no interest. Usually, scalability requirements are set and solved once by a distributed system and
- don't require significant additional interventions by engineers.
- </p>
- <p>
- However, Apache Ignite grew to the point when the community decided to revisit its discovery subsystem that influences how well and far Ignite scales out. The goal was pretty clear - Ignite has to scale to 1000s of nodes
- as good as it scales to 100s now.
- </p>
- <p>
- It took many months to get the task implemented. So, please join me in welcoming Apache Ignite 2.5 that now can be scaled easily to 1000s of nodes and goes with other exciting capabilities. Let's check out the most
- prominent ones.
- </p>
+ <p>Dynamically building database queries can be necessary for some use cases, such as UI-defined filtering. This can get challenging with LINQ frameworks like EF Core and Ignite.NET.</p>
+ <p><a href="https://ptupitsyn.github.io/Dynamic-LINQ-With-Ignite/">Read More...</a></p>
</div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-5-scaling.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/apache-ignite-2-4-brings.html">Apache Ignite 2.4 ings Advanced Machine Learning and Spark DataFrames Capabilities</a></h2>
+ <h2><a href="/blog/apache-ignite-2-13-0.html">Apache Ignite 2.13.0: new Apache Calcite-based SQL engine</a></h2>
<div>
- March 15, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-4-brings.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite 2.4 ings Advanced Machine Learning and Spark DataFrames Capabilities%20https://ignite.apache.org/blog/apache-ignite-2-4-brings.html">Twitter</a>
+ April 28, 2022 by Nikita Amelchev. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-13-0.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.13.0: new Apache Calcite-based SQL engine%20https://ignite.apache.org/blog/apache-ignite-2-13-0.html">Twitter</a>
</div>
</div>
<div class="post__content">
<p>
- Usually, Ignite community rolls out a new version once in 3 months, but we had to make an exception for Apache Ignite 2.4 that consumed five months in total. We could easily blame Thanksgiving, Christmas and New Year
- holidays for the delay and would be forgiven, but, in fact, we were forging the release you can't simply pass by.
- </p>
- <p>Let's dive in and search for a big fish.</p>
- <h3>Machine Learning General Availability</h3>
- <p>
- Eight months ago, at the time of Apache Ignite 2.0, we put out the first APIs that formed the foundation of the Ignite's machine learning component of today. Since that time, Ignite machine learning experts and
- enthusiasts have been moving the liary to the general availability condition meticulously. And Ignite 2.4 became a milestone that let us consider the
- <a href="https://apacheignite.readme.io/docs/machine-learning" target="_blank">ML Grid</a> to be production ready.
+ As of April 26, 2022, <a href="https://ignite.apache.org/">Apache Ignite</a> 2.13 has been released. You can directly check the full list of resolved <a href="https://s.apache.org/x8u49">Important JIRA tasks</a> but here
+ let's briefly overview some valuable improvements.
</p>
+ <h4>This is a breaking change release: The legacy service grid implementation was removed.</h4>
+ <h3 id="new-apache-calcite-based-sql-engine">New Apache Calcite-based SQL engine</h3>
+ <p>We've implemented a new experimental SQL engine based on Apache Calcite. Now it's possible to:</p>
+ <ul>
+ <li>Get rid of some <a href="https://cwiki.apache.org/confluence/display/IGNITE/IEP-37%3A+New+query+execution+engine#IEP37:Newqueryexecutionengine-Motivation">H2 limitations</a>;</li>
+ <li><a href="https://cwiki.apache.org/confluence/display/IGNITE/IEP-37%3A+New+query+execution+engine#IEP37:Newqueryexecutionengine-Implementationdetails">Optimize</a> some query execution.</li>
+ </ul>
+ <p>The current H2-based engine has fundamental limitations. For example:</p>
+ <ul>
+ <li>some queries should be splitted into 2 phases (map subquery and reduce subquery), but some of them cannot be effectively executed in 2 phases.</li>
+ <li>H2 is a third-party database product with not-ASF license.</li>
+ <li>The optimizer and other internal things are not supposed to work in a distributed environment.</li>
+ <li>It's hard to make Ignite-specific changes to the H2 code, patches are often declined.</li>
+ </ul>
</div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-4-brings.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-13-0.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/meltdown-and-spectre-patches-show.html">Meltdown and Spectre patches show negligible impact to Apache Ignite performance</a></h2>
+ <h2><a href="/blog/apache-ignite-2-12-0.html">Apache Ignite 2.12.0: CDC, Index Query API, Vulnerabilities Fixes</a></h2>
<div>
- January 30, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/meltdown-and-spectre-patches-show.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Meltdown and Spectre patches show negligible impact to Apache Ignite performance%20https://ignite.apache.org/blog/meltdown-and-spectre-patches-show.html">Twitter</a>
+ January 14, 2022 by Nikita Amelchev. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-12-0.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.12.0: CDC, Index Query API, Vulnerabilities Fixes%20https://ignite.apache.org/blog/apache-ignite-2-12-0.html">Twitter</a>
</div>
</div>
<div class="post__content">
<p>
- As promised in my <a href="https://blogs.apache.org/ignite/entry/protecting-apache-ignite-from-meltdown">initial blog post</a> on this matter, Apache Ignite community applied security patches against the
- notorious Meltdown Spectre vulnerabilities and completed performance testing of general operations and workloads that are typical for Ignite deployments.
+ As of January 14, 2022, <a href="https://ignite.apache.org/">Apache Ignite</a> 2.12 has been released. You can directly check the full list of resolved <a href="https://s.apache.org/0zyi2">Important JIRA tasks</a> but here
+ let’s briefly overview some valuable improvements.
+ </p>
+ <h3 id="vulnerability-updates">Vulnerability Updates</h3>
+ <p>
+ The Apache Ignite versions lower than 2.11.1 are vulnerable to <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44832">CVE-2021-44832</a> which is related to the <code>ignite-log4j2</code> module usage.
</p>
+ <p>The release also fixes 10+ CVE’s of various modules. See <a href="https://ignite.apache.org/releases/ignite2/2.12.0/release_notes.html">release notes</a> for more details.</p>
+ <h3 id="change-data-capture">Change Data Capture</h3>
<p>
- The security patches were applied only for <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5754" target="_blank">CVE-2017-5754</a> (Meltdown) and <a
- href="https://nvd.nist.gov/vuln/detail/CVE-2017-5753"
- target="_blank"
- >CVE-2017-5753</a
- > (Spectre Variant 1) vulnerabilities. The patches for <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5715" target="_blank">CVE-2017-5715</a> (Spectre Variant 2) for the hardware the community used for
- testing are not stable yet an can
- <a href="https://newsroom.intel.com/news/root-cause-of-reboot-issue-identified-updated-guidance-for-customers-and-partners/" target="_blank">cause system reboot issues or another unpredictable behavior</a>.
+ Change Data Capture (<a href="https://en.wikipedia.org/wiki/Change_data_capture">CDC</a>) is a data processing pattern used to asynchronously receive entries that have been changed on the local node so that action can be
+ taken using the changed entry.
</p>
- <p>The applied patches have shown that the performance implications are negligible - the performance drop is just in the 0 - 7% range as the figure shows:</p>
</div>
- <div class="post__footer"><a class="more" href="/blog/meltdown-and-spectre-patches-show.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-12-0.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/protecting-apache-ignite-from-meltdown.html">Protecting Apache Ignite from 'Meltdown' and 'Spectre' vulnerabilities</a></h2>
+ <h2><a href="/blog/apache-ignite-2-11-1.html">Apache Ignite 2.11.1: Emergency Log4j2 Update</a></h2>
<div>
- January 8, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/protecting-apache-ignite-from-meltdown.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Protecting Apache Ignite from 'Meltdown' and 'Spectre' vulnerabilities%20https://ignite.apache.org/blog/protecting-apache-ignite-from-meltdown.html">Twitter</a>
+ December 21, 2021 by Maxim Muzafarov. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-11-1.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.11.1: Emergency Log4j2 Update%20https://ignite.apache.org/blog/apache-ignite-2-11-1.html">Twitter</a>
</div>
</div>
<div class="post__content">
<p>
- The world was rocked after the recent disclosure of the
- <a href="https://www.vox.com/business-and-finance/2018/1/4/16850004/meltdown-spectre-intel-security-flaw-update" target="_blank">Meltdown and Spectre</a> vulnerabilities that literally affect almost all software ever
- developed. Both issues are related to the way all modern CPUs are designed and this is why they have opened unprecedented security breaches -- making the software, including Apache Ignite, vulnerable to
- hacker attacks.
+ The new <a href="https://ignite.apache.org/">Apache Ignite</a> 2.11.1 is an emergency release that fixes <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228">CVE-2021-44228</a>,
+ <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45046">CVE-2021-45046</a>,<a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45105">CVE-2021-45105</a> related to the ignite-log4j2 module
+ usage.
</p>
- <p>The vulnerabilities are registered in the National Vulnerability Database under the following CVEs:</p>
+ <h3 id="apache-ignite-with-log4j-vulnerability">Apache Ignite with Log4j Vulnerability</h3>
+ <p>All the following conditions must be met:</p>
<ul>
- <li><a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5753" target="_blank">CVE-2017-5753</a> — Spectre variant 1</li>
- <li><a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5715" target="_blank">CVE-2017-5715</a> — Spectre variant 2</li>
- <li><a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5754" target="_blank">CVE-2017-5754</a> — Meltdown</li>
+ <li>The Apache Ignite version lower than 2.11.0 is used (since these vulnerabilities are already fixed in 2.11.1, 2.12, and upper versions);</li>
+ <li>The <code>ignite-logj42</code> is used by Apache Ignite and located in the <code>libs</code> directory (by default it is located in the <code>libs/optional</code>directory, so these deployments are not affected);</li>
+ <li>
+ The Java version in use is older than the following versions: <code>8u191</code>, <code>11.0.1</code>. This is due to the fact that later versions set the JVM property
+ <code>com.sun.jndi.ldap.object.trustURLCodebase</code> to <code>false</code> by default, which disables JNDI loading of classes from arbitrary URL code bases.
+ </li>
</ul>
+ <p>NOTE: Relying only on the Java version as a protection against these vulnerabilities is very risky and has not been tested.</p>
</div>
- <div class="post__footer"><a class="more" href="/blog/protecting-apache-ignite-from-meltdown.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-11-1.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/apache-ignite-essentials-series-for.html">Apache Ignite Essentials: 2-part Webinar Series for Architects and Java Developers</a></h2>
+ <h2><a href="/blog/apache-ignite-2-11-stabilization.html">Apache Ignite 2.11: Stabilization First</a></h2>
<div>
- November 17, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-essentials-series-for.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite Essentials: 2-part Webinar Series for Architects and Java Developers%20https://ignite.apache.org/blog/apache-ignite-essentials-series-for.html">Twitter</a>
+ September 20, 2021 by Maxim Muzafarov. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-11-stabilization.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.11: Stabilization First%20https://ignite.apache.org/blog/apache-ignite-2-11-stabilization.html">Twitter</a>
</div>
</div>
<div class="post__content">
- <p class="entryContent">
- We finally made this happen! I’m happy to invite all of the software architects and engineers out there to a series of webinars that will introduce you to the fundamental capabilities of in-memory computing platforms
- such as Apache Ignite.
+ <p>
+ The new <a href="https://ignite.apache.org/">Apache Ignite</a> 2.11 was released on September 17, 2021. It can be considered to be a greater extent as a stabilization release that closed a number of technical debts of the
+ internal architecture and bugs. Out of more than 200 completed tasks, 120 are bug fixes. However, some valuable improvements still exist, so let's take a quick look at them together.
+ </p>
+ <h3 id="thin-clients">Thin Clients</h3>
+ <p>
+ Partition awareness is enabled by default in the 2.11 release and allows thin clients to send query requests directly to the node that owns the queried data. Without partition awareness, an application executes all queries
+ and operations via a single server node that acts as a proxy for the incoming requests.
+ </p>
+ <p>
+ The support of <a href="https://ignite.apache.org/docs/latest/thin-clients/java-thin-client#cache-entry-listening">Continuous Queries</a>added to the java thin client. For the other supported features, you can check - the
+ <a href="https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features">List of Thin Client Features</a>.
</p>
- <p>There will also be a mix of theory and practice. A lot of code examples are waiting to be shown so that you can apply the theory in practice right away.</p>
- <p>The series consists of two parts.</p>
- <h3><a href="https://ignite.apache.org/events.html#in-memory-computing-essentials-architects-and-developers-part-1" target="_blank">Part 1: Tuesday, November 21, 2017, 11:00am PT / 2:00pm ET</a></h3>
- To be covered:
- <ul>
- <li>Cluster configuration and deployment.</li>
- <li>Distributed database internals (partitioning, replication).</li>
- <li>Data processing with key-value APIs.</li>
- <li>Affinity Collocation.</li>
- <li>Data processing with SQL.</li>
- </ul>
</div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-essentials-series-for.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-11-stabilization.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/apache-ignite-2-3-more.html">Apache Ignite 2.3 - More SQL and Persistence Capabilities</a></h2>
+ <h2><a href="/blog/apache-ignite-momentum-highlights-from.html">Apache Ignite Momentum: Highlights from 2020-2021</a></h2>
<div>
- November 1, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-3-more.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite 2.3 - More SQL and Persistence Capabilities%20https://ignite.apache.org/blog/apache-ignite-2-3-more.html">Twitter</a>
+ September 14, 2021 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-momentum-highlights-from.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite Momentum: Highlights from 2020-2021%20https://ignite.apache.org/blog/apache-ignite-momentum-highlights-from.html">Twitter</a>
</div>
</div>
<div class="post__content">
- <p>Putting aside the regular bug fixes and performance optimizations, the Apache Ignite 2.3 release brings new SQL capabilities and Ignite persistence improvements that are worth mentioning.</p>
+ <p>
+ When Apache Ignite entered the Apache Software Foundation (ASF) Incubator in 2014, it took less than a year for the project and its community to graduate from the Incubator and become a top-level project for the ASF. Since
+ then, Ignite has experienced a significant and steady growth in popularity, and it has been used by thousands of application developers and architects to create high-performance and scalable applications used by millions
+ of people daily. In this article, we’ll recap the achievements of Ignite in 2020-2021.
+ </p>
<p></p>
- <h3>SQL</h3>
+ <h3><br />Ignite is Ranked as a Top 5 Project<br /></h3>
<p></p>
- <p>Let's start with SQL first.</p>
- <p>Apache Ignite users have consistently told us that despite all of Ignite’s SQL capabilities, it’s been at times challenging trying to figure out how to start using Ignite as an SQL database.</p>
<p>
- This was mostly caused by scattered documentation pages, lack of “getting started” guides and tutorials. We’ve remedied this oversight! All related SQL knowledge has been curated in a
- <a href="https://apacheignite-sql.readme.io/docs" target="_blank">single documentation domain</a>.
+ The ASF has ranked Apache ignite as a Top 5 project in various categories since 2017. <a href="https://blogs.apache.org/foundation/entry/apache-in-2017-by-the" target="_blank">That year</a>, Ignite was in the Top 5 of
+ Apache Project Repositories by Commits and most active Apache mailing lists. <a href="https://www.apache.org/foundation/docs/FY2021AnnualReport.pdf" target="_blank">Today</a>, the momentum continues, and Ignite continues
+ to be ranked as a Top 5 project in multiple categories: second on the Top 5 big data user lists, third on the Top 5 big data dev lists, second on the Top 5 of all user lists, third on the Top 5 repos by size.
+ </p>
+ <p>
+ <a href="/img/blog/463ae37d-866d-4c15-8ebf-6b88499daa81.jpeg"><img src="/img/blog/463ae37d-866d-4c15-8ebf-6b88499daa81.jpeg" width="30%" /></a>
</p>
</div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-3-more.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-momentum-highlights-from.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/apache-ignite-community-news-september.html">Apache Ignite Community News (Issue 3)</a></h2>
+ <h2><a href="/blog/apache-ignite-2-10-thin.html">Apache Ignite 2.10: Thin Client Expansion</a></h2>
<div>
- September 15, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-community-news-september.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite Community News (Issue 3)%20https://ignite.apache.org/blog/apache-ignite-community-news-september.html">Twitter</a>
+ March 18, 2021 by Maxim Muzafarov. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-10-thin.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.10: Thin Client Expansion%20https://ignite.apache.org/blog/apache-ignite-2-10-thin.html">Twitter</a>
</div>
</div>
<div class="post__content">
- <p><b>by Tom Diederich</b></p>
- <p>This is our third community update – there’s a lot going on, so let's get started.</p>
- <p>Apache Ignite experts have already spoken at two meetups this month, both in Silicon Valley, but there are several more scheduled this month around the world.</p>
- <p></p>
- <p style="margin-bottom: 15pt">
- <span style="line-height: 19.5pt"
- ><span style="font-family: Helvetica"
- ><span style="color: #333333"
- >On <b>Sept. 9</b> Apache Ignite PMC chair Denis Magda was the featured presenter at the<b> </b
- ><a href="https://www.meetup.com/datariders/events/242523245/"
- ><b><span style="color: #467d76">Big Data and Cloud Meetup</span></b></a
- >
- in Santa Clara, Calif. His talk, titled "Apache Spark and Apache Ignite: Where Fast Data Meets the IoT," was highly rated and we’re planning a hands-on workshop with meetup organizers for
- November.</span
- ></span
- ></span
- >
+ <p class="entryContent">
+ As of March 15, 2021, <a href="https://ignite.apache.org/">Apache Ignite</a> 2.10 has been released. You can directly check the full list of resolved <a href="https://s.apache.org/i3ny6">Important JIRA's</a> but here
+ let’s briefly overview some valuable improvements.
</p>
+ <h3 id="thin-clients">Thin Clients</h3>
+ Thin clients now support several important features which, previously were available only on the thick clients. Thin clients are always backward and forward compatible with the server nodes of the cluster, so the cluster
+ upgrade process will be more convenient if the lack of these features prevented you from doing that.
+ <p>See the list of what is changed for thin clients below:</p>
+ <ul>
+ <li>Transactions</li>
+ <li>Service invocations</li>
+ <li>Continuous Queries</li>
+ <li>SQL API</li>
+ <li>Cluster API</li>
+ <li>Cache Async API</li>
+ <li>Kubernetes Discovery (<em>ThinClientKubernetesAddressFinder</em>)</li>
+ </ul>
+ You may check the <a href="https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features">List of Thin Client Features</a> that supported by platforms you are interested in or see the
+ <a href="https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-2.10/">What's new in Apache Ignite.NET 2.10</a>.
</div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-community-news-september.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-10-thin.html">↓ Read all</a></div>
</article>
<article class="post">
<div class="post__header">
- <h2><a href="/blog/apache-ignite-community-update-august.html">Apache Ignite Community Update (August 2017 Issue)</a></h2>
+ <h2><a href="/blog/ignite-2-8-released-less.html">Ignite 2.8 Released: Less Stress in Production and Advances in Machine Learning</a></h2>
<div>
- August 30, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-community-update-august.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Apache Ignite Community Update (August 2017 Issue)%20https://ignite.apache.org/blog/apache-ignite-community-update-august.html">Twitter</a>
+ March 11, 2020 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/ignite-2-8-released-less.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Ignite 2.8 Released: Less Stress in Production and Advances in Machine Learning%20https://ignite.apache.org/blog/ignite-2-8-released-less.html">Twitter</a>
</div>
</div>
<div class="post__content">
<p>
- <b><i>by Tom Diederich</i></b>
+ With thousands of changes contributed to Apache Ignite 2.8 that enhanced almost all the components of the platform, it’s possible to overlook some of the improvements that can convince you to upgrade to this version
+ sooner than later. While a quick check of the <a href="https://ignite.apache.org/releases/ignite2/2.8.0/release_notes.html" target="_blank">release notes</a> will help to discover anticipated bug fixes, this article aims
+ to guide through enhancements every Ignite developer should be aware of.
</p>
+ <h3>New Subsystem for Production Monitoring and Tracing</h3>
<p>
- Igniters, here are some community highlights from the last couple week. If I missed anything, please share it here. Meetups! Did you know that Apache Ignite experts are available to speak at your meetup? And we also have
- spots open for YOU to speak at the following meetups that some of us co-organize:
+ Several months of constant work on <a href="https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=112820392" target="_blank">IEP-35: Monitoring & Profiling</a> has resulted in the creation of a robust and
+ elastic subsystem for production monitoring and diagnostic (aka. profiling). This was influenced by the needs of many developers who deployed Ignite in critical environments and were asking for a foundation that can be
+ integrated with many external monitoring tools and be expanded easily.
+ </p>
+ <p>
+ The <a href="https://apacheignite.readme.io/docs/new-metrics#section-exporters" target="_blank">new subsystem</a> consists of several registries that group individual metrics related to a specific Ignite component. For
+ instance, you will find registries for cache, compute, or service grid APIs. Since the registries are designed to be generic, specific exporters can observe the state of Ignite via a myriad of tools supporting various
+ protocols. By default, Ignite 2.8 introduces exporters for monitoring interfaces such as log files, JMX and SQL views, and contemporary ones such as OpenCensus.
</p>
- <ul>
- <li><a href="https://www.meetup.com/Apache-Ignite-London/" target="_blank">Apache Ignite London</a></li>
- <li><a href="https://www.meetup.com/Bay-Area-In-Memory-Computing/" target="_blank">Bay Area In-Memory Computing Meetup</a></li>
- <li><a href="https://www.meetup.com/NYC-In-Memory-Computing-Meetup/" target="_blank">NYC In-Memory Computing Meetup</a></li>
- <li><a href="https://www.meetup.com/Moscow-Apache-Ignite-Meetup/" target="_blank">Moscow Apache Ignite Meetup</a></li>
- </ul>
</div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-community-update-august.html">↓ Read all</a></div>
+ <div class="post__footer"><a class="more" href="/blog/ignite-2-8-released-less.html">↓ Read all</a></div>
</article>
</section>
<section class="blog__footer">
@@ -713,6 +705,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/ignite/2/index.html b/blog/ignite/2/index.html
index 9f8f5049d9..88abddd870 100644
--- a/blog/ignite/2/index.html
+++ b/blog/ignite/2/index.html
@@ -341,6 +341,208 @@
<div class="blog__content">
<main class="blog_main">
<section class="blog__posts">
+ <article class="post">
+ <div class="post__header">
+ <h2><a href="/blog/apache-ignite-2-5-scaling.html">Apache Ignite 2.5: Scaling to 1000s Nodes Clusters</a></h2>
+ <div>
+ May 31, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-5-scaling.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.5: Scaling to 1000s Nodes Clusters%20https://ignite.apache.org/blog/apache-ignite-2-5-scaling.html">Twitter</a>
+ </div>
+ </div>
+ <div class="post__content">
+ <p>
+ Apache Ignite was always appreciated by its users for two primary things it delivers - scalability and performance. Throughout the lifetime many distributed systems tend to do performance optimizations from a release to
+ release while making scalability related improvements just a couple of times. It's not because the scalability is of no interest. Usually, scalability requirements are set and solved once by a distributed system and
+ don't require significant additional interventions by engineers.
+ </p>
+ <p>
+ However, Apache Ignite grew to the point when the community decided to revisit its discovery subsystem that influences how well and far Ignite scales out. The goal was pretty clear - Ignite has to scale to 1000s of nodes
+ as good as it scales to 100s now.
+ </p>
+ <p>
+ It took many months to get the task implemented. So, please join me in welcoming Apache Ignite 2.5 that now can be scaled easily to 1000s of nodes and goes with other exciting capabilities. Let's check out the most
+ prominent ones.
+ </p>
+ </div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-5-scaling.html">↓ Read all</a></div>
+ </article>
+ <article class="post">
+ <div class="post__header">
+ <h2><a href="/blog/apache-ignite-2-4-brings.html">Apache Ignite 2.4 ings Advanced Machine Learning and Spark DataFrames Capabilities</a></h2>
+ <div>
+ March 15, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-4-brings.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.4 ings Advanced Machine Learning and Spark DataFrames Capabilities%20https://ignite.apache.org/blog/apache-ignite-2-4-brings.html">Twitter</a>
+ </div>
+ </div>
+ <div class="post__content">
+ <p>
+ Usually, Ignite community rolls out a new version once in 3 months, but we had to make an exception for Apache Ignite 2.4 that consumed five months in total. We could easily blame Thanksgiving, Christmas and New Year
+ holidays for the delay and would be forgiven, but, in fact, we were forging the release you can't simply pass by.
+ </p>
+ <p>Let's dive in and search for a big fish.</p>
+ <h3>Machine Learning General Availability</h3>
+ <p>
+ Eight months ago, at the time of Apache Ignite 2.0, we put out the first APIs that formed the foundation of the Ignite's machine learning component of today. Since that time, Ignite machine learning experts and
+ enthusiasts have been moving the liary to the general availability condition meticulously. And Ignite 2.4 became a milestone that let us consider the
+ <a href="https://apacheignite.readme.io/docs/machine-learning" target="_blank">ML Grid</a> to be production ready.
+ </p>
+ </div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-4-brings.html">↓ Read all</a></div>
+ </article>
+ <article class="post">
+ <div class="post__header">
+ <h2><a href="/blog/meltdown-and-spectre-patches-show.html">Meltdown and Spectre patches show negligible impact to Apache Ignite performance</a></h2>
+ <div>
+ January 30, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/meltdown-and-spectre-patches-show.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Meltdown and Spectre patches show negligible impact to Apache Ignite performance%20https://ignite.apache.org/blog/meltdown-and-spectre-patches-show.html">Twitter</a>
+ </div>
+ </div>
+ <div class="post__content">
+ <p>
+ As promised in my <a href="https://blogs.apache.org/ignite/entry/protecting-apache-ignite-from-meltdown">initial blog post</a> on this matter, Apache Ignite community applied security patches against the
+ notorious Meltdown Spectre vulnerabilities and completed performance testing of general operations and workloads that are typical for Ignite deployments.
+ </p>
+ <p>
+ The security patches were applied only for <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5754" target="_blank">CVE-2017-5754</a> (Meltdown) and <a
+ href="https://nvd.nist.gov/vuln/detail/CVE-2017-5753"
+ target="_blank"
+ >CVE-2017-5753</a
+ > (Spectre Variant 1) vulnerabilities. The patches for <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5715" target="_blank">CVE-2017-5715</a> (Spectre Variant 2) for the hardware the community used for
+ testing are not stable yet an can
+ <a href="https://newsroom.intel.com/news/root-cause-of-reboot-issue-identified-updated-guidance-for-customers-and-partners/" target="_blank">cause system reboot issues or another unpredictable behavior</a>.
+ </p>
+ <p>The applied patches have shown that the performance implications are negligible - the performance drop is just in the 0 - 7% range as the figure shows:</p>
+ </div>
+ <div class="post__footer"><a class="more" href="/blog/meltdown-and-spectre-patches-show.html">↓ Read all</a></div>
+ </article>
+ <article class="post">
+ <div class="post__header">
+ <h2><a href="/blog/protecting-apache-ignite-from-meltdown.html">Protecting Apache Ignite from 'Meltdown' and 'Spectre' vulnerabilities</a></h2>
+ <div>
+ January 8, 2018 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/protecting-apache-ignite-from-meltdown.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Protecting Apache Ignite from 'Meltdown' and 'Spectre' vulnerabilities%20https://ignite.apache.org/blog/protecting-apache-ignite-from-meltdown.html">Twitter</a>
+ </div>
+ </div>
+ <div class="post__content">
+ <p>
+ The world was rocked after the recent disclosure of the
+ <a href="https://www.vox.com/business-and-finance/2018/1/4/16850004/meltdown-spectre-intel-security-flaw-update" target="_blank">Meltdown and Spectre</a> vulnerabilities that literally affect almost all software ever
+ developed. Both issues are related to the way all modern CPUs are designed and this is why they have opened unprecedented security breaches -- making the software, including Apache Ignite, vulnerable to
+ hacker attacks.
+ </p>
+ <p>The vulnerabilities are registered in the National Vulnerability Database under the following CVEs:</p>
+ <ul>
+ <li><a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5753" target="_blank">CVE-2017-5753</a> — Spectre variant 1</li>
+ <li><a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5715" target="_blank">CVE-2017-5715</a> — Spectre variant 2</li>
+ <li><a href="https://nvd.nist.gov/vuln/detail/CVE-2017-5754" target="_blank">CVE-2017-5754</a> — Meltdown</li>
+ </ul>
+ </div>
+ <div class="post__footer"><a class="more" href="/blog/protecting-apache-ignite-from-meltdown.html">↓ Read all</a></div>
+ </article>
+ <article class="post">
+ <div class="post__header">
+ <h2><a href="/blog/apache-ignite-essentials-series-for.html">Apache Ignite Essentials: 2-part Webinar Series for Architects and Java Developers</a></h2>
+ <div>
+ November 17, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-essentials-series-for.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite Essentials: 2-part Webinar Series for Architects and Java Developers%20https://ignite.apache.org/blog/apache-ignite-essentials-series-for.html">Twitter</a>
+ </div>
+ </div>
+ <div class="post__content">
+ <p class="entryContent">
+ We finally made this happen! I’m happy to invite all of the software architects and engineers out there to a series of webinars that will introduce you to the fundamental capabilities of in-memory computing platforms
+ such as Apache Ignite.
+ </p>
+ <p>There will also be a mix of theory and practice. A lot of code examples are waiting to be shown so that you can apply the theory in practice right away.</p>
+ <p>The series consists of two parts.</p>
+ <h3><a href="https://ignite.apache.org/events.html#in-memory-computing-essentials-architects-and-developers-part-1" target="_blank">Part 1: Tuesday, November 21, 2017, 11:00am PT / 2:00pm ET</a></h3>
+ To be covered:
+ <ul>
+ <li>Cluster configuration and deployment.</li>
+ <li>Distributed database internals (partitioning, replication).</li>
+ <li>Data processing with key-value APIs.</li>
+ <li>Affinity Collocation.</li>
+ <li>Data processing with SQL.</li>
+ </ul>
+ </div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-essentials-series-for.html">↓ Read all</a></div>
+ </article>
+ <article class="post">
+ <div class="post__header">
+ <h2><a href="/blog/apache-ignite-2-3-more.html">Apache Ignite 2.3 - More SQL and Persistence Capabilities</a></h2>
+ <div>
+ November 1, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-2-3-more.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite 2.3 - More SQL and Persistence Capabilities%20https://ignite.apache.org/blog/apache-ignite-2-3-more.html">Twitter</a>
+ </div>
+ </div>
+ <div class="post__content">
+ <p>Putting aside the regular bug fixes and performance optimizations, the Apache Ignite 2.3 release brings new SQL capabilities and Ignite persistence improvements that are worth mentioning.</p>
+ <p></p>
+ <h3>SQL</h3>
+ <p></p>
+ <p>Let's start with SQL first.</p>
+ <p>Apache Ignite users have consistently told us that despite all of Ignite’s SQL capabilities, it’s been at times challenging trying to figure out how to start using Ignite as an SQL database.</p>
+ <p>
+ This was mostly caused by scattered documentation pages, lack of “getting started” guides and tutorials. We’ve remedied this oversight! All related SQL knowledge has been curated in a
+ <a href="https://apacheignite-sql.readme.io/docs" target="_blank">single documentation domain</a>.
+ </p>
+ </div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-2-3-more.html">↓ Read all</a></div>
+ </article>
+ <article class="post">
+ <div class="post__header">
+ <h2><a href="/blog/apache-ignite-community-news-september.html">Apache Ignite Community News (Issue 3)</a></h2>
+ <div>
+ September 15, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-community-news-september.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite Community News (Issue 3)%20https://ignite.apache.org/blog/apache-ignite-community-news-september.html">Twitter</a>
+ </div>
+ </div>
+ <div class="post__content">
+ <p><b>by Tom Diederich</b></p>
+ <p>This is our third community update – there’s a lot going on, so let's get started.</p>
+ <p>Apache Ignite experts have already spoken at two meetups this month, both in Silicon Valley, but there are several more scheduled this month around the world.</p>
+ <p></p>
+ <p style="margin-bottom: 15pt">
+ <span style="line-height: 19.5pt"
+ ><span style="font-family: Helvetica"
+ ><span style="color: #333333"
+ >On <b>Sept. 9</b> Apache Ignite PMC chair Denis Magda was the featured presenter at the<b> </b
+ ><a href="https://www.meetup.com/datariders/events/242523245/"
+ ><b><span style="color: #467d76">Big Data and Cloud Meetup</span></b></a
+ >
+ in Santa Clara, Calif. His talk, titled "Apache Spark and Apache Ignite: Where Fast Data Meets the IoT," was highly rated and we’re planning a hands-on workshop with meetup organizers for
+ November.</span
+ ></span
+ ></span
+ >
+ </p>
+ </div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-community-news-september.html">↓ Read all</a></div>
+ </article>
+ <article class="post">
+ <div class="post__header">
+ <h2><a href="/blog/apache-ignite-community-update-august.html">Apache Ignite Community Update (August 2017 Issue)</a></h2>
+ <div>
+ August 30, 2017 by Denis Magda. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-community-update-august.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=Apache Ignite Community Update (August 2017 Issue)%20https://ignite.apache.org/blog/apache-ignite-community-update-august.html">Twitter</a>
+ </div>
+ </div>
+ <div class="post__content">
+ <p>
+ <b><i>by Tom Diederich</i></b>
+ </p>
+ <p>
+ Igniters, here are some community highlights from the last couple week. If I missed anything, please share it here. Meetups! Did you know that Apache Ignite experts are available to speak at your meetup? And we also have
+ spots open for YOU to speak at the following meetups that some of us co-organize:
+ </p>
+ <ul>
+ <li><a href="https://www.meetup.com/Apache-Ignite-London/" target="_blank">Apache Ignite London</a></li>
+ <li><a href="https://www.meetup.com/Bay-Area-In-Memory-Computing/" target="_blank">Bay Area In-Memory Computing Meetup</a></li>
+ <li><a href="https://www.meetup.com/NYC-In-Memory-Computing-Meetup/" target="_blank">NYC In-Memory Computing Meetup</a></li>
+ <li><a href="https://www.meetup.com/Moscow-Apache-Ignite-Meetup/" target="_blank">Moscow Apache Ignite Meetup</a></li>
+ </ul>
+ </div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-community-update-august.html">↓ Read all</a></div>
+ </article>
<article class="post">
<div class="post__header">
<h2><a href="/blog/apache-ignite-2-1-a.html">Apache Ignite 2.1 - A Leap from In-Memory to Memory-Centric Architecture</a></h2>
@@ -493,6 +695,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/ignite/index.html b/blog/ignite/index.html
index 2ef5035245..8a0ecdf95c 100644
--- a/blog/ignite/index.html
+++ b/blog/ignite/index.html
@@ -494,19 +494,6 @@
</div>
<div class="post__footer"><a class="more" href="/blog/apache-ignite-2-17-0.html">↓ Read all</a></div>
</article>
- <article class="post">
- <div class="post__header">
- <h2><a href="/blog/apache-ignite-net-intel-cet-fix.html">Ignite on .NET 9 and Intel CET</a></h2>
- <div>
- November 22, 2024 by Pavel Tupitsyn. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-net-intel-cet-fix.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Ignite on .NET 9 and Intel CET%20https://ignite.apache.org/blog/apache-ignite-net-intel-cet-fix.html">Twitter</a>
- </div>
- </div>
- <div class="post__content">
- <p>Old JDK code meets new Intel security feature, JVM + CLR in one process, and a mysterious crash.</p>
- <p><a href="https://ptupitsyn.github.io/Ignite-on-NET-9/">Read More...</a></p>
- </div>
- </article>
</section>
<section class="blog__footer">
<ul class="pagination">
diff --git a/blog/imdb/index.html b/blog/imdb/index.html
index 04a6a9fa9b..ca39761601 100644
--- a/blog/imdb/index.html
+++ b/blog/imdb/index.html
@@ -463,6 +463,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/in-memory/index.html b/blog/in-memory/index.html
index 184022bd15..53d03e1fb6 100644
--- a/blog/in-memory/index.html
+++ b/blog/in-memory/index.html
@@ -581,6 +581,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/in/index.html b/blog/in/index.html
index d9d81ac2a2..f7eec24cec 100644
--- a/blog/in/index.html
+++ b/blog/in/index.html
@@ -523,6 +523,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/index.html b/blog/index.html
index 5f720d7cae..15eef6d914 100644
--- a/blog/index.html
+++ b/blog/index.html
@@ -341,17 +341,6 @@
<div class="blog__content">
<main class="blog_main">
<section class="blog__posts">
- <article class="post">
- <div class="post__header">
- <h2><a href="/blog/apache-ignite-3-client-connections-handling.html">How many client connections can Apache Ignite 3 handle?</a></h2>
- <div>
- December 10, 2025 by Pavel Tupitsyn. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-3-client-connections-handling.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=How many client connections can Apache Ignite 3 handle?%20https://ignite.apache.org/blog/apache-ignite-3-client-connections-handling.html">Twitter</a>
- </div>
- </div>
- <div class="post__content"><p>Apache Ignite 3 manages client connections so efficiently that the scaling limits common in database-style systems simply aren’t a factor.</p></div>
- <div class="post__footer"><a class="more" href="/blog/apache-ignite-3-client-connections-handling.html">↓ Read all</a></div>
- </article>
<article class="post">
<div class="post__header">
<h2><a href="/blog/apache-ignite-3-architecture-part-4.html">Apache Ignite Architecture Series: Part 4 - Integrated Platform Performance: Maintaining Speed Under Pressure</a></h2>
@@ -368,6 +357,17 @@
</div>
<div class="post__footer"><a class="more" href="/blog/apache-ignite-3-architecture-part-4.html">↓ Read all</a></div>
</article>
+ <article class="post">
+ <div class="post__header">
+ <h2><a href="/blog/apache-ignite-3-client-connections-handling.html">How many client connections can Apache Ignite 3 handle?</a></h2>
+ <div>
+ December 10, 2025 by Pavel Tupitsyn. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-3-client-connections-handling.html">Facebook</a><span>, </span
+ ><a href="http://twitter.com/home?status=How many client connections can Apache Ignite 3 handle?%20https://ignite.apache.org/blog/apache-ignite-3-client-connections-handling.html">Twitter</a>
+ </div>
+ </div>
+ <div class="post__content"><p>Apache Ignite 3 manages client connections so efficiently that the scaling limits common in database-style systems simply aren’t a factor.</p></div>
+ <div class="post__footer"><a class="more" href="/blog/apache-ignite-3-client-connections-handling.html">↓ Read all</a></div>
+ </article>
<article class="post">
<div class="post__header">
<h2><a href="/blog/apache-ignite-3-architecture-part-3.html">Apache Ignite Architecture Series: Part 3 - Schema Evolution Under Operational Pressure: When Downtime Isn't an Option</a></h2>
@@ -494,19 +494,6 @@
</div>
<div class="post__footer"><a class="more" href="/blog/apache-ignite-2-17-0.html">↓ Read all</a></div>
</article>
- <article class="post">
- <div class="post__header">
- <h2><a href="/blog/apache-ignite-net-intel-cet-fix.html">Ignite on .NET 9 and Intel CET</a></h2>
- <div>
- November 22, 2024 by Pavel Tupitsyn. Share in <a href="http://www.facebook.com/sharer.php?u=https://ignite.apache.org/blog/apache-ignite-net-intel-cet-fix.html">Facebook</a><span>, </span
- ><a href="http://twitter.com/home?status=Ignite on .NET 9 and Intel CET%20https://ignite.apache.org/blog/apache-ignite-net-intel-cet-fix.html">Twitter</a>
- </div>
- </div>
- <div class="post__content">
- <p>Old JDK code meets new Intel security feature, JVM + CLR in one process, and a mysterious crash.</p>
- <p><a href="https://ptupitsyn.github.io/Ignite-on-NET-9/">Read More...</a></p>
- </div>
- </article>
</section>
<section class="blog__footer">
<ul class="pagination">
diff --git a/blog/key-value/index.html b/blog/key-value/index.html
index 42a401e4de..a8754c7b30 100644
--- a/blog/key-value/index.html
+++ b/blog/key-value/index.html
@@ -468,6 +468,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/learning/index.html b/blog/learning/index.html
index 56b5c1ab5b..78dba7b9b9 100644
--- a/blog/learning/index.html
+++ b/blog/learning/index.html
@@ -514,6 +514,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/linq/index.html b/blog/linq/index.html
index 880b6777d9..3fbb92e50f 100644
--- a/blog/linq/index.html
+++ b/blog/linq/index.html
@@ -459,6 +459,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/log4j2/index.html b/blog/log4j2/index.html
index 2109038bb5..78eadf0d0d 100644
--- a/blog/log4j2/index.html
+++ b/blog/log4j2/index.html
@@ -474,6 +474,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/machine/index.html b/blog/machine/index.html
index fa4eabf1b8..f21115c8e7 100644
--- a/blog/machine/index.html
+++ b/blog/machine/index.html
@@ -514,6 +514,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/meetup/index.html b/blog/meetup/index.html
index 3fd3f2d0b6..1c4b6281b0 100644
--- a/blog/meetup/index.html
+++ b/blog/meetup/index.html
@@ -471,6 +471,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/meltdown-and-spectre-patches-show.html b/blog/meltdown-and-spectre-patches-show.html
index 4400b0f921..dce6d54d9e 100644
--- a/blog/meltdown-and-spectre-patches-show.html
+++ b/blog/meltdown-and-spectre-patches-show.html
@@ -501,6 +501,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/meltdown/index.html b/blog/meltdown/index.html
index fa05b6e6b7..904644608d 100644
--- a/blog/meltdown/index.html
+++ b/blog/meltdown/index.html
@@ -496,6 +496,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/memory/index.html b/blog/memory/index.html
index 94be2c57fc..fcae4b87c6 100644
--- a/blog/memory/index.html
+++ b/blog/memory/index.html
@@ -523,6 +523,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/nodal/index.html b/blog/nodal/index.html
index 545c9235a0..217c5382e5 100644
--- a/blog/nodal/index.html
+++ b/blog/nodal/index.html
@@ -469,6 +469,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/open-source/index.html b/blog/open-source/index.html
index 9727483655..4c280c2607 100644
--- a/blog/open-source/index.html
+++ b/blog/open-source/index.html
@@ -525,6 +525,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/open/index.html b/blog/open/index.html
index cb35545c53..7fcc983664 100644
--- a/blog/open/index.html
+++ b/blog/open/index.html
@@ -551,6 +551,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/performance/index.html b/blog/performance/index.html
index 4bd44d342b..b5e3102b15 100644
--- a/blog/performance/index.html
+++ b/blog/performance/index.html
@@ -485,6 +485,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/presenting-apache-ignite-sql-grid.html b/blog/presenting-apache-ignite-sql-grid.html
index 8d09a42d82..68e90395ca 100644
--- a/blog/presenting-apache-ignite-sql-grid.html
+++ b/blog/presenting-apache-ignite-sql-grid.html
@@ -489,6 +489,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/protecting-apache-ignite-from-meltdown.html b/blog/protecting-apache-ignite-from-meltdown.html
index 2a6e26a4cd..92f45d7f3d 100644
--- a/blog/protecting-apache-ignite-from-meltdown.html
+++ b/blog/protecting-apache-ignite-from-meltdown.html
@@ -538,6 +538,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/rdbms/index.html b/blog/rdbms/index.html
index c6136f60e8..042b99e7ea 100644
--- a/blog/rdbms/index.html
+++ b/blog/rdbms/index.html
@@ -487,6 +487,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/release/index.html b/blog/release/index.html
index 11f4608da6..3e4001ffc4 100644
--- a/blog/release/index.html
+++ b/blog/release/index.html
@@ -122,7 +122,7 @@
<nav class="hdrmenu">
<ul class="flexi">
<li class="js-hasdrop"><a class="hdrmenu--expanded" href="/" data-panel="getStarted">Get Started</a></li>
- <li class="js-hasdrop"><a class="hdrmenu__current hdrmenu--expanded" href="/features" data-panel="features">Features</a></li>
+ <li class="js-hasdrop"><a class="hdrmenu--expanded" href="/features" data-panel="features">Features</a></li>
<li class="js-hasdrop"><a class="hdrmenu--expanded" href="/community.html" data-panel="community">Community</a></li>
<li><a href="/use-cases/provenusecases.html" data-panel="">Powered By</a></li>
<li class="js-hasdrop"><a class="hdrmenu--expanded" href="/resources.html" data-panel="resources">Resources</a></li>
@@ -634,6 +634,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/schema-design-for-distributed-systems-ai3.html b/blog/schema-design-for-distributed-systems-ai3.html
index fc56eac1f5..0f48941aa3 100644
--- a/blog/schema-design-for-distributed-systems-ai3.html
+++ b/blog/schema-design-for-distributed-systems-ai3.html
@@ -117,7 +117,7 @@
<nav class="hdrmenu">
<ul class="flexi">
<li class="js-hasdrop"><a class="hdrmenu--expanded" href="/" data-panel="getStarted">Get Started</a></li>
- <li class="js-hasdrop"><a class="hdrmenu__current hdrmenu--expanded" href="/features" data-panel="features">Features</a></li>
+ <li class="js-hasdrop"><a class="hdrmenu--expanded" href="/features" data-panel="features">Features</a></li>
<li class="js-hasdrop"><a class="hdrmenu--expanded" href="/community.html" data-panel="community">Community</a></li>
<li><a href="/use-cases/provenusecases.html" data-panel="">Powered By</a></li>
<li class="js-hasdrop"><a class="hdrmenu--expanded" href="/resources.html" data-panel="resources">Resources</a></li>
@@ -717,6 +717,7 @@ albums.upsert(null, abbeyRoad); // Automatically colocated with artist
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/security/index.html b/blog/security/index.html
index 386a1bb6de..cde70e0259 100644
--- a/blog/security/index.html
+++ b/blog/security/index.html
@@ -509,6 +509,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/source/index.html b/blog/source/index.html
index 1fae0a1b54..86d21a2961 100644
--- a/blog/source/index.html
+++ b/blog/source/index.html
@@ -551,6 +551,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/spark/index.html b/blog/spark/index.html
index b24e9b1882..7c6844a304 100644
--- a/blog/spark/index.html
+++ b/blog/spark/index.html
@@ -471,6 +471,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/spectre/index.html b/blog/spectre/index.html
index ba78f07511..1997484f49 100644
--- a/blog/spectre/index.html
+++ b/blog/spectre/index.html
@@ -496,6 +496,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/sql/index.html b/blog/sql/index.html
index b733e7edd5..9282f34723 100644
--- a/blog/sql/index.html
+++ b/blog/sql/index.html
@@ -534,6 +534,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/store/index.html b/blog/store/index.html
index e0cc705fa3..c7bb8650e1 100644
--- a/blog/store/index.html
+++ b/blog/store/index.html
@@ -468,6 +468,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/two/index.html b/blog/two/index.html
index d06d0e9fa3..9c78ee0855 100644
--- a/blog/two/index.html
+++ b/blog/two/index.html
@@ -490,6 +490,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/whats-new-in-apache-ignite-3-0.html b/blog/whats-new-in-apache-ignite-3-0.html
index 91305e2f34..4762e18721 100644
--- a/blog/whats-new-in-apache-ignite-3-0.html
+++ b/blog/whats-new-in-apache-ignite-3-0.html
@@ -541,6 +541,7 @@
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>
diff --git a/blog/whats-new-in-apache-ignite-3-1.html b/blog/whats-new-in-apache-ignite-3-1.html
index a9e5328c21..c7a4116a4f 100644
--- a/blog/whats-new-in-apache-ignite-3-1.html
+++ b/blog/whats-new-in-apache-ignite-3-1.html
@@ -688,6 +688,7 @@ node config update ignite.network.nodeFinder.type=MULTICAST
></a>
<script src="/js/vendor/hystmodal/hystmodal.min.js"></script>
<script src="/js/vendor/smoothscroll.js"></script>
+ <script src="/js/vendor/mermaid/mermaid.min.js"></script>
<script src="/js/main.js?ver=0.9"></script>
</body>
</html>