This is an automated email from the ASF dual-hosted git repository.
ppa 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 1002a6d830 IGNITE-27551-fix Fix missing <br> (#308)
1002a6d830 is described below
commit 1002a6d83055c1ff6b85ec11af2e75932a4d63c2
Author: jinxxxoid <[email protected]>
AuthorDate: Wed Jan 14 11:36:52 2026 +0400
IGNITE-27551-fix Fix missing <br> (#308)
---
_src/_blog/apache-ignite-3-architecture-part-8.pug | 4 ++++
blog/apache-ignite-3-architecture-part-8.html | 7 +++----
2 files changed, 7 insertions(+), 4 deletions(-)
diff --git a/_src/_blog/apache-ignite-3-architecture-part-8.pug
b/_src/_blog/apache-ignite-3-architecture-part-8.pug
index da4e922303..eb3907d491 100644
--- a/_src/_blog/apache-ignite-3-architecture-part-8.pug
+++ b/_src/_blog/apache-ignite-3-architecture-part-8.pug
@@ -349,6 +349,7 @@ pre
br
h2 The Architectural Evolution Decision
+
h3 When Platform Consolidation Makes Business Sense
p #[strong Clear Indicators:]
ul
@@ -384,6 +385,7 @@ ul
br
h2 The Evolution Imperative
+br
p Your current architecture enabled your initial success. But architecture
that works at 1,000 events/second faces different challenges at 10,000
events/second. The question isn't whether you'll need to evolve. It's whether
you'll evolve proactively or reactively.
p #[strong Proactive Evolution Benefits:]
ul
@@ -397,6 +399,7 @@ p Apache Ignite 3 represents architectural evolution that
eliminates the fundame
br
h2 Series Conclusion: Architecture as Business Strategy
+br
p This series demonstrated how Apache Ignite 3's integrated platform addresses
the compound challenges of high-velocity applications:
ol
li #[strong Multi-system complexity] creates performance bottlenecks that
grow with success
@@ -407,6 +410,7 @@ ol
li #[strong Distributed consensus] ensures consistency during high-frequency
operations
li #[strong MVCC transactions] provide ACID guarantees without performance
sacrifice
li #[strong Platform consolidation] delivers measurable business benefits
+br
p #[strong The architectural principle]: When your application's success
outgrows your architecture's design limits, evolution becomes a business
imperative.
p Your high-velocity application can scale past traditional constraints. The
technical foundation exists. The business case is compelling. The only question
is whether you'll evolve your architecture as intentionally as you've evolved
your application.
diff --git a/blog/apache-ignite-3-architecture-part-8.html
b/blog/apache-ignite-3-architecture-part-8.html
index 6e00136bb0..2d3897e508 100644
--- a/blog/apache-ignite-3-architecture-part-8.html
+++ b/blog/apache-ignite-3-architecture-part-8.html
@@ -730,6 +730,7 @@ public class BusinessMetricsCollector {
</ul>
<br />
<h2>The Evolution Imperative</h2>
+ <br />
<p>
Your current architecture enabled your initial success. But
architecture that works at 1,000 events/second faces different challenges at
10,000 events/second. The question isn't whether you'll need to evolve. It's
whether
you'll evolve proactively or reactively.
@@ -749,6 +750,7 @@ public class BusinessMetricsCollector {
</p>
<br />
<h2>Series Conclusion: Architecture as Business Strategy</h2>
+ <br />
<p>This series demonstrated how Apache Ignite 3's integrated
platform addresses the compound challenges of high-velocity applications:</p>
<ol>
<li><strong>Multi-system complexity</strong> creates
performance bottlenecks that grow with success</li>
@@ -760,16 +762,13 @@ public class BusinessMetricsCollector {
<li><strong>MVCC transactions</strong> provide ACID
guarantees without performance sacrifice</li>
<li><strong>Platform consolidation</strong> delivers
measurable business benefits</li>
</ol>
+ <br />
<p><strong>The architectural principle</strong>: When your
application's success outgrows your architecture's design limits, evolution
becomes a business imperative.</p>
<p>
Your high-velocity application can scale past traditional
constraints. The technical foundation exists. The business case is compelling.
The only question is whether you'll evolve your architecture as intentionally as
you've evolved your application.
</p>
<br />
- <p>
- <strong>[← Return to Part 1: When Multi-System Complexity
Compounds at Scale</strong>(ai3-arch-blog-1-multi-system-complexity.html)] |
<strong>[View Series
Introduction</strong>(ai3-arch-blog-0-series-introduction.html)]
- </p>
- <br />
<p><em>Thank you for following this architectural journey.
Your applications deserve platforms that scale with your business success, not
against it.</em></p>
</div>
</article>
