JSON Web Tokens should be avoided

Re:JSON Web Tokens should be avoided by justinclift on Tuesday March 14, 2017 @09:17AM (#13867228)

Hmmm, using a database (eg PG) for the authoritative information, with memcached in front sounds like it would be practical for most uses.

[ Parent | on HN ]

Re:JSON Web Tokens should be avoided by falcolas on Tuesday March 14, 2017 @09:54AM (#13867459)

At which point you should probably ask yourself: "What value is keeping all of my state inside this token providing me?"

[ Parent | on HN ]

Re:JSON Web Tokens should be avoided by mwpmaybe on Tuesday March 14, 2017 @10:40AM (#13867811)

Probably not. If the Pg instance is replicated, as indicated above, it'll be challenging to keep the Memcached copy in sync. In other words, you can't just use the caching feature of your ORM, you'll need another piece.

[ Parent | on HN ]

Re:JSON Web Tokens should be avoided by justinclift on Tuesday March 14, 2017 @01:44PM (#13869716)

Thanks, that does need further thinking about. :)

[ Parent | on HN ]

Re:JSON Web Tokens should be avoided by cygned on Wednesday March 15, 2017 @10:20AM (#13876257)

Postgres is not a good solution for this kind of data. I'd use Redis, but maybe there are even better products.

[ Parent | on HN ]