{
    "version": "https://jsonfeed.org/version/1",
    "title": "Apache Ignite Blog",
    "home_page_url": "https://ignite.apache.org/blog",
    "description": "News, updates, and technical articles about Apache Ignite",
    "items": [
        {
            "id": "https://ignite.apache.org/blog/2026/05/06/apache-ignite-2-18-0",
            "content_html": null,
            "url": "https://ignite.apache.org/blog/2026/05/06/apache-ignite-2-18-0",
            "title": "Apache Ignite 2.18 Release: What's New",
            "summary": "We are happy to announce the release of Apache Ignite 2.18.0!",
            "date_modified": "2026-05-06T00:00:00.000Z",
            "author": {
                "name": "Evgeniy Stanilovskiy",
                "url": "https://github.com/zstan"
            },
            "tags": [
                "database",
                "ignite2",
                "release"
            ]
        },
        {
            "id": "https://ignite.apache.org/blog/2026/01/27/schema-data-mapping-ignite3",
            "content_html": null,
            "url": "https://ignite.apache.org/blog/2026/01/27/schema-data-mapping-ignite3",
            "title": "Schema and Data Mapping in Apache Ignite 3",
            "summary": "Your schema came from somewhere. Maybe SQL scripts, maybe another developer, maybe your own DDL. Your application uses Mapper.of() for data access, and the workflow is functional. But if your POJO field names don't exactly match your column names, you're writing map() calls to bridge them, and that can start to feel heavy.",
            "date_modified": "2026-01-28T00:00:00.000Z",
            "author": {
                "name": "Michael Aglietti",
                "url": "https://github.com/maglietti"
            },
            "tags": [
                "technical",
                "ignite3",
                "java"
            ]
        },
        {
            "id": "https://ignite.apache.org/blog/2026/01/13/ignite3-architecture-p8",
            "content_html": null,
            "url": "https://ignite.apache.org/blog/2026/01/13/ignite3-architecture-p8",
            "title": "The Business Case for Architectural Evolution: Platform Consolidation Benefits",
            "summary": "Your high-velocity application's architectural decisions directly impact business metrics. Response times affect customer satisfaction. System complexity drives operational overhead. Development velocity determines competitive advantage. When architecture limits business outcomes, evolution isn't a technical choice. It's a business necessity.",
            "date_modified": "2026-01-13T00:00:00.000Z",
            "author": {
                "name": "Michael Aglietti",
                "url": "https://github.com/maglietti"
            },
            "tags": [
                "architecture",
                "technical",
                "ignite3"
            ]
        },
        {
            "id": "https://ignite.apache.org/blog/2026/01/06/ignite3-architecture-p7",
            "content_html": null,
            "url": "https://ignite.apache.org/blog/2026/01/06/ignite3-architecture-p7",
            "title": "MVCC Transactions for High-Frequency Processing: ACID at Scale",
            "summary": "Traditional databases force a choice between fast transactions and concurrent analytics, but Apache Ignite's universal transaction model delivers both simultaneously.",
            "date_modified": "2026-01-06T00:00:00.000Z",
            "author": {
                "name": "Michael Aglietti",
                "url": "https://github.com/maglietti"
            },
            "tags": [
                "architecture",
                "technical",
                "ignite3"
            ]
        },
        {
            "id": "https://ignite.apache.org/blog/2025/12/30/ignite3-architecture-p6",
            "content_html": null,
            "url": "https://ignite.apache.org/blog/2025/12/30/ignite3-architecture-p6",
            "title": "Distributed Consistency Under Load: When High-Velocity Meets High-Availability",
            "summary": "Distributed systems traditionally force a choice between consistency and speed. Apache Ignite's RAFT implementation delivers both: strong guarantees that protect your business without the coordination penalties that limit throughput.",
            "date_modified": "2025-12-30T00:00:00.000Z",
            "author": {
                "name": "Michael Aglietti",
                "url": "https://github.com/maglietti"
            },
            "tags": [
                "architecture",
                "technical",
                "ignite3"
            ]
        },
        {
            "id": "https://ignite.apache.org/blog/2025/12/23/ignite3-architecture-p5",
            "content_html": null,
            "url": "https://ignite.apache.org/blog/2025/12/23/ignite3-architecture-p5",
            "title": "Eliminating Data Movement: The Hidden Cost of Distributed Event Processing",
            "summary": "Your high-velocity application processes events fast enough until it doesn't. The bottleneck isn't CPU or memory. It's data movement. Every time event processing requires data from another node, network latency adds milliseconds that compound into seconds of delay under load.",
            "date_modified": "2025-12-23T00:00:00.000Z",
            "author": {
                "name": "Michael Aglietti",
                "url": "https://github.com/maglietti"
            },
            "tags": [
                "architecture",
                "technical",
                "ignite3"
            ]
        },
        {
            "id": "https://ignite.apache.org/blog/2025/12/16/ignite3-architecture-p4",
            "content_html": null,
            "url": "https://ignite.apache.org/blog/2025/12/16/ignite3-architecture-p4",
            "title": "Integrated Platform Performance: Maintaining Speed Under Pressure",
            "summary": "Traditional systems force a choice: real-time analytics or fast transactions. Apache Ignite eliminates this trade-off with integrated platform performance that delivers both simultaneously.",
            "date_modified": "2025-12-16T00:00:00.000Z",
            "author": {
                "name": "Michael Aglietti",
                "url": "https://github.com/maglietti"
            },
            "tags": [
                "architecture",
                "technical",
                "ignite3"
            ]
        },
        {
            "id": "https://ignite.apache.org/blog/2025/12/10/ignite3-client-connections",
            "content_html": null,
            "url": "https://ignite.apache.org/blog/2025/12/10/ignite3-client-connections",
            "title": "How many client connections can Apache Ignite 3 handle?",
            "summary": "Apache Ignite 3 manages client connections so efficiently that the scaling limits common in database-style systems simply aren't a factor.",
            "date_modified": "2025-12-11T00:00:00.000Z",
            "author": {
                "name": "Pavel Tupitsyn",
                "url": "https://github.com/ptupitsyn"
            },
            "tags": [
                "performance",
                "technical",
                "ignite3"
            ]
        },
        {
            "id": "https://ignite.apache.org/blog/2025/12/09/ignite3-architecture-p3",
            "content_html": null,
            "url": "https://ignite.apache.org/blog/2025/12/09/ignite3-architecture-p3",
            "title": "Schema Evolution Under Operational Pressure: When Downtime Isn't an Option",
            "summary": "Schema changes in traditional databases mean downtime, lost revenue, and deployment chaos across multiple systems. This piece demonstrates how Apache Ignite's flexible schema approach helps lets data model evolve at the pace of your business requirements.",
            "date_modified": "2025-12-10T00:00:00.000Z",
            "author": {
                "name": "Michael Aglietti",
                "url": "https://github.com/maglietti"
            },
            "tags": [
                "architecture",
                "technical",
                "ignite3"
            ]
        },
        {
            "id": "https://ignite.apache.org/blog/2025/12/02/ignite3-architecture-p2",
            "content_html": null,
            "url": "https://ignite.apache.org/blog/2025/12/02/ignite3-architecture-p2",
            "title": "Memory-First Architecture: The Foundation for High-Velocity Event Processing",
            "summary": "Traditional databases force a choice: fast memory access or durable storage. High-velocity applications processing 10,000+ events per second hit a wall when disk I/O adds 5-15ms to every transaction.",
            "date_modified": "2025-12-03T00:00:00.000Z",
            "author": {
                "name": "Michael Aglietti",
                "url": "https://github.com/maglietti"
            },
            "tags": [
                "architecture",
                "technical",
                "ignite3"
            ]
        },
        {
            "id": "https://ignite.apache.org/blog/2025/11/25/ignite3-architecture-p1",
            "content_html": null,
            "url": "https://ignite.apache.org/blog/2025/11/25/ignite3-architecture-p1",
            "title": "When Multi-System Complexity Compounds at Scale",
            "summary": "Your high-velocity application began with smart architectural choices: PostgreSQL for reliable transactions, Redis for fast cache access, and custom processing for domain-specific logic. These decisions powered early success and growth.",
            "date_modified": "2025-11-26T00:00:00.000Z",
            "author": {
                "name": "Michael Aglietti",
                "url": "https://github.com/maglietti"
            },
            "tags": [
                "architecture",
                "technical",
                "ignite3"
            ]
        },
        {
            "id": "https://ignite.apache.org/blog/2025/11/18/schema-design-for-distributed-systems-ai3",
            "content_html": null,
            "url": "https://ignite.apache.org/blog/2025/11/18/schema-design-for-distributed-systems-ai3",
            "title": "Schema Design for Distributed Systems: Why Data Placement Matters",
            "summary": "You can scale out your database, add more nodes, and tune every index, but if your data isn’t in the right place, performance still hits a wall. Every distributed system eventually runs into this: joins that cross the network, caches that can’t keep up, and queries that feel slower the larger your cluster gets.",
            "date_modified": "2025-11-19T00:00:00.000Z",
            "author": {
                "name": "Michael Aglietti",
                "url": "https://github.com/maglietti"
            },
            "tags": [
                "technical",
                "ignite3"
            ]
        },
        {
            "id": "https://ignite.apache.org/blog/2025/11/11/getting-to-know-ignite3",
            "content_html": null,
            "url": "https://ignite.apache.org/blog/2025/11/11/getting-to-know-ignite3",
            "title": "Getting to Know Apache Ignite 3",
            "summary": "Apache Ignite 3 is a memory-first distributed SQL database platform that consolidates transactions, analytics, and compute workloads previously requiring separate systems. Built from the ground up over four years of development, it represents a complete departure from traditional caching solutions toward a unified distributed computing platform with microsecond latencies and collocated processing capabilities.",
            "date_modified": "2025-11-12T00:00:00.000Z",
            "author": {
                "name": "Michael Aglietti",
                "url": "https://github.com/maglietti"
            },
            "tags": [
                "technical",
                "ignite3",
                "featured"
            ]
        },
        {
            "id": "https://ignite.apache.org/blog/2025/11/03/apache-ignite-3-1",
            "content_html": null,
            "url": "https://ignite.apache.org/blog/2025/11/03/apache-ignite-3-1",
            "title": "Apache Ignite 3.1: Performance, Multi-Language Client Support, and Production Hardening",
            "summary": "Apache Ignite 3.1 improves the three areas that matter most when running distributed systems: performance at scale, language flexibility, and operational visibility. The release also fixes hundreds of bugs related to data corruption, race conditions, and edge cases discovered since 3.0.",
            "date_modified": "2025-11-03T00:00:00.000Z",
            "author": {
                "name": "Evgeniy Stanilovskiy",
                "url": "https://github.com/zstan"
            },
            "tags": [
                "apache",
                "release",
                "ignite3"
            ]
        },
        {
            "id": "https://ignite.apache.org/blog/2025/02/24/whats-new-in-apache-ignite-3-0",
            "content_html": null,
            "url": "https://ignite.apache.org/blog/2025/02/24/whats-new-in-apache-ignite-3-0",
            "title": "What's New in Apache Ignite 3.0",
            "summary": "Apache Ignite 3.0 is the latest milestone in Apache Ignite evolution that enhances developer experience, platform resilience, and efficiency. In this article, we'll explore the key new features and improvements in Apache Ignite 3.0.",
            "date_modified": "2025-02-24T00:00:00.000Z",
            "author": {
                "name": "Stanislav Lukyanov",
                "url": "https://github.com/slukyanov"
            },
            "tags": [
                "apache",
                "release",
                "ignite3"
            ]
        },
        {
            "id": "https://ignite.apache.org/blog/2025/02/13/apache-ignite-2-17-0",
            "content_html": null,
            "url": "https://ignite.apache.org/blog/2025/02/13/apache-ignite-2-17-0",
            "title": "Apache Ignite 2.17 Release: What's New",
            "summary": "We are happy to announce the release of Apache Ignite 2.17.0! In this latest version, the Ignite community has introduced a range of new features and improvements to deliver a more efficient, flexible, and future-proof platform. Below, we'll cover the key highlights that you can look forward to when upgrading to the new release.",
            "date_modified": "2025-02-13T00:00:00.000Z",
            "author": {
                "name": "Nikita Amelchev",
                "url": "https://github.com/NSAmelchev"
            },
            "tags": [
                "database",
                "ignite2",
                "release",
                "archived"
            ]
        }
    ]
}