![Apache Ignite’s Baseline Topology explained](/sites/default/files/styles/blog_thumbnail/public/2019-03/Apache%20Ignite%E2%80%99s%20Baseline%20Topology%20explained.jpg?itok=s4Gs2tOg)
When the Ignite project emerged in the Apache Software Foundation, it was thought of as a pure in-memory-solution: a distributed cache that put data into memory to speed access time. But then in 2017 came Apache® Ignite™ 2.1, which saw the debut of Ignite’s Native Persistence module that allowed Ignite to be treated as a full-blown distributed database. Since then Ignite has not depended on an…