http-proxy
edgedb
Our great sponsors
http-proxy | edgedb | |
---|---|---|
14 | 19 | |
13,728 | 12,236 | |
0.4% | 1.2% | |
0.0 | 9.9 | |
6 days ago | 2 days ago | |
JavaScript | Python | |
GNU General Public License v3.0 or later | 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.
http-proxy
-
Is there a way to accept incoming http but outgoing must be https?
Take a look at https://github.com/http-party/node-http-proxy , specifically their .web() helper
-
HTTPS proxy setup with response modification
I have been tasked with writing a proxy server that takes a clients requests and forwards it to a target server (normal proxy stuff). The client and the target are out of my control. The only change in the client is that the its requests to the proxy server instead of the target. Now, what I need to do is modify the response from target because the client expects it in a certain format and the server responds with a different format. I have a working implementation using http-proxy (https://github.com/http-party/node-http-proxy) that works over HTTP . But I need it to work over HTTPS, I can't make much sense of the documentation and I can't find any additional resources on how HTTPS can be implemented. The client-proxy and proxy-target connection both need to be encrypted(HTTPS). I found solutions using different tools but they mostly seem to be encrypted end to end, so the proxy can't read the response data(I need to be able to modify it). Any ideas on how I can do this?
-
what's the stack for this application?
What you're describing is a proxy server. If you wanted to use Node.js check out https://github.com/http-party/node-http-proxy. Notice that the examples there just forward the req though which potentially has identifying information like cookies, so you'll need to rework to anonymize. Should be straightforward.
- What libraries should I use to map multiple ports into a single one with node.js?
-
GraphQL is now available on Supabase
There's several ways to have a blog path contain a separate setup from the marketing/product routes.
One is to run a reverse proxy on the root domain to pull in separate routes for various services.
https://github.com/http-party/node-http-proxy
You can do rewrites at the server level for the root domain
Or if the app on the root domain can do the routing for you (have done this before with a Rails app)
- Launch HN: Requestly (YC W22) – Network debugging proxy for web and mobile
-
Creating and deploying a tiny proxy server on Vercel in 10 minutes
Check the documentation of the http-proxy-middleware library (and of the node-http-proxy library, used under-the-hood) to learn how you can manipulate the proxied request & response.
-
How to create a simple forward proxy
Relevant node-http-proxy issue: https://github.com/http-party/node-http-proxy/issues/230
- The history and reasons behind CORS, and how to use it
-
Heroku equivalent/alternative to editing local hosts file?
I'm running Node app in Heroku which is using node-http-proxy, and I've given my Heroku app the domain "example.com"
edgedb
- EdgeDB – A graph-relational database with declarative schema
-
Beyond SQL: A relational database for modern applications
A new DB, with a new query language that's like "SQL done right"? This immediately reminded me of EdgeDB: https://edgedb.com/
Is there anyone here who knows enough about these two products to do a compare/contrast?
-
EdgeDB 3.0
The whole thing consists of these main parts:
1. SQL parser: https://github.com/edgedb/edgedb/tree/master/edb/pgsql/parse...
-
DuckDB 0.8.0
>relational no-sql
Do you mean something like edgeDB?[0]
Or do you mean some non-declarative language completely? I don't see the latter making much sense. The issue with SQL for me is the "natural language" which quickly loses all intended readabilty when you have SELECT col1, col2 FROM (SELECT * FROM ... WHERE 1=0 AND ... which is what edgeDB is trying to solve.
-
Question about custom properties querying with the query builder
We need to land #3747, then something like this should work
- EdgeDB 2.0
-
GraphQL Is a Trap?
You have to do your own optimiser to avoid, for instance, the N+1 query problem. (Just Google that, plenty of explanations around.) Many GraphQL frameworks have a “naive” subquery implementation that performs N individual subqueries. You either have to override this for each parent/child pairing, or bolt something on the back to delay all the “SELECT * FROM tbl_subquery WHERE id = ?” operations and convert them into one “… WHERE id IN (…)”. Sounds like a great use of your time.
In the end you might think to yourself “why am I doing this, when my SQL database already has query optimisation?”. And it’s a fair question, you are onto it. Try one of those auto-GraphQL things instead. EdgeDB (https://edgedb.com) does it as we speak, runs atop Postgres. Save yourself the enormous effort if you’re only building a GraphQL API for a single RBDMS, and not as a façade for a cluster of microservices and databases and external requests.
Or just nod to your boss and go back to what being a backend developer has always meant: laboriously building by hand completely ad hoc JSON versions of SQL RBDMS schemas, each terribly unhappy in its own way. In no way does doing it manually but presenting GraphQL deviate from this Sisyphean tradition.
I read in the article that NOT having GraphQL exactly match your DB schema is a best practice. My response is “did a backend developer write this?”
-
How we sharded our test suite for 10x faster runs on GitHub Actions
Same idea, yeah. Unfortunately, in our case we couldn't use pytest due to complicated test setup, so we used a customized unittest runner instead.
-
GraphQL is now available on Supabase
EdgeDB [1] has indeed a rich GraphQL layer, but it's a very different project.
While it also builds on top of Postgres, EdgeDB replaces the entire relational database front-end. EdgeDB features a SQL replacement language called EdgeQL (analytical capabilities of SQL married with deep-fetching in GraphQL), a higher-level data model (tables -> object types), integrated migrations engine, a custom protocol with great performance & great client APIs, and many other things. Read more here [2].
(disclaimer: I'm EdgeDB co-founder)
-
EdgeDB 1.0
I'm curious how this squares up with what someone linked elsewhere: https://github.com/edgedb/edgedb/discussions/3403
> EdgeDB does not treat Postgres as a simple standard SQL store. The opposite is true. To realize the full potential of the graph-relational model and EdgeQL efficiently, we must squeeze every last bit of functionality out of PostgreSQL's implementation of SQL and its schema.
This would seem to be an opposing view of how coupled EdgeDB and PostgreSQL are. Which is it?
What are some alternatives?
axios - Promise based HTTP client for the browser and node.js
supabase - The open source Firebase alternative.
ky-universal - Use Ky in both Node.js and browsers
cockroach - CockroachDB - the open source, cloud-native distributed SQL database.
node-fetch - A light-weight module that brings the Fetch API to Node.js
neon - Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, branching, and bottomless storage.
gh-got - Convenience wrapper for Got to interact with the GitHub API
Prisma - Next-generation ORM for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB and CockroachDB
Nock - HTTP server mocking and expectations library for Node.js
supabase-graphql-example - A HackerNews-like clone built with Supabase and pg_graphql
got - 🌐 Human-friendly and powerful HTTP request library for Node.js
edgedb-rust - The official Rust binding for EdgeDB