Comments by "Jeremy Chone" (@JeremyChone) on "ByteByteGo" channel.

  1. Very good overview of the key caches. Thanks for sharing all of those great knowledge with everybody!
    18
  2. Good video as usual. Our rule of thumb is "Lame Is the New Cool" as far as database choice.
    16
  3. Very nice explanation. On top of password individual hash (stored in the DB), we also use an additional system wide salt, usually stored as a kubernetes secret property. This add another level of security. Also, we also use similar salt technic for the web token signature. Web Tokens embed their expiration, which is updated at each web request (typically as a http only cookie), and the third element is the signature using: ash(user_uuid + user_tsalt + global_tsalt). Also, we do NOT store credentials/access in the token, which is a longer conversation. So, a user row has a psalt column, for the password hash, and a tsalt for the token salt. Anyway, great vide, this is great to find this level of content on YouTube.
    7
  4. Great videos. We like to have a "multi-services" architecture where size is more of a deployment detail, thanks to Kubernetes. Also, most important in cloud architecture is to be event-based from the start to avoid Web-Of-Hell service architecture.
    7
  5. We moved from REST to JSON-RPC for all our remote APIs. Much better representation for remote function calls. It made the whole http method to function call mapping gymnastic disappears. We wish we would have done so 10 years ago.
    5
  6. Why not Redis Stream for Queue?
    5
  7. wow, what an awesome introduction to SQL optimization.
    5
  8. json-rpc rocks!
    2
  9. I would assume this architecture work with both cartesian and spherical coordinates? It seems that long/lat was mentioned, but from my understanding, spherical coordinates should used for the query. Btw, DataFrame technology could be great here (specifically Polars/ApacheArrow). Polars with the GeoPolars extension could be a great fit. I will try to do some benchmarking it if I find the dataset.
    2
  10. Is SRT based on HTTP/3 ?
    2
  11.  @JustinShaedo What do you mean by better supported?
    1
  12.  @JustinShaedo  Hmm, I'm not sure what "natively supported by browsers" means. JSON-RPC is simply JSON over an HTTP POST. In fact, it's a subset of REST in terms of the protocol and HTTP method used. So, assuming we make our requests with the browser's XHR or the new Fetch API, there's nothing more the browser needs to provide to support JSON-RPC over REST, since JSON-RPC is a subset of REST.
    1
  13.  @JustinShaedo  Thank you. Yes, we have been building large applications using JSON-RPC for many years now, and it has worked extremely well. We even provided an API to our clients' developer users, and they loved it. It's very simple: just an HTTP POST with JSON in and out, featuring a minimal top-level structure. It works in any browser, any client, with no stubs or SDK needed. Developers can find more information by searching for jsonrpc online; the specification is incredibly straightforward. In fact, we use it in our rust10x blueprint (a Web App production blueprint), and it works like a charm. I've made an extensive video about it, with more to come. There are many myths about json-rpc, but once its simplicity and versatility are understood, it resolves many issues. No more REST gymnastics for function calling, and best of all, it's protocol-independent. We can use it for network calls, WebView to Backend calls, like Tauri commands, or even in message passing in an actor model. However, there's no absolute best way to code large production applications. If developers are more comfortable with REST or gRPC, that's completely respectable too. Happy coding!
    1
  14.  @ByteByteGo  Yes, this is why I asked. Curious to know if there is some natural convergence between those two protocols.
    1
  15.  @JohnDoe-my5ip  Fair point. We like PostgreSQL.
    1