# ANN: JuliaDB.jl

**URL:** <https://discourse.julialang.org/t/ann-juliadb-jl/3564>\
**Category:** Community\
**Created:** [May 6, 2017, 7:23pm UTC](https://discourse.julialang.org/t/ann-juliadb-jl/3564 "2017-05-06T19:23:38Z")\
**Posts on this page:** 1\
**Showing post:** 77

<div class="post-metadata">

**Author:** ![mbauman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbauman/32/31082_2.png) [@mbauman](https://discourse.julialang.org/u/mbauman)\
**Post date:** [May 11, 2017, 5:41pm UTC](https://discourse.julialang.org/t/ann-juliadb-jl/3564/77 "2017-05-11T17:41:44Z")

</div>

Alright, things were fairly intertwined, but I did my best to split off the naming discussion into: [The naming of JuliaDB.jl](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653/1)

One portion I was a little sad to see go was:

> [@The naming of JuliaDB.jl](https://discourse.julialang.org/t/the-naming-of-juliadb-jl/3653/2):
>
> 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.

Let’s try to keep this thread focused the functionality of JuliaDB.

---

_[View the full topic](https://discourse.julialang.org/t/ann-juliadb-jl/3564)._