tiedot is a document database that uses JSON for documents and queries; it can be embedded into your program, or run a stand-alone server using HTTP for an API.
- Designed for both embedded usage and standalone service.
- Fault-tolerant data structures that put safety of your data first.
- Built with performance and scalability always in mind.
- Use JSON syntax to build powerful queries.
tiedot scales reasonably well on SMP machines. Under maximum load, it usually either uses all CPUs to 100%, or uses up all IO bandwidth. The following performance results are collected on three different types of machines, using tiedot built-in benchmark:
(Operations per second)
| Processor | Insert | Read | Query | Update | Delete | |
|---|---|---|---|---|---|---|
| Mobile Intel Core i7 (2nd Gen) | 140k | 310k | 58k | 60k | 140k | A 3 years old laptop |
| Desktop Intel Core 2 Duo | 107k | 231k | 44k | 48k | 90k | A 5 years old workstation |
| Amazon EC2 m1.xlarge | 90k | 188k | 39k | 42k | 116k | Medium range instance type |
| Amazon EC2 t1.micro | 18k | 70k | 15k | 19k | 54k | The slowest instance type |
- Quick Start Guide: tiedot in 10 minutes
- HTTP API reference
- Embedded usage
- Data structures
- Query processor and index
- Concurrency and networking
- Limitations
| Version | Branch | Release Date | Comment |
|---|---|---|---|
| Alpha | alpha | 2013-06-28 | First release |
You may want to check out Issues section for future plans, and please feel very free to contact Howard if you have any feedback / questions. I also have Twitter and blog, please check them out as well.
The following copyright notice and disclaimers apply to all files in the project repository:
Copyright (c) 2013, Howard Guo All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Is tiedot "yet another NoSQL database"?
There are probably as many NoSQL database as there are Linux distributions.
tiedot is not as powerful (yet) - and does not intend to compete with mainstream NoSQL database engines such as CouchDB or Cassandra. However, tiedot performs reasonably well given its small size (< 3k LOC); and for certain loads, it may perform as well as those large brand NoSQL solutions.
What is the motive behind this project?
Golang (Go) is a fascinating language - very easy to use, scalable and reasonably stable. I am very passionate about document database technologies (check out my other GitHub projects!) and enjoy the moments when my program scales well on SMP machines. So this is my Golang practice.
Why the name "tiedot"?
"tiedot" is a Finnish word standing for "data". I enjoy learning (natural and computer) languages, also enjoy listening to music in many languages. "Tiedot" sounds cute, doesn't it?