| |
| 🔗 Stories, Tutorials & Articles |
| |
|
| |
| 14x Faster Faceted Search in PostgreSQL with ParadeDB |
| |
| |
ParadeDB brings Elasticsearch-style faceting to PostgreSQL, ranked search results and filter counts, all in one shot. No extra passes.
It pulls this off with a custom window function, planner hooks, and Tantivy's columnar index under the hood. That's how they’re squeezing out 10×+ speedups on hefty datasets.
System shift: Structured SQL and unstructured full-text search now run in the same query. That’s not just faster, it changes how folks wire up search in relational stacks. |
|
| |
|
| |
|
| |
| Use Python for Scripting! |
| |
| |
Shell scripts love to break across macOS and Linux. Blame all the GNU vs BSD quirks; sed, date, readlink, take your pick. The mess adds up fast, especially in build pipelines and CI systems.
This post makes the case for a cleaner way: Python 3. Standard library. Predictable behavior. Same results whether it's Ubuntu, Arch, or some stubborn MacBook in QA. |
|
| |
|
| |
|
| |
| How We Migrated DB 1 to DB 2 , 1 Billion Records Without Downtime |
| |
| |
A team moved over 1 billion production records, no downtime, no drama. The stack: dual writes, Kafka retries, and idempotent inserts to keep it clean.
They ran shadow reads to sniff for errors, chunked the transfers with checksums, and held off indexing to keep inserts fast. Caches got warmed early to dodge cold start thrash. |
|
| |
|
| |
|
| |
| How Reddit Migrated Comments Functionality from Python to Go |
| |
| |
| Reddit successfully migrated its monolithic, high-traffic Comments service from legacy Python to modern Go microservices with zero user disruption. This was achieved by using a "tap compare" for reads and isolated "sister datastores" for writes, ensuring safe verification of the new code against production data. Despite challenges like cross-language serialization and database race conditions, the migration succeeded, resulting in a dramatic reduction in p99 latency for all write operations. . |
|
| |
|
| |
|
| |
| Guarding My Git Forge Against AI Scrapers |
| |
| |
To stop a wave of scraping on their self-hosted Forgejo, the author stacked defenses like a firewall architect on caffeine. First came manual IP rate-limiting. Then NGINX caching and traffic shaping. Finally: Iocaine 3.
That last one didn’t just block bots, it lured them into a maze of junk pages. The Nam-Shub-of-Enki module spun up auto-generated nonsense and rerouted bad actors straight into it. Think bot honeypot meets digital oubliette.
Caching flopped, requests were too random to reuse. Only Iocaine held the line, tagging fingerprints, filtering by ASN, and slashing CPU burn, bandwidth, and power draw.
System shift: Bot scraping keeps evolving. Defenders now need smarter, per-request detection and dynamic responses, especially for open-facing infra. Bot traffic isn't obvious anymore. It's organized. |
|
| |
|
| |
|
| |
| How We Saved 70% of CPU and 60% of Memory in Refinery’s Go Code, No Rust Required. |
| |
| |
Refinery 3.0 cuts CPU by 70% and slashes RAM by 60%. The trick: selective field extraction from serialized spans. No full deserialization. Fewer heap allocations. Way less waste.
It also recycles buffers, handles metrics smarter, and is gearing up to parallelize its core decision loop. |
|
| |
|
| |
|
| |
| SQLite JSON Superpower: Virtual Columns + Indexing - DB Pro Blog |
| |
| |
SQLite’s JSON virtual generated columns punch way above their weight. They let you index JSON fields on the fly, no migrations, no whining. Computed like real columns, queryable like real columns, indexable like real columns. But from JSON.
Want flexibility without surrendering speed? This flips the script. Skip the schema stress and still get fast queries. |
|
| |
|
| |
|
| |
| Phishing for AWS Credentials via the New 'aws login' Flow |
| |
| |
AWS rolled out a new aws login CLI command using OAuth 2.0 with PKCE. It grabs short-lived credentials, finally pushing out those dusty long-lived access keys.
But here’s the hitch: The remote login flow opens up a phishing gap. Since the CLI session and browser session aren’t bound, attackers could spoof the flow and dodge phishing-resistant MFA.
Why it matters: Ephemeral creds are a win for security. But without tighter session binding and clear user guidance, this move leaves an open flank. AWS is raising the bar, but teams will need to follow suit. |
|
| |
|
| |
👉 Got something to share? Create your FAUN Page and start publishing your blog posts, tools, and updates. Grow your audience, and get discovered by the developer community. |
