ryan14975

The coupling concern is valid but I think it's the right trade-off for most CRUD apps. In practice, 80% of your endpoints are thin wrappers around your models anyway. The remaining 20% where you need separate request/response schemas — you just write those by hand.

The auto-generated admin panel is a nice touch. That alone saves days on internal tooling.

Using MCP daily through Claude Code for browser automation and external APIs. The protocol works — the tooling around it is what needs to mature.

Biggest pain point is reliability: connections drop, tools fail silently, no good way to know if a call actually reached the server.

But the article's "just HTTP with extra steps" framing misses the point. The value is the standardized tool interface. Before MCP, every AI integration was a bespoke wrapper. A shared vocabulary for "here's a tool, here's its schema, call it" is genuinely useful, rough edges and all.

Solo founder here, currently marketing a niche developer tool (ZIP API for cloud storage). Sharing what I've learned in the first two weeks:

The "post everywhere" strategy doesn't work. I tried posting on Reddit with links to my product — comments got silently filtered by AutoMod. Even linking to a Dev.to article got flagged as a banned domain on r/cloudflare. You can't even tell your stuff is invisible unless you check in a private window.

What's actually working (slowly): answering real questions in subreddits where my users hang out, with zero self-promotion. One genuine technical answer on r/cloudflare got 5 upvotes. That's more signal than any launch post.

The hardest part isn't building the product — it's accepting that marketing is a months-long trust-building exercise, not a launch event.

One underappreciated reason DEFLATE/gzip persists: it's streaming-friendly. You can emit compressed bytes incrementally without buffering the entire input. BWT-based algorithms (bzip2) need the whole block in memory before the transform can run.

This matters a lot for formats like ZIP, where the archive is constructed on-the-fly. You can pipe data through DEFLATE and compute CRC32 as you go, writing headers retroactively via Data Descriptors. Try that with bzip2 and you're stuck buffering 900KB blocks before you can output anything.

zstd threading and framing are a step forward here, but DEFLATE's simplicity and tiny memory footprint (~32KB window) make it hard to kill in constrained or streaming contexts.

Similar principle applies to server-side constraints. I run a file processing API on Cloudflare Workers with 128MB RAM — no filesystem, no disk. Had to build a fully streaming ZIP64 archiver that never buffers more than a few KB at a time. It's processed 10TB+ of data so far.

Constraints like DuckDB targeting the cheapest MacBook or Workers' 128MB limit force you into better architectures. You end up with streaming pipelines instead of "load everything into memory" approaches, which scale better regardless of hardware.

The settings.json allowlist gives you exactly this kind of granularity. You can permit specific tool patterns like Read, Glob, Grep, Bash(git *) while keeping destructive operations gated. It's not as discoverable as a CLI flag but it's been working well for me for unattended sessions.

The interesting technical detail here is that this runs on Workers. Cloudflare's been quietly building out a full compute-at-edge stack — Workers, R2, D1, Queues — and a crawl endpoint fits naturally into that. You can now chain a crawl → process → store pipeline entirely within their network with zero egress.

Whether that level of vertical integration is healthy for the web is a separate debate, but from a pure infrastructure perspective, it's a compelling model.

This makes a lot of sense. Cloudflare already has the rendered content at edge — serving a structured snapshot from cache would eliminate redundant crawling entirely.

What I'd love to see is site owners being able to opt in and control the format. Something like a /cdn-cgi/structured endpoint that respects your robots.txt directives but gives crawlers clean markdown or JSON instead of making them parse raw HTML. The site owner wins (less bot traffic), the crawler wins (structured data), and Cloudflare wins (less load on origin).

Eazip (https://eazip.io) — ZIP remote files in one API call.

I built a service that lets developers bundle remote files into a ZIP with a single POST request. You send a list of URLs, we fetch, package, and return a signed download link.

The problem: creating ZIPs from remote files (S3, R2, CDN) usually means downloading to a server, zipping locally, managing temp storage, and cleaning up. It's surprisingly painful at scale — especially with large files or thousands of items.

Eazip handles all of that. ZIP64 support for files over 4GB, up to 5,000 files per job, zero egress fees on downloads, and no infrastructure to manage.

Use cases so far: e-commerce photo bundles, document delivery (invoices/contracts), creative asset distribution, and backup/export tooling.

Free tier available, no credit card required. Would love feedback from the HN community.