jupp0r

10 ms·

91.
by jupp0r 2y ago
95% of this is specific to Ruby, not GraphQL. I also found ruby-graphql not to be a excellent library in contrast to what the author says. Other implementations (apollo for node, gqlgen for Go) alleviate many of the concerns mentioned in th
92.
by jupp0r 2y ago
Have you ever wondered why you don't have to login when you go from photos.google.com to docs.google.com?
93.
by jupp0r 2y ago
Yes. It's super common for SaaS companies that are <1% the size of Google to have infrastructure in multiple regions.
94.
by jupp0r 2y ago
Assumptions you are making: * everything is located physically close together (good luck reading from a DB table in Singapore from a service in Europe for every request) * you have few enough client services that want to do this that the nu
95.
by jupp0r 2y ago
Ever heard of speed of light? If you really think that "just connect to the same db" was an easy solution to the problem you describe in the general sense then you haven't done so in a moderately complex system yet. It can be
96.
by jupp0r 2y ago
Or just have infrastructure that needs to validate the session in different parts of the continent (world).
97.
by jupp0r 2y ago
I would challenge your assumption. Unless you absolutely need to have 100% durable, consistent revocations for some reasons, something like memcached is perfect here as the worst case scenario in case of a failure is a slight, temporary deg
98.
by jupp0r 2y ago
"If we're talking about a web session, time-limited randomly-generated session tokens that are stored in a DB still work fine. If you really need it, put a caching layer (memcached or redis or valkey or whatever) in front of it. Y
99.
by jupp0r 2y ago
"have a distributed cache of JWTs that have been revoked. The nice thing about JWTs is that they expire, so you can sweep your cache and drop tokens that have expired every night or whenever." Every cache has TTL, so you just set
100.
by jupp0r 2y ago
70% of the web is Wordpress, so yeah.
101.
by jupp0r 2y ago
The notion that you have Google/Facebook scale problems at 10k requests per second (vs 10s of millions of requests per second) is a pretty funny claim in its own right.
102.
by jupp0r 2y ago
My impression is that the article author is following the good old "everything lives in my Rails monolith" philosophy from 10 years ago where login and authn is just another library including db migrations that you slap onto your
103.
by jupp0r 2y ago
It's pretty rare in practice to be able to make authz decisions solely based on the information in JWT claims. Space in HTTP headers is limited and any moderately complex system will have a separate authz concept anyways that can be us
104.
by jupp0r 2y ago
"Just use the normal session mechanism that comes with your web framework and that you were using before someone told you that Google uses jwt. It has stood the test of time and is probably fine." You don't need to be Faceboo
105.
by jupp0r 2y ago
The question is completely meaningless and impossible to answer unless you specify what exactly you mean when you say "performance". Operating systems do lots of things, including in userspace. The answer to your question could be
106.
by jupp0r 2y ago
Egypt may well believe that (and others have rightfully pointed out that not following UN conventions for refugees is outside of the jurisdiction of the ICC), but I don't think there is a plausible case to be made that refusing to help
107.
by jupp0r 2y ago
I realize that the charges are different and clearly attributed to each party they are brought against. The optics of this will still practically lead to people equating both parties and the charges. An alternative (ie seeking both warrants
108.
by jupp0r 2y ago
The optics of equating a terrorist organization on the one hand with a democratic state with functioning judicial system and accountability for any crimes committed on the other hand by putting them in the same press release is pretty bad f
109.
by jupp0r 2y ago
Why wouldn't you just get a Model 3 for that price? It's just much better tech, more fun, much better range and probably has better resale value down the road. Not a fan of the CEO for sure, but it seems like there are worlds betw
110.
by jupp0r 2y ago
There is also almost all of the really reliable Toyota diesel engines for Land Cruisers, etc that never made it to the US market.
111.
by jupp0r 2y ago
Because when you are Youtube, even relatively marginal cost improvements can be huge in absolute. There is also the UX of having to wait X minutes for an uploaded video to be ready that is improved by this.
112.
by jupp0r 2y ago
If you work through the TLA+ tutorial[1] it will help you get a good idea of the benefits and limitations of verification. [1] https://learntla.com/
113.
by jupp0r 2y ago
To start with, you usually perform verification on a behavioral model and not on the code itself. This opens up the possibility that there are behavioral differences between the code itself and the model which wouldn't be caught.
114.
by jupp0r 2y ago
In practical terms, if you are a database and Jepsen doesn't find any bugs, that's as much assurance as you are going to get in 2024 short of formal verification.
115.
by jupp0r 2y ago
"The amount of APIs in the world that require concurrency within a single request scope to meet latency needs approaches zero." I've never worked on any non-Rails API where this was true. The Ruby community keeps telling me t
116.
by jupp0r 2y ago
https://archive.is/d9Jho
117.
by jupp0r 2y ago
"I can make a JS or Go program perform the same way. In fact the exact same thing happened in my shop with Go/Gorm. The key question is: how do you compute the 5mb of JSON? The devil is in those details. We changed the way we comp
118.
by jupp0r 2y ago
"being in the corner at scale doesn't force you to rewrite everything. Just the piece that put you there. You can leave Rails app to handle most things, and extract parts of specialized infra as needed." You can't easily
119.
by jupp0r 2y ago
I also have the feeling that you are talking to a different person. I'm talking about latency, you are talking about bandwidth. I'm talking about concurrency, you are talking about parallelism. You can scale up any Rails app super
120.
by jupp0r 2y ago
"The vast, vast majority of workloads, especially at small startups, do not need a concurrency story outside of running N processes. Concurrency often gets in the way more than it helps unless you're actively trying to optimize so

More ›