window.fetch polyfill
gh-ost
Our great sponsors
window.fetch polyfill | gh-ost | |
---|---|---|
25 | 32 | |
25,806 | 11,997 | |
0.0% | 1.0% | |
7.9 | 7.4 | |
about 22 hours ago | 11 days ago | |
JavaScript | Go | |
MIT License | MIT License |
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.
window.fetch polyfill
-
How do I detect requests initiated by the new fetch standard? How should I detect an AJAX request in general?
Most js libraries use XMLHttpRequest and so provide HTTP_X_REQUESTED_WITH: XMLHttpRequest, but neither Chrome's implementation nor Github's polyfill of the new fetch uses a similar header. So how can one detect that the request is AJAX?
-
Stop polyfilling fetch in your npm package
In this case, Github offers a great fetch polyfill for browsers: https://github.com/github/fetch
- What is happened to github official fetch repository? Recently opened issues are don't seem human-written.
- oh mah Gawd!
-
jQuery 3.6.2 Released
You can polyfill fetch() if that's a concern:
https://github.com/github/fetch
- Is this possible?
- The impact of removing jQuery on our web performance
- fetch patch request is not allowed
- What is the difference between isomorphic-fetch and fetch?
-
Fetch: reject promise and catch the error if status is not OK?
I'm using this fetch polyfill in Redux with redux-promise-middleware.
gh-ost
- "At GitHub we do not use foreign keys, ever, anywhere"
-
How Modern SQL Databases Are Changing Web Development - #3 Better Developer Experience
I’ve been through multiple incidents where everything worked fine in the testing environment but ended up locking the production database for minutes when deployed. A category of open-source tools called OSC (Online Schema Change) exists to mitigate such pain, like gh-ost used by GitHub and OSC used by Meta. They work by creating a set of "ghost tables" to apply the migrations, copy over old data from the original tables, and catch up with new writes simultaneously. When all old data is migrated, you can trigger a cutover to make the "ghost tables" production. Check the post below for a great introduction and comparison:
-
We migrated to SQL. Our biggest learning? Don't use Prisma
Sounds like it's basically explained in the gh-ost readme https://github.com/github/gh-ost#how
I think it amounts to "use views to decouple access to the table with a fixed interface" and "use triggers for migrating data between tables"
-
Ask HN: Is PostgreSQL better than MySQL?
Gh-ost is the new hotness. Simple to use and lots of great features: https://github.com/github/gh-ost
-
My Green/blue AWS db deployment strategy for avoiding data loss due to table locks
If the performance of the db is a concern during migrations (locking, high cpu consumption for large writes) there are tools that can help and do similiar to what your describing but with the benefit that they are battle tested tools. This one spring to mind https://github.com/github/gh-ost there are other options as well and its worth reading the trade off docs
-
Changing column from longtext to mediumtext taking over 2 hours
Not sure which version of MySQL you're using, but one approach would be to use a tool like pt-online-schema-change (from Percona) or g-host -- which will create a duplicate table and then swap it in place of the original table. It's a safer approach when operating in production environments. Here's a good comparison of the tools many people use https://planetscale.com/docs/learn/online-schema-change-tools-comparison
-
Ask HN: Do you use foreign Keys in Relational Databases
No, especially on large tables with billions of records. They make online schema changes impossible. More details: https://github.com/github/gh-ost/issues/331#issuecomment-266...
-
Migrating a production database without any downtime
Tip #4: Consider slow-running migrations. Some tables can be so large that the traditional migration way is simply not a viable option for them. In such cases, you can consider embedding the data migration code right into your application, or use a special utility like GitHub's online schema migration for MySQL. A slow-running migration can work in production for days or even weeks. It gradually converts the data by small chunks, so you can carefully balance the load on the database while making sure that it doesn't cause slowness or downtime.
-
How do you handle RDS schema migrations?
GitHub gh-ost
-
Changing Tires at 100mph: A Guide to Zero Downtime Migrations
Actually I never tried but I was scared by the small print of GH not using RDS themselves [1] and Ghost relying on lower-level features that might be not easily available in RDS. Also I had the impression you have to setup a normal non-RDS replica attached to your RDS master?
[1] https://github.com/github/gh-ost/blob/master/doc/rds.md
What are some alternatives?
axios - Promise based HTTP client for the browser and node.js
pg-online-schema-change - Easy CLI tool for making zero downtime schema changes and backfills in PostgreSQL [Moved to: https://github.com/shayonj/pg-osc]
node-fetch - A light-weight module that brings the Fetch API to Node.js
doctrine-test-bundle - Symfony bundle to isolate your app's doctrine database tests and improve the test performance
request - 🏊🏾 Simplified HTTP request client.
squawk - 🐘 linter for PostgreSQL, focused on migrations
superagent - Ajax for Node.js and browsers (JS HTTP client). Maintained for @forwardemail, @ladjs, @spamscanner, @breejs, @cabinjs, and @lassjs.
pg_squeeze - A PostgreSQL extension for automatic bloat cleanup
Nock - HTTP server mocking and expectations library for Node.js
hub - A command-line tool that makes git easier to use with GitHub.
fetch - A Fetch API wrapper
Jenkins - Jenkins automation server