yugabyte-db
geo-distributed-messenger
yugabyte-db | geo-distributed-messenger | |
---|---|---|
91 | 6 | |
8,580 | 9 | |
1.1% | - | |
10.0 | 5.0 | |
4 days ago | 8 months ago | |
C | Java | |
GNU General Public License v3.0 or later | The Unlicense |
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.
yugabyte-db
-
Crash on clock skew: performance vs availability
In a distributed database, NTP synchronization is essential and should be carefully monitored and fixed in case of any failures. To allow some time drift, a maximum clock skew is set. This skew should be kept low enough for performance to avoid too many read retries and high enough for availability to avoid any node evictions caused by network errors. It is a good idea to check the NTP synchronization when starting a YugabyteDB node. This will be implemented by 22255.
-
Advisory/Custom/Application Lock with YugabyteDB
Different ways exist to implement locking mechanisms on arbitrary values. For example, PostgreSQL provides pg_advisory_lock, MySQL has get_lock, Oracle Database offers dbms_lock, and SQL Server use sp_getapplock. For YugabyteDB, the PostgreSQL version is not currently supported (#3642).
-
A lightweight YugabyteDB docker image for CI/CD
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.
-
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
geo-distributed-messenger
-
Geo-Distributed Microservices and Their Database: Fighting the High Latency
My development journey of the first version of the geo-distributed messenger has ended. So in this last article of the series, I’d like to talk about multi-region database deployment options that were validated for the messenger.
-
Using Global Cloud Load Balancer to Route User Requests to the Closest App Instance
Suppose Ms. Blue, one of my application users, is vacationing in the Tampa Bay area of Florida. She promised not to open my corporate Slack-like messenger (the geo-distributed app I’m building) while on vacation.
-
Geo-Distributed API Layer With Kong Gateway
When I start a VM in Google Cloud, the VM executes a special startup script that installs required libraries, builds and runs the microservices, and configures Kong Gateway. These are the steps for Kong setup:
-
Automating Java Application Deployment Across Multiple Cloud Regions
I developed the habit of coding the geo-distributed messenger two days a week (strictly during business hours, as evenings are for my mischievous sons and dear wife!). So, here is the latest summary, for those of you who are following my development journey.
-
How To Connect a Heroku Java App to a Cloud-Native Database
Ahoy, matey! I'm back from a short vacation and ready to continue my pet project: geo-distributed messenger in Java!
-
How to Build a Multi-Zone Java App in One Day
Let me walk you through the main components of the first version of my messenger application. Here are its GitHub coordinates.
What are some alternatives?
citus - Distributed PostgreSQL as an extension
Vaadin - Vaadin 6, 7, 8 is a Java framework for modern Java web applications.
cockroach - CockroachDB - the open source, cloud-native distributed SQL database.
nodejs-storage - Node.js client for Google Cloud Storage: unified object storage for developers and enterprises, from live data serving to data analytics/ML to data archiving.
neon - Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.
psycopg2 - PostgreSQL database adapter for the Python programming language
realtime - Broadcast, Presence, and Postgres Changes via WebSockets
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]
postgres-ha - Postgres + Stolon for HA clusters as Fly apps.
PostgreSQL - Mirror of the official PostgreSQL GIT repository. Note that this is just a *mirror* - we don't work with pull requests on github. To contribute, please see https://wiki.postgresql.org/wiki/Submitting_a_Patch
HikariCP - 光 HikariCP・A solid, high-performance, JDBC connection pool at last.
AdventureWorks-for-Postgres - Set up the AdventureWorks sample database for use with Postgres