scaliendb VS yugabyte-db

Hey man, don't worry, it will be all right!

About ~10 years ago in 2012-2013, within a ~6 month period (i) my startup [1] which I've been doing for 4 years failed / we shut it down (ii) my wife left, and a few months later told me that she'd been cheating on me.

There was a ~6 month period when I was very depressed, sometimes I wasn't able to sleep for multiple nights in a row, even when I got sleep, it was a few hours at best. It was a truly terrible period, I felt humiliated and reduced to nothing. I looked at my friends with stable boring jobs and families and thought that I messed up big time. I was so depressed, I even went to church a couple of times Sunday morning, because I couldn't sleep and I felt so sorry for myself, even though I'm an agnostic physicist.

Then something really unexpected happened: I got a job at a successful startup [2], which had great culture and people, and suddenly I was partying 2x a week with great people. While I was doing my own startup I stopped doing sports, so I picked up a +15 kg. The depression helped me lose most of it, and since I suddenly had a lot of free-time (no startup, no wife), I started doing sports again [3]. Even more unexpected, being divorced turned out to be appealing to ladies (I jokingly call it the "wounded deer" phenomenon), so I suddenly had ladies sending me signals.

Overall, in another ~6 months, to my huge surprise, there was a huge turn-around in my life, and in the end 2013 became one of the best years in my life! It was super-surprising, because it started on such a downer (Jan-6 was when my wife told me it's over, next day she moved out), but by Q3 I was hooked up with my girlfriend [4], feeling super happy at work and I even did another Ironman that year!

So... it's completely normal to feel depressed in such situations. Just give it some time, build yourself up, and find a good social situation. I personally also started a Phd, which I didn't finish because of the aforementioned startup, but I don't want to tell you to do that. You can potentially create positive vibes around you even by going to a co-working place 2x a week, doing some team sports, etc.

-

[1] https://github.com/scalien/scaliendb

When it comes to production, it is recommended to use the official docker image for YugabyteDB. You can either obtain it from Docker Hub or build it yourself using the Dockerfile. If you are using CI/CD pipelines, it may be helpful to reduce the size of the image. One way to do this is to remove the debug symbols from the compiled binaries. These symbols are useful for troubleshooting but not essential for automated testing. If you encounter any issues, you can easily reproduce them using the regular image.

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.

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.

It can be done like https://github.com/yugabyte/yugabyte-db/ has.

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.

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

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.

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

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.