Author: dmagda
Date: Thu May 31 22:26:50 2018
New Revision: 1832650

URL: http://svn.apache.org/viewvc?rev=1832650&view=rev
Log:
Updated release notes

Modified:
    ignite/site/trunk/releases/2.5.0/release_notes.html

Modified: ignite/site/trunk/releases/2.5.0/release_notes.html
URL: 
http://svn.apache.org/viewvc/ignite/site/trunk/releases/2.5.0/release_notes.html?rev=1832650&r1=1832649&r2=1832650&view=diff
==============================================================================
--- ignite/site/trunk/releases/2.5.0/release_notes.html (original)
+++ ignite/site/trunk/releases/2.5.0/release_notes.html Thu May 31 22:26:50 2018
@@ -3,6 +3,24 @@
 </head>
 <body>
 <h1>Apache IGNITE 2.5</h1>
+<div>
+    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>
+    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.
+        Read <a 
href="https://blogs.apache.org/ignite/entry/apache-ignite-2-5-scaling"; 
target="_blank">this article</a>
+        which outlines major achievements of the release.
+    </p>
+</div>
 <div></div><h2>Features and Improvements</h2>
 <ul>
 <li>implement getCurrentCoordinator method in IgniteMXBean<a 
href="https://issues.apache.org/jira/browse/IGNITE-8430";> [#IGNITE-8430]</a>


Reply via email to