vitess VS Tile38

Compare vitess vs Tile38 and see what are their differences.


Vitess is a database clustering system for horizontal scaling of MySQL. (by vitessio)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
vitess Tile38
60 9
17,809 8,888
1.5% -
9.9 7.0
about 18 hours ago 8 days ago
Go Go
Apache License 2.0 MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of vitess. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-04-09.


Posts with mentions or reviews of Tile38. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-09-22.
  • Show HN: TG – Fast geometry library in C
    11 projects | | 22 Sep 2023
  • PostgreSQL: No More Vacuum, No More Bloat
    6 projects | | 15 Jul 2023
    Experimental format to help readability of a long rant:


    According to the OP, there's a "terrifying tale of VACUUM in PostgreSQL," dating back to "a historical artifact that traces its roots back to the Berkeley Postgres project." (1986?)


    Maybe the whole idea of "use X, it has been battle-tested for [TIME], is robust, all the bugs have been and keep being fixed," etc., should not really be that attractive or realistic for at least a large subset of projects.


    In the case of Postgres, on top of piles of "historic code" and cruft, there's the fact that each user of Postgres installs and runs a huge software artifact with hundreds or even thousands of features and dependencies, of which every particular user may only use a tiny subset.


    In Kleppmann's DDOA [1], after explaining why the declarative SQL language is "better," he writes: "in databases, declarative query languages like SQL turned out to be much better than imperative query APIs." I find this footnote to the paragraph a bit ironic: "IMS and CODASYL both used imperative query APIs. Applications typically used COBOL code to iterate over records in the database, one record at a time." So, SQL was better than CODASYL and COBOL in a number of ways... big surprise?

    Postgres' own PL/pgSQL [2] is a language that (I imagine) most people would rather NOT use: hence a bunch of alternatives, including PL/v8, on its own a huge mass of additional complexity. SQL is definitely "COBOLESQUE" itself.


    Could we come up with something more minimal than SQL and looking less like COBOL? (Hopefully also getting rid of ORMs in the process). Also, I have found inspiring to see some people creating databases for themselves. Perhaps not a bad idea for small applications? For instance, I found BuntDB [3], which the developer seems to be using to run his own business [4]. Also, HYTRADBOI? :-) [5].


    A usual objection to use anything other than a stablished relational DB is "creating a database is too difficult for the average programmer." How about debugging PostgreSQL issues, developing new storage engines for it, or even building expertise on how to set up the instances properly and keep it alive and performant? Is that easier?

    I personally feel more capable of implementing a small, well-tested, problem-specific, small implementation of a B-Tree than learning how to develop Postgres extensions, become an expert in its configuration and internals, or debug its many issues.

    Another common opinion is "SQL is easy to use for non-programmers." But every person that knows SQL had to learn it somehow. I'm 100% confident that anyone able to learn SQL should be able to learn a simple, domain-specific, programming language designed for querying DBs. And how many of these people that are not able to program imperatively would be able to read a SQL EXPLAIN output and fix deficient queries? If they can, that supports even more the idea that they should be able to learn something different than SQL.







  • Your Data Fits in RAM
    4 projects | | 2 Aug 2022
    I actually worked on a project that did this. We used a database called "Tile38" [1] which used an R-Tree to make geospatial queries speedy. It was pretty good.

    Our dataset was ~150 GiB, I think? All in RAM. Took a while to start the server, as it all came off disk. Could have been faster. (It borrowed Redis's query language, and its storage was just "store the commands the recreate the DB, literally", IIRC. Dead simple, but a lot of slack/wasted space there.)

    Overall not a bad database. Latency serving out of RAM was, as one should/would expect, very speedy!


  • Redcon - Redis compatible server framework for Rust
    10 projects | /r/rust | 14 May 2022
    I ported it from Go and use it for my Tile38 project.
  • Tile38 - a geolocation data store, spatial index, and realtime geofence
    1 project | /r/golang | 14 Aug 2021
    1 project | /r/geospatial | 14 Aug 2021
    1 project | /r/programming | 14 Aug 2021
  • Path hints for B-trees can bring a performance increase of 150% – 300%
    3 projects | | 30 Jul 2021
  • How do I implement push notifications on a 10 mile radius from a certain user?
    1 project | /r/dartlang | 17 Jun 2021

What are some alternatives?

When comparing vitess and Tile38 you can also consider the following projects:

tidb - TiDB is an open-source, cloud-native, distributed, MySQL-Compatible database for elastic scale and real-time analytics. Try AI-powered Chat2Query free at :

go-mysql-elasticsearch - Sync MySQL data into elasticsearch

supabase - The open source Firebase alternative.

ledisdb - A high performance NoSQL Database Server powered by Go

cockroach - CockroachDB - the open source, cloud-native distributed SQL database.

goleveldb - LevelDB key/value database in Go.

citus - Distributed PostgreSQL as an extension

groupcache - groupcache is a caching and cache-filling library, intended as a replacement for memcached in many cases.

InfluxDB - Scalable datastore for metrics, events, and real-time analytics

kingshard - A high-performance MySQL proxy