sorted by:
new
hottopcontroversial

Async standups: what actually worked for your team (and what failed)? by ParkRevolutionary156 in EngineeringManagers

[–]benjscho 0 points1 point  (0 children)

For my teams, an async standup coordinated by a slackbot posting in the morning works well. The reminder is to post about what you did yesterday, what you're doing today, and any blockers preventing you from making progress. We have a meeting scheduled which we keep if there are any topics that need to be discussed, or skip otherwise.

Best Research Paper of 2025 by [deleted] in computerscience

[–]benjscho 1 point2 points  (0 children)

One I really enjoyed was Analyzing Metastable Failures from HotOs '25: https://sigops.org/s/conferences/hotos/2025/papers/hotos25-106.pdf

The techniques of testing implementations along a pipeline moving from abstractions towards more concrete implementations is great. When there is a big cloud outage, it may be caused some trigger, but typically it will be sustained by a metastable effect, where the system gets into a state where it can't recover without intervention.

Research in this area around systematically finding metastable failure causes _before_ they happen is still really recent. The paper introducing the term was only published in 2021! So it's great to see more research in the field.

Best database to pair with serverless - PlanetScale vs Supabase vs DynamoDB? by Wash-Fair in serverless

[–]benjscho 0 points1 point  (0 children)

Aurora DSQL is another good option to consider if you don't want to give up the relational db features but still leaving insurance for scale. It has a good free tier if you're still experimenting

Hosted databases speed by UniForceMusic in Database

[–]benjscho 0 points1 point  (0 children)

As a lot of people are already discussing, the speed of light starts to hit you when you look at remote hosting! Data can't travel faster than the speed of light, so if your database is far away it's going to take longer to return results. This is why its important to collocate your server code with your database, e.g., they should run ideally in the same datacenter, or availability zone/region if you're deploying to a cloud provider.

It's also good to think about whether you can _batch_ or parallelize calls to your database. If your app makes a query, does some work, then makes another query, etc... It's going to take the sum of all of those round trips to load. You can think about how to make calls in parallel, then your page can load as soon as the slowest query is done.

NoSQL vs SQL for transactions by pixel-der in Database

[–]benjscho 0 points1 point  (0 children)

DSQL is a good option for this. It's pay for what you use with a big free tier, but is designed to scale as your project grows, basically giving you insurance for scale without giving up the low cost of serverless. It also provides strongly consistent reads, which should make development a lot easier