mejedi-tcl2lua VS tarantool-c

Compare mejedi-tcl2lua vs tarantool-c and see what are their differences.

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
mejedi-tcl2lua tarantool-c
1 1
- 26
- -
- 4.2
- about 1 month ago
C
- GNU General Public License v3.0 or later
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.

mejedi-tcl2lua

Posts with mentions or reviews of mejedi-tcl2lua. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-02-04.
  • Ten-year experience in DBMS testing
    15 projects | dev.to | 4 Feb 2022
    The history of SQL tests in Tarantool is fascinating. We used VDBE to adopt a part of SQLite code, namely the SQL query parser and the bytecode compiler. One of the main reasons was that SQLite code has almost 100% test coverage. However, the tests were written in TCL, and we don't use it at all. So we had to write a TCL-Lua convertor to port tests written in TCL, and imported them into the code base after optimizing the resulting code. We still use these tests and add new ones when necessary.

tarantool-c

Posts with mentions or reviews of tarantool-c. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-02-04.
  • Ten-year experience in DBMS testing
    15 projects | dev.to | 4 Feb 2022
    In CMake build files, we use compiler flags that enable extra checks at build time, and we run "make clean" when there are no raw warnings. Besides static analysis in the compilers, we use Coverity static analysis. We used PVS-Studio once, and it detected several non-critical errors in Tarantool itself and in tarantool-c connector. Sometimes, we used cppcheck, not that it found many bugs.

What are some alternatives?

When comparing mejedi-tcl2lua and tarantool-c you can also consider the following projects:

expirationd - Expiration daemon module for Tarantool

luaunit - LuaUnit is a popular unit-testing framework for Lua, with an interface typical of xUnit libraries (Python unittest, Junit, NUnit, ...). It supports several output formats (Text, TAP, JUnit, ...) to be used directly or work with Continuous Integration platforms (Jenkins, Maven, ...).

small - Specialized memory allocators

queue - Create task queues, add and take jobs, monitor failed tasks

YCSB - Yahoo! Cloud Serving Benchmark

jepsen.tarantool - Jepsen tests for Tarantool

luatest - Tarantool test framework written in Lua

msgpuck - A simple and efficient MsgPack binary serialization library in a self-contained header file

cbench - Tarantool C Bench - a simple tool to benchmark Tarantool internal API