Render

ReadMe powers the API documentation for 5000+ companies with only 20 engineers. Of those 20, only 1 engineer—Ryan Park—focuses on infrastructure. A big source of leverage is the managed services they build upon, including Render. Learn why, after 8 years on Heroku, ReadMe chose to migrate to Render—and how they did it with under 2 minutes of downtime: https://lnkd.in/eHaCtCrz

Want to speed up your DB queries? 3 useful tools & concepts: 🔎 `EXPLAIN` and `EXPLAIN ANALYZE` 🛠️ Join algorithms 🎨 PEV2 These helped us debug and fix a slow query taking *hours* to run. Steps we took: 1️⃣ Get the shape / scale of the data 2️⃣ Draw a picture of the problem 3️⃣ Use `EXPLAIN` and `EXPLAIN ANALYZE` to see the query plan, PEV2 to visualize 4️⃣ Use knowledge of join algos to form a hypothesis 5️⃣ Understand + use stats — see our full post for details Full story from Render engineer Eric Fritz: 👉 https://lnkd.in/emPbrXni #postgres #postgresql #debugging

At Render, we highlight exceptional stories from customers at every stage of growth—from idea to scaling enterprise. Discover how Propeller Digital, a 7-person eCommerce agency, switched to self-hosting on Render after a site they built degraded due to high traffic. In just a week, they migrated to an auto-scaling Medusa instance hosted on Render. This move solved the problem, secured a future pricing advantage, and led the agency to change a core philosophy. Read more in our latest post: https://lnkd.in/gVqapy3t

This month, Render engineer Eric Liu migrated the Sveld open source library from Yarn/Vitest to Bun. Deploys sped up 2x. Code became more readable. See the speed breakdowns, code diffs, and migration steps in his post. Then try out Render’s native Bun support! https://lnkd.in/eZXtANKa

You can now deploy Render services to Virginia (US East)! Eager to migrate from Heroku to Render but need to stay in Virginia? Now's your chance. Virginia's in early access while it cools from the oven, but it's feature-complete and available to everyone. https://lnkd.in/gZX49GFa

We've shipped powerful new networking and compute metrics for your Render services: • CPU, RAM, and disk usage for each instance • HTTP request volume, segmented by response code • Custom time ranges with drag-to-zoom • For teams: HTTP response latency, plus filtering by request path/domain There's a lot to see! Take a tour of the new Metrics page in your dashboard, or on our blog: https://lnkd.in/g_AWi2ch

We've added a couple handy features for Render Blueprints, our Infrastructure-as-Code model: 1) You can now generate a render.yaml file from your existing services to start managing them with a Blueprint (or to quickly replicate your infrastructure) 2) Most popular IDEs now support automatic validation for render.yaml files. Catch syntax hiccups before you sync your Blueprint, not after. If you're new to Render Blueprints (or Infrastructure-as-Code), see what they're all about: https://lnkd.in/guiPgKxq

Render now supports Bitbucket! 🪣 Connect your Bitbucket repository and start shipping with automatic deploys, service previews, and native language runtimes.

With new protected environments, only team admins can perform potentially destructive actions, such as deleting services or modifying environment variables. More in the docs: https://lnkd.in/gu6G74E5 And check out how we implemented these role-based controls using Go generics: https://lnkd.in/g9jxAwPQ

This February, a simple query blocked our staging pipeline: ``` SELECT e.id FROM events e JOIN postgres_dbs db ON (e.data ->> 'serviceId') = db.database_id LIMIT 1; ``` ✅ Both sides of the join had relevant indexes. ✅ The query had a `LIMIT 1`. 🤔 It still took hours to run. Learn, step-by-step from Render engineer Eric Fritz, how we tracked down and fixed this query: 🔎 https://lnkd.in/e2sH2dP2 (If you have a hypothesis already… we're hiring 😉: https://lnkd.in/esFShvV3)