r2dbc-postgresql
sql-task-queue
r2dbc-postgresql | sql-task-queue | |
---|---|---|
4 | 1 | |
986 | 10 | |
0.3% | - | |
7.6 | 10.0 | |
26 days ago | over 4 years ago | |
Java | PLpgSQL | |
Apache License 2.0 | Apache License 2.0 |
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.
r2dbc-postgresql
-
Reactive Backend Applications with Spring Boot, Kotlin and Coroutines (Part 1)
Now that we have an application, let's turn it into a reactive application. For this, we will replace Spring Web dependency with Spring WebFlux, Spring Data JPA with Spring Data R2DBC. We will also add R2DBC dependency for our H2 database. R2DBC works with a reactive driver so it will integrate nicely with the rest of our application to allow us database access in a non-blocking way.
- Reactive db drivers (r2dbc)
-
I need to create an API, but I don't know what framework to use. What would you choose, of you were me, and scalability is a quite important factor?
However, if you really expect a lot of users (especially concurrent ones) to use your API, you should delve into the world of reactive programming. Use tools like RxJS (JS/TS) or Project Reactor (Java) in such a case, preferably in combination with a broker like Kafka or RabbitMQ. R2DBC is also great for a data store. Then of course if you want to go one step further, there also exists the less popular but very interesting Actor model which Akka easily has ported into Java.
- Postgres is a great pub/sub and job server
sql-task-queue
-
Postgres is a great pub/sub and job server
> This is fantastic for relatively low volume queues with intensive work to be done by a small number of workers. For these types of use cases, I'll take this approach over RabbitMQ or Kafka all day long.
That’s what our workload is like for our SaaS code analysis platform. We create a few tasks (~10 max) for every customer submission (usually triggered by a code push). We replaced Kafka with a PostgreSQL table a couple of years ago.
We made the schema, functions, and Grafana dashboard open source [0]. I think it’s slightly out-of-date but mostly the same, and has been running perfectly.
[0] https://github.com/ShiftLeftSecurity/sql-task-queue
What are some alternatives?
worker - High performance Node.js/PostgreSQL job queue (also suitable for getting jobs generated by PostgreSQL triggers/functions out into a different work queue)
realtime - Broadcast, Presence, and Postgres Changes via WebSockets
dramatiq - A fast and reliable background task processing library for Python 3.
walex - Postgres change events (CDC) in Elixir
pg-boss - Queueing jobs in Node.js using PostgreSQL like a boss
reactive-kotlin-weather-api
dramatiq-pg
Que - A Ruby job queue that uses PostgreSQL's advisory locks for speed and reliability.
sorg - A Go-based static site generator that compiles brandur.org.