StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. In-Memory Databases
  4. In Memory Databases
  5. MemSQL vs Tile38

MemSQL vs Tile38

OverviewComparisonAlternatives

Overview

MemSQL
MemSQL
Stacks86
Followers184
Votes44
Tile38
Tile38
Stacks17
Followers41
Votes0
GitHub Stars9.5K
Forks597

MemSQL vs Tile38: What are the differences?

# Introduction

Key differences between MemSQL and Tile38 are outlined below:

1. **Database Type**: MemSQL is a distributed, in-memory, SQL database management system, while Tile38 is an open-source geospatial database with a focus on location-based data.
   
2. **Primary Use Case**: MemSQL is primarily used for real-time analytics and operational applications that require high performance, scalability, and flexibility. In contrast, Tile38 is designed specifically for geospatial applications, spatial indexing, and querying geospatial data.

3. **Data Model**: MemSQL supports traditional SQL data modeling with tables, rows, and columns, suitable for relational data storage and processing. On the other hand, Tile38 focuses on geospatial data types such as points, lines, and polygons, offering specific functionalities for spatial queries.

4. **Architecture**: MemSQL utilizes a distributed architecture with a focus on in-memory processing to deliver high-performance analytics and query processing. Contrastingly, Tile38 is built on top of a single-node architecture optimized for geospatial operations and spatial indexing.

5. **Query Language**: MemSQL uses standard SQL for querying and manipulating data, providing a familiar interface for developers and analysts. In contrast, Tile38 offers its own query language tailored for geospatial operations, making it specialized for location-based data processing.

6. **Scalability**: MemSQL is designed for horizontal scalability and can be deployed in a distributed cluster to handle large volumes of data and high query loads efficiently. Tile38, while supporting replication for fault tolerance, is more focused on optimizing geospatial queries within a single instance.

In Summary, MemSQL and Tile38 differ in database type, primary use case, data model, architecture, query language, and scalability.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Detailed Comparison

MemSQL
MemSQL
Tile38
Tile38

MemSQL converges transactions and analytics for sub-second data processing and reporting. Real-time businesses can build robust applications on a simple and scalable infrastructure that complements and extends existing data pipelines.

It is an open source (MIT licensed), in-memory geolocation data store, spatial index, and realtime geofence. It supports a variety of object types including lat/lon points, bounding boxes, XYZ tiles, Geohashes, and GeoJSON.

ANSI SQL Support;Fully-distributed Joins;Compiled Queries; ACID Compliance;In-Memory Tables;On-Disk Tables; Massively Parallel Execution;Lock Free Data Structures;JSON Support; High Availability; Online Backup and Restore;Online Replication
Spatial index with search methods such as Nearby, Within, and Intersects; Realtime geofencing through webhooks or pub/sub channels; Object types of lat/lon, bbox, Geohash, GeoJSON, QuadKey, and XYZ tile; Support for lots of Clients Libraries written in many different languages; Variety of protocols, including http (curl), websockets, telnet, and the Redis RESP; Server responses are RESP or JSON; Full command line interface; Leader / follower replication; In-memory database that persists on disk
Statistics
GitHub Stars
-
GitHub Stars
9.5K
GitHub Forks
-
GitHub Forks
597
Stacks
86
Stacks
17
Followers
184
Followers
41
Votes
44
Votes
0
Pros & Cons
Pros
  • 9
    Distributed
  • 5
    Realtime
  • 4
    Columnstore
  • 4
    Concurrent
  • 4
    Sql
No community feedback yet
Integrations
Google Compute Engine
Google Compute Engine
MySQL
MySQL
QlikView
QlikView
Erlang
Erlang
PHP
PHP
C++
C++
Clojure
Clojure
Swift
Swift
Windows
Windows
Node.js
Node.js
Linux
Linux
Java
Java
Python
Python

What are some alternatives to MemSQL, Tile38?

Redis

Redis

Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams.

Hazelcast

Hazelcast

With its various distributed data structures, distributed caching capabilities, elastic nature, memcache support, integration with Spring and Hibernate and more importantly with so many happy users, Hazelcast is feature-rich, enterprise-ready and developer-friendly in-memory data grid solution.

Aerospike

Aerospike

Aerospike is an open-source, modern database built from the ground up to push the limits of flash storage, processors and networks. It was designed to operate with predictable low latency at high throughput with uncompromising reliability – both high availability and ACID guarantees.

Apache Ignite

Apache Ignite

It is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads delivering in-memory speeds at petabyte scale

SAP HANA

SAP HANA

It is an application that uses in-memory database technology that allows the processing of massive amounts of real-time data in a short time. The in-memory computing engine allows it to process data stored in RAM as opposed to reading it from a disk.

VoltDB

VoltDB

VoltDB is a fundamental redesign of the RDBMS that provides unparalleled performance and scalability on bare-metal, virtualized and cloud infrastructures. VoltDB is a modern in-memory architecture that supports both SQL + Java with data durability and fault tolerance.

Tarantool

Tarantool

It is designed to give you the flexibility, scalability, and performance that you want, as well as the reliability and manageability that you need in mission-critical applications

Azure Redis Cache

Azure Redis Cache

It perfectly complements Azure database services such as Cosmos DB. It provides a cost-effective solution to scale read and write throughput of your data tier. Store and share database query results, session states, static contents, and more using a common cache-aside pattern.

KeyDB

KeyDB

KeyDB is a fully open source database that aims to make use of all hardware resources. KeyDB makes it possible to breach boundaries often dictated by price and complexity.

LokiJS

LokiJS

LokiJS is a document oriented database written in javascript, published under MIT License. Its purpose is to store javascript objects as documents in a nosql fashion and retrieve them with a similar mechanism. Runs in node (including cordova/phonegap and node-webkit), nativescript and the browser.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase