3 ms·

The author is a bit opinionated to say the least. He's also on a crusade against JSON web tokens and MongoDB. [0] http://cryto.net/~joepie91/blog/2016/06/13/st

The author is a bit opinionated to say the least. He's also on a crusade against JSON web tokens and MongoDB. [0] http://cryto.net/~joepie91/blog/2016/06/13/stop-using-jwt-for-sessions/ http://cryto.net/~joepie91/blog/2016/06/13/stop-using-jwt-fo... [1] http://cryto.net/~joepie91/blog/2015/07/19/why-you-should-never-ever-ever-use-mongodb/ http://cryto.net/~joepie91/blog/2015/07/19/why-you-should-ne...

strictnein 7y ago
Hmm... so he's right on 1/3 issues.
- dmix 7y ago
  JWT is fine when implemented properly for the types of use cases it was intended for. Which in 2019 is the vast majority of libraries available.
  - prophesi 7y ago
    And, to be clear, using them for sessions is not one of those intended use cases, as joepie91 is arguing in that article. Using an actual server-side solution is easier and safer. For posterity, here's the second part to his crusade: http://cryto.net/~joepie91/blog/2016/06/19/stop-using-jwt-for-sessions-part-2-why-your-solution-doesnt-work/ http://cryto.net/~joepie91/blog/2016/06/19/stop-using-jwt-fo...
- GrayShade 7y ago
  2/3.
  - blaser-waffle 7y ago
    Whats wrong with MongoDB?
    - GrayShade 7y ago
      Nowadays not much, but it used to be overrated and had serious reliability problems. Your startup probably doesn't need Big Data (TM). Just use a relational database like Postgres and learn a bit of SQL. IIRC, Postgres outperformed Mongo at JSON processing, which was supposed to be one of the stronger points of MongoDB.
    - parliament32 7y ago
      Mongo is the wrong choice for a solid 75% of the places it's used. In the vast majority of cases, it was brought in to replace a relational db because developers though it would be faster to not have a schema / constraints / relationships, etc. It usually lets you develop faster, at the cost of blowing up in your face a few months/years down the line, when you have to rebuild your app to use a real database because your devs remembered why relational dbs are useful in the first place. Mongo is a document store, not a relational db. Mongo is a good choice if you're looking to replace ElasticSearch, not if you're looking to replace MySQL.
parliament32 7y ago
He's not wrong about either of those.

strictnein 7y ago

Hmm... so he's right on 1/3 issues.

dmix 7y ago
JWT is fine when implemented properly for the types of use cases it was intended for. Which in 2019 is the vast majority of libraries available.
- prophesi 7y ago
  And, to be clear, using them for sessions is not one of those intended use cases, as joepie91 is arguing in that article. Using an actual server-side solution is easier and safer. For posterity, here's the second part to his crusade: http://cryto.net/~joepie91/blog/2016/06/19/stop-using-jwt-for-sessions-part-2-why-your-solution-doesnt-work/ http://cryto.net/~joepie91/blog/2016/06/19/stop-using-jwt-fo...
GrayShade 7y ago
2/3.
- blaser-waffle 7y ago
  Whats wrong with MongoDB?
  - GrayShade 7y ago
    Nowadays not much, but it used to be overrated and had serious reliability problems. Your startup probably doesn't need Big Data (TM). Just use a relational database like Postgres and learn a bit of SQL. IIRC, Postgres outperformed Mongo at JSON processing, which was supposed to be one of the stronger points of MongoDB.
  - parliament32 7y ago
    Mongo is the wrong choice for a solid 75% of the places it's used. In the vast majority of cases, it was brought in to replace a relational db because developers though it would be faster to not have a schema / constraints / relationships, etc. It usually lets you develop faster, at the cost of blowing up in your face a few months/years down the line, when you have to rebuild your app to use a real database because your devs remembered why relational dbs are useful in the first place. Mongo is a document store, not a relational db. Mongo is a good choice if you're looking to replace ElasticSearch, not if you're looking to replace MySQL.

parliament32 7y ago

He's not wrong about either of those.