mysql-5.6
yugabyte-db
mysql-5.6 | yugabyte-db | |
---|---|---|
6 | 88 | |
2,446 | 8,498 | |
0.4% | 0.7% | |
9.4 | 10.0 | |
4 days ago | 3 days ago | |
C++ | C | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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.
mysql-5.6
-
Jonathan Katz: Thoughts on PostgreSQL in 2024
RocksDB is a fork of Google's LevelDB, a KV store using Log Structured Merge Tree (LSM tree) which is great for high write workloads. The MySQL storage engine that uses RocksDB is called MyRocks[0].
[0] http://myrocks.io/
-
High Performance Embedded Key-Value Store
This is much lower-level than sqlite. In fact, you could use this as the storage layer for a SQL database. See, e.g., MyRocks[0] which is a MySQL backend that uses RocksDB as the storage layer.
[0] http://myrocks.io/
-
FOQS: Making a distributed priority queue disaster-ready
> given how much $FB has benefited from running the entirety of the worlds largest social graph on top of MySQL.
They've contributed quite a lot back to the MySQL community, I thought? MyRocks comes to mind
http://myrocks.io/
-
Leaving MySQL
as we are all discussing the pros and cons of various DBs, my favourite MySQL feature has to be the pluggable storage engines. Being able to support both InnoDB and RocksDB backed tables in the same database is wonderful. Just today I made use of the MyRocks storage engine's handy TTL [1] feature instead of a tedious delete & optimise scheduled job
[1]https://github.com/facebook/mysql-5.6/wiki/Time-to-Live-%28T...
-
Microsoft Introduces EdgelessDB: A Database Designed for Confidential Computing
Note: while it is based on MariaDB, it replaces InnoDB (the MariaDB/MySQL storage engine) with MyRocks (which is based on RocksDB), and as a consequence it is missing some features (such as foreign keys[1]) that prevent it from being usable in many applications.
[1] https://github.com/facebook/mysql-5.6/wiki/MyRocks-limitatio...
- Is Flutter a good choice for my social network app?
yugabyte-db
-
Multi-region YugabyteDB deployment on AWS EKS with Istio
YugabyteDB is a transactional database that brings together four must-have needs of cloud native apps – namely SQL as a flexible query language, low-latency performance, continuous availability, and globally-distributed scalability. Other databases do not serve all 4 of these needs simultaneously.
-
Best Practice: use the same datatypes for comparisons, like joins and foreign keys
It is possible to apply Batched Nested Loop but with additional code that checks the range of the outer bigint and compare it only if it matches the range of integer. This has been added in YugabyteDB 2.21 with #20715 YSQL: Allow BNL on joins over different integer types to help migrations from PostgreSQL with such datatype inconsistencies.
-
Jonathan Katz: Thoughts on PostgreSQL in 2024
It can be done like https://github.com/yugabyte/yugabyte-db/ has.
-
Is co-partition or interleave necessary in Distributed SQL?
Therefore, interleaving or co-partitioning is probably not necessary, and would reduce agility and scalability more than improving the performance. Unless you have a good reason for it that you can share on Issue #79. But, first, test and tune the queries to see if you need something else.
-
PostGIS on YugabyteDB Alma8 (workarounds)
This is a workaround, not supported. I've opened the following issue to get it solve in the YugabyteDB deployment: https://github.com/yugabyte/yugabyte-db/issues/19389
-
Bitmap Scan in YugabyteDB
Note that there may still be a need for bitmaps, especially with disjunctions (OR) as the following is about conjunction (AND), and it can still be implemented, differently than PostgreSQL. This is tracked by #4634.
- Yugabyte – distributed PostgreSQL, 100% open source
-
PL/Python on YugabyteDB
FROM almalinux:8 as build RUN dnf -y update &&\ dnf groupinstall -y 'Development Tools' # get YugabyteDB sources ARG YB_TAG=2.18 RUN git clone --branch ${YB_TAG} https://github.com/yugabyte/yugabyte-db.git WORKDIR yugabyte-db # install dependencies and compilation tools RUN dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm RUN dnf -y install epel-release libatomic rsync python3-devel cmake3 java-1.8.0-openjdk maven npm golang gcc-toolset-12 gcc-toolset-12-libatomic-devel patchelf glibc-langpack-en ccache vim wget python3.11-devel python3.11-pip clang ncurses-devel readline-devel libsqlite3x-devel RUN mkdir /opt/yb-build RUN chown "$USER" /opt/yb-build # Install Python 3 RUN alternatives --remove-all python3 RUN alternatives --remove-all python RUN alternatives --install /usr/bin/python python /usr/bin/python3.11 3 RUN alternatives --install /usr/bin/python3 python3 /usr/bin/python3.11 3 # add #include "pg_yb_utils.h" to src/postgres/src/pl/plpython/plpy_procedure.c RUN sed -e '/#include "postgres.h"/a#include "pg_yb_utils.h"' -i src/postgres/src/pl/plpython/plpy_procedure.c # if using python > 3.9 remove #include and #include from src/postgres/src/pl/plpython/plpython.h RUN sed -e '/#include /d' -e '/#include /d' -i src/postgres/src/pl/plpython/plpython.h # add '--with-python', to python/yugabyte/build_postgres.py under the configure_postgres method RUN sed -e "/'\.\/configure',/a\ '--with-python'," -i python/yugabyte/build_postgres.py # Build and package the release RUN YB_CCACHE_DIR="$HOME/.cache/yb_ccache" ./yb_build.sh -j$(nproc) --clean-all --build-yugabyted-ui --no-linuxbrew --clang15 -f release RUN chmod +x bin/get_clients.sh bin/parse_contention.py bin/yb-check-consistency.py RUN YB_USE_LINUXBREW=0 ./yb_release --force WORKDIR / RUN mv /yugabyte-db/build/yugabyte*.tar.gz /yugabyte.tgz
-
YugabyteDB official Dockerfile
You have seen me using the official YugabyteDB Docker image extensively. This image is suitable for various purposes, including labs, development, testing, and even production. In the past, we used to create it internally due to its seamless integration with our build process. However, some companies prefer to construct the image on their own, which is indeed a commendable practice. After all, it's not advisable to run random images with root privileges on your servers. As a result, we have made a significant alteration by introducing a refined Dockerfile to our Github repository.
-
FlameGraphs on Steroids with profiler.firefox.com
Of course, I can guess from the function names, but YugabyteDB is Open Source and I can search for them. What happens here is that I didn't declare a Primary Key for my table and then an internal one (ybctid) is generated, because secondary indexes need a key to address the table row. This ID generation calls /dev/urandom. I made this simple example to show that low-level traces can give a clue about high level data model problems.
What are some alternatives?
splinterdb - High Performance Embedded Key-Value Store
citus - Distributed PostgreSQL as an extension
edgelessdb - EdgelessDB is a MySQL-compatible database for confidential computing. It runs entirely inside a secure enclave and comes with advanced features for collaboration, recovery, and access control.
cockroach - CockroachDB - the open source, cloud-native distributed SQL database.
duckduckgo-locales - Translation files for <a href="https://duckduckgo.com"> </a>
neon - Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, branching, and bottomless storage.
gh-ost - GitHub's Online Schema-migration Tool for MySQL
psycopg2 - PostgreSQL database adapter for the Python programming language
realtime - Broadcast, Presence, and Postgres Changes via WebSockets
rosettable - service to add postgres triggers on mysql CRUD events
Apache AGE - Graph database optimized for fast analysis and real-time data processing. It is provided as an extension to PostgreSQL. [Moved to: https://github.com/apache/age]