# The naming of JuliaDB.jl

**URL:** <https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653>\
**Category:** Offtopic\
**Created:** [May 8, 2017, 5:28pm UTC](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653 "2017-05-08T17:28:48Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Juan](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/juan/32/7657_2.png) [@Juan](https://discourse.julialang.org/u/Juan)\
**Post date:** [May 8, 2017, 5:28pm UTC](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653/1 "2017-05-08T17:28:48Z")

</div>

Hello.

Are these two different projects with the same name:?  
[https://github.com/JuliaComputing/JuliaDB.jl](https://github.com/JuliaComputing/JuliaDB.jl)  
[https://github.com/JuliaDB](https://github.com/JuliaDB)

Do you have any benchmark (or comparison of features) against sqlite, data.table, feather, fst or monetdb?

Does it use compression?

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [May 8, 2017, 5:58pm UTC](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653/2 "2017-05-08T17:58:19Z")

</div>

One of these is an organization the other is a project. Still the name clash is not ideal. Honestly, we’ve tried forever to come up with a different name for JuliaDB, but nothing else has stuck, so in the interest of getting it out there, we decided to just go with the working name that we’ve been using internally. There are three options:

1. Both the org and the project can use the name “JuliaDB” and they can be disambiguated contextually.
2. The org could be renamed to “JuliaDatabases”, which is arguably a more apt name.
3. The project could be renamed to something else – we’re open to suggestions.

An aspect of understanding JuliaDB is that, compared to traditional SQL databases, which are all about transactional storage, JuliaDB is more about persistent computation and bringing code to data efficiently and seamlessly – including being able to store any kind of Julia data without fuss. So the “Julia” part in the name can be thought of as putting a strong emphasis on code.

---

<div class="post-metadata">

**Author:** ![shashi](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/shashi/32/1824_2.png) [@shashi](https://discourse.julialang.org/u/shashi)\
**Post date:** [May 8, 2017, 5:58pm UTC](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653/3 "2017-05-08T17:58:30Z")

</div>

[GitHub - JuliaData/JuliaDB.jl: Parallel analytical database in pure Julia](https://github.com/JuliaComputing/JuliaDB.jl) is a package, whereas [https://github.com/JuliaDB](https://github.com/JuliaDB) is an organization under which there are many database driver libraries. This could be confusing, and I think technically the plural `JuliaDatabases` is a more appropriate name for the organization.

> Do you have any benchmark (or comparison of features) against sqlite, data.table, feather, fst or monetdb?

Not as of now, but we’re working on it. The candidates for comparison we are considering are `pandas.Series` and `xts`, (maybe also `data.table`) which are columnar in-memory databases in the same design space as JuliaDB.jl, rather than `sqlite`.

---

<div class="post-metadata">

**Author:** ![giordano](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/giordano/32/2166_2.png) [@giordano](https://discourse.julialang.org/u/giordano)\
**Post date:** [May 8, 2017, 6:10pm UTC](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653/4 "2017-05-08T18:10:03Z")

</div>

[quote=“StefanKarpinski, post:14, topic:3564, full:true”]  
Honestly, we’ve tried forever to come up with a different name for JuliaDB, but nothing else has stuck[/quote]  
`DistributedBytes.jl` as suggested above?

---

<div class="post-metadata">

**Author:** ![StefanKarpinski](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stefankarpinski/32/24_2.png) [@StefanKarpinski](https://discourse.julialang.org/u/StefanKarpinski)\
**Post date:** [May 8, 2017, 6:14pm UTC](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653/5 "2017-05-08T18:14:18Z")

</div>

I think that @ChrisRackauckas was suggesting “Julia Distributed Bytes” as a backronym for JuliaDB rather than suggesting that we change the name to DistributedBytes.jl. Personally, I’d be rather confused if I found a package named distributed bytes and it was a database. OTOH, I’m not sure what I would expect it to be.

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [May 8, 2017, 6:18pm UTC](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653/6 "2017-05-08T18:18:55Z")

</div>

I almost feel a non descriptive name like “Pandas” or “Hadoop” or something like that would be best for JuliaDB.jl (i.e. the package). It seems like a product that doesn’t just emulate something that exists already, and it combines a lot of different things into quite a unique, new thing, and I almost feel that any combination of existing terms will just point folks in the wrong direction as to what the package actually is.

---

<div class="post-metadata">

**Author:** ![ChrisRackauckas](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chrisrackauckas/32/77_2.png) [@ChrisRackauckas](https://discourse.julialang.org/u/ChrisRackauckas)\
**Post date:** [May 8, 2017, 6:32pm UTC](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653/7 "2017-05-08T18:32:07Z")

</div>

> [@ANN: JuliaDB.jl](https://discourse.julialang.org/t/ann-juliadb-jl/3564/19):
>
> I think that @ChrisRackauckas was suggesting “Julia Distributed Bytes” as a backronym for JuliaDB rather than suggesting that we change the name to DistributedBytes.jl.

Yeah, I was partially kidding to address @davidanthoff’s concerns that the name should have distributed in there. I say partially because I too am at least slightly confused by the name, and at least that interpretation worked 🙂.

---

<div class="post-metadata">

**Author:** ![ChrisRackauckas](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/chrisrackauckas/32/77_2.png) [@ChrisRackauckas](https://discourse.julialang.org/u/ChrisRackauckas)\
**Post date:** [May 8, 2017, 6:33pm UTC](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653/8 "2017-05-08T18:33:24Z")

</div>

> [@ANN: JuliaDB.jl](https://discourse.julialang.org/t/ann-juliadb-jl/3564/14):
>
> The org could be renamed to “JuliaDatabases”, which is arguably a more apt name.

That should be done anyways IMO

---

<div class="post-metadata">

**Author:** ![Evizero](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/evizero/32/10118_2.png) [@Evizero](https://discourse.julialang.org/u/Evizero)\
**Post date:** [May 8, 2017, 6:38pm UTC](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653/9 "2017-05-08T18:38:22Z")

</div>

> [@ANN: JuliaDB.jl](https://discourse.julialang.org/t/ann-juliadb-jl/3564/23):
>
> I would be fine with a non-descriptive name if we can think of a good one

How about `Judid` for **Ju** lia **Di** stributed **D** atabase.

(Or are we over the whole “let’s just use some first name” thing ? 🙂 )

---

<div class="post-metadata">

**Author:** ![hpoit](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/hpoit/32/245_2.png) [@hpoit](https://discourse.julialang.org/u/hpoit)\
**Post date:** [May 8, 2017, 7:50pm UTC](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653/10 "2017-05-08T19:50:10Z")

</div>

I’m pretty happy with JuliaDB.jl for a name.

---

<div class="post-metadata">

**Author:** ![DNF](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dnf/32/10191_2.png) [@DNF](https://discourse.julialang.org/u/DNF)\
**Post date:** [May 8, 2017, 8:06pm UTC](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653/11 "2017-05-08T20:06:29Z")

</div>

> [@ANN: JuliaDB.jl](https://discourse.julialang.org/t/ann-juliadb-jl/3564/27):
>
> How about Judid for Julia Distributed Database.

A Julia version of Pandas? Judid?

Ahem…

Judas? [ducks and runs]

---

<div class="post-metadata">

**Author:** ![miguelraz](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/miguelraz/32/631_2.png) [@miguelraz](https://discourse.julialang.org/u/miguelraz)\
**Post date:** [May 8, 2017, 9:01pm UTC](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653/12 "2017-05-08T21:01:32Z")

</div>

JuliaFin, JuliaRun, JuliaPro… JuliaFlow?

---

<div class="post-metadata">

**Author:** ![jballanc](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jballanc/32/328_2.png) [@jballanc](https://discourse.julialang.org/u/jballanc)\
**Post date:** [May 9, 2017, 12:25am UTC](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653/13 "2017-05-09T00:25:23Z")

</div>

Honestly, I’m still amazed that no one has jumped on the [blindingly obvious](https://en.wikipedia.org/wiki/Julia_set) `JuliaSet.jl` 😉

---

<div class="post-metadata">

**Author:** ![JeffreySarnoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jeffreysarnoff/32/1980_2.png) [@JeffreySarnoff](https://discourse.julialang.org/u/JeffreySarnoff)\
**Post date:** [May 9, 2017, 1:08am UTC](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653/14 "2017-05-09T01:08:08Z")

</div>

🗨

```
  JuliaDB JuliaFlex  
       DTable FlexTable

```

---

<div class="post-metadata">

**Author:** ![hgeorgako](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/hgeorgako/32/5518_2.png) [@hgeorgako](https://discourse.julialang.org/u/hgeorgako)\
**Post date:** [May 9, 2017, 2:03am UTC](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653/15 "2017-05-09T02:03:03Z")

</div>

Jackal.jl  
Juice.jl (The glass looks like a database. That’s why)  
Jagger.jl

![](https://global.discourse-cdn.com/julialang/original/3X/e/3/e340f782f3438cb503cfd8918904982a4efd7169.png)

---

<div class="post-metadata">

**Author:** ![essenciary](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/essenciary/32/210469_2.png) [@essenciary](https://discourse.julialang.org/u/essenciary)\
**Post date:** [May 9, 2017, 12:03pm UTC](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653/16 "2017-05-09T12:03:42Z")

</div>

Sorry for the off-topic but are there any plans for the core team to officially support the low-level libraries for the main relational databases? For example, the most complete PostgreSQL library ([https://github.com/JuliaDB/PostgreSQL.jl](https://github.com/JuliaDB/PostgreSQL.jl)) is abandonware for almost year and lacks useful features (like pub/sub).

---

<div class="post-metadata">

**Author:** ![barche](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/barche/32/79_2.png) [@barche](https://discourse.julialang.org/u/barche)\
**Post date:** [May 9, 2017, 12:47pm UTC](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653/17 "2017-05-09T12:47:38Z")

</div>

> [@ANN: JuliaDB.jl](https://discourse.julialang.org/t/ann-juliadb-jl/3564/14):
>
> Honestly, we’ve tried forever to come up with a different name for JuliaDB, but nothing else has stuck

Half-joking of course (especially since I can’t think of anything better either), but shouldn’t it be [avoided to use Julia in the package name](https://docs.julialang.org/en/latest/manual/packages.html#Package-Development-1)? 😉

---

<div class="post-metadata">

**Author:** ![mkborregaard](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mkborregaard/32/556_2.png) [@mkborregaard](https://discourse.julialang.org/u/mkborregaard)\
**Post date:** [May 9, 2017, 12:51pm UTC](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653/18 "2017-05-09T12:51:49Z")

</div>

One must assume that “the package is connected to, or endorsed by, contributors to the Julia language itself” 🙂

---

<div class="post-metadata">

**Author:** ![datnamer](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/datnamer/32/3471_2.png) [@datnamer](https://discourse.julialang.org/u/datnamer)\
**Post date:** [May 9, 2017, 1:20pm UTC](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653/19 "2017-05-09T13:20:20Z")

</div>

What anout ODBC.jl?

---

<div class="post-metadata">

**Author:** ![essenciary](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/essenciary/32/210469_2.png) [@essenciary](https://discourse.julialang.org/u/essenciary)\
**Post date:** [May 9, 2017, 1:41pm UTC](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653/20 "2017-05-09T13:41:10Z")

</div>

From my perspective, using ODBC drivers for web apps is very rare. I don’t think it’s a common approach with any modern web development stack (certainly not Ruby, PHP, JavaScript, etc). Not even [ASP.NET](http://ASP.NET) as far as I remember.

But I guess this can be a way to go if we can’t have up to date libraries wrapping the C API. Thanks for the tip.

[Next page](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653.md?page=2)