HN user

ConnorLeet

34 karma
Posts0
Comments29
View on HN
No posts found.

Plenty of guys complaining about dating on TikTok too. It’s an absolutely massive platform and there’s videos on just about anything especially interpersonal relationships (coach industry)

Do you have any resources to point me towards that elaborate on the benefits of a process-per-tenant/user for performance?

I work on a data-intensive app that fits the use-case you describe but I'm confused about the benefits for performance. (can certainly see how the code would end up nice/simpler) Is this mostly applicable to certain stacks?

Possessing an ID, shouldn’t give access, regardless of whether it’s a numerical PK or a UUID. (Unless that’s a feature, like shareable links) Still need to check if the user should be able to use that ID.

If that isn’t implemented, the system isn’t secure, doesn’t matter which path you use.

Do you have any resources or examples of challenges with scaling up a shared-nothing architecture? At the crossroads between a shared-nothing and shared disk decision at the moment.

How many op/s was that? Bytes/s? Just curious because I was involved in migrating a write-heavy service off of C* to SQL Server. Our writes have higher latency now, but using managed SQL is worth it. (much cheaper too)

If the whole crypto ecosystem crashes (unlikely in my opinion) graphics cards can be resold and recoup losses.

Yes.

The thing for me is that is fulfilling, is the talented and genuine people I work with, and from doing the best work I can.

People always talk about how fulfillment coming from "Changing the world," and helping people, but really if you mesh with the people - that's fulfilling enough for me!

Why LINQ beats SQL 9 years ago

Array.reduce(), Array.filter(), Array.map(), in JavaScript are pretty LINQ-ish if you ask me!