Querydsl
Logflare
Querydsl | Logflare | |
---|---|---|
6 | 11 | |
4,575 | 778 | |
0.5% | 1.3% | |
4.1 | 9.8 | |
3 days ago | about 14 hours ago | |
Java | Elixir | |
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.
Querydsl
-
PostgreSQL Is Enough
There is a bit of tooling needed but is already around. For Java for example I had very good experience with a combination of flyway [1] for migrations, testcontainers [2] for making integration tests as easy as unit tests and querydsl [3] for a query and mapping layer.
[1] https://github.com/flyway/flyway
[2] https://java.testcontainers.org/modules/databases/postgres/
[3] https://github.com/querydsl/querydsl
-
Apache Empire-Db: Full SQL Freedom for Java
http://querydsl.com/ also seems similar
-
Useful & Unknown Java Libraries - Piotr's TechBlog
As for JPA: I cannot miss the QueryDSL library for building typesafe queries. Another interesting alternative is Jinq, that provides a java stream api to query entities.
-
You might not need an ORM
> all I really want is a nice API for building queries (that actually supports all underlying database features) and automatic mapping of the results to whatever objects/structs and primitives the language supports.
For Java based solutions, check out https://www.jooq.org/ or http://querydsl.com/
-
How do access sql through java in the real world?
QueryDsl -- http://querydsl.com
- How to build SQL query strings?
Logflare
-
PostgreSQL Is Enough
btw recently cleaned up my wal cache busting code quite a bit if you're interested.
https://github.com/Logflare/logflare/blob/main/lib/logflare/...
Need to make a lib out of this!!
-
Migrating from Supabase
hey hn, supabase ceo here
the Val Town team were kind enough to share this article with me before they released it. Perhaps you know from previous HN threads that we take customer feedback very seriously. Hearing feedback like this is hard. Clearly the team at Val Town wanted Supabase to be great and we didn’t meet their expectations. For me personally, that hurts. A few quick comments
1. Modifying the database in production: I’ve published a doc on Maturity Models[0]. Hopefully this makes it clear that developers should be using Migrations once their project is live (not using the Dashboard to modify their database live). It also highlights the options for managing dev/local environments. This is just a start. We’re building Preview Databases into the native workflow so that developers don’t need to think about this.
2. Designing for Supabase: Our goal is to make all of Postgres easy, not obligatory. I’ve added a paragraph[1] in the first page in our Docs highlighting that it’s not always a good idea to go all-in on Postgres. We’ll add examples to our docs with “traditional” approaches like Node + Supabase, Rails + Supabase, etc. There are a lot of companies using this approach already, but our docs are overly focused on “the Supabase way” of doing things. There shouldn’t be a reason to switch from Supabase to any other Postgres provider if you want “plain Postgres”.
3. That said, we also want to continue making “all of Postgres” easy to use. We’re committed to building an amazing CLI experience. Like any tech, we’re going to need a few iterations. W’re building tooling for debugging and observability. We have index advisors coming[2]. We recently added Open Telemetry to Logflare[3] and added logging for local development[4]. We’re making platform usage incredibly clear[5]. We aim to make your database indestructible - we care about resilience as much as experience and we’ll make sure we highlight that in future product announcements.
I’ll finish with something that I think we did well: migrating away from Supabase was easy for Val Town, because it’s just Postgres. This is one of our core principles, “everything is portable” (https://supabase.com/docs/guides/getting-started/architectur...). Portability forces us compete on experience. We aim to be the best Postgres hosting service in the world, and we’ll continue to focus on that goal even if we’re not there yet.
[0] Maturity models: https://supabase.com/docs/guides/platform/maturity-model
[1] Choose your comfort level: https://supabase.com/docs/guides/getting-started/architectur...
[2] Index advisor: https://database.dev/olirice/index_advisor
[3] Open Telemetry: https://github.com/Logflare/logflare/pull/1466
[4] Local logging: https://supabase.com/blog/supabase-logs-self-hosted
[5] Usage: https://twitter.com/kiwicopple/status/1658683758718124032?s=...
-
How to get access logs from Cloudflare?
https://logflare.app/ is awesome, pipes into BiqQuery and is really easy to use and WAY cheaper than logpush. Depending on the amount of traffic, it's only a few dollars a month.
-
Supabase Logs: open-source logging server
hey hn, supabase ceo here
this one is a long-time coming and it's a continuation of our acquisition of Logflare[0]. Since the acquisition we've be open-source-ing the server, which you can find here: https://github.com/Logflare/logflare
Logflare handles about 1.5 billion log-events everyday on supabase. It's built with Elixir and has no problems with that workload.
This is really just the start of the Logflare updates. All logs are currently ingested into BigQuery, and we are adding support for Clickhouse and other OLAP backends. Over time this will function very much like an open source Sentry alternative, where you can ingest data from various sources.
The team will be around if you have any questions about the technical implementation
[0] acquision: https://supabase.com/blog/supabase-acquires-logflare
-
Supabase Logs: open source logging server
Logflare was available under a BSL license prior to joining Supabase. We’ve since changed the license to Apache 2.0, aligning it with our open source philosophy.
-
Logging requests with cloudflare
https://www.cloudflare.com/apps/logflare https://logflare.app/
-
Tools for Querying Logs with SQL
Logflare, now a part of Supabase, aims to streamline the logging experience for Cloudflare-, Elixir-, and Vercel-based applications. However, it can be adapted to support any type of log. Logflare provides structured logging ability without limits or added latency. It aims to provide the best performance with minimal overhead when processing logs for supported application platforms.
What are some alternatives?
jOOQ - jOOQ is the best way to write SQL in Java
Hydra - Open source API gateway with integrated cache and data transformations.
JDBI - The Jdbi library provides convenient, idiomatic access to relational databases in Java and other JVM technologies such as Kotlin, Clojure or Scala.
n2o - ⭕ N2O: Distributed WebSocket Application Server ISO 20922
Jinq - LINQ-style queries for Java 8
Phoenix Toggl - Toggl tribute done with Elixir, Phoenix Framework, React and Redux.
Apache Hive - Apache Hive
ExChat - (Not maintaining) A Slack-like app by Elixir, Phoenix & React(redux)
Spring Data JPA - Simplifies the development of creating a JPA-based data access layer.
Phoenix Battleship - The Good Old game, built with Elixir, Phoenix, React and Redux
Presto - The official home of the Presto distributed SQL query engine for big data
majremind