1) Your application doesn't need it now but if it's a real application then you should always be getting ready for the future. JWT support is extremely easy to add now-a-days as any production-ready web framework will support out of the box or with a plugin.
2) JWT is a common standard for handling several different concerns. Having it implemented out of the box means it will already be there when you actually do need it.
I personally design everything with a scaling-first mentality. It's easy to neglect scaling until your awesome app crashes at the awesomest time ever and you lose all of your awesome users and you awesome clients don't feel awesome about paying you an awesome amount of money.
Great observation.
I would refute with two points:
1) Your application doesn't need it now but if it's a real application then you should always be getting ready for the future. JWT support is extremely easy to add now-a-days as any production-ready web framework will support out of the box or with a plugin.
2) JWT is a common standard for handling several different concerns. Having it implemented out of the box means it will already be there when you actually do need it.
I personally design everything with a scaling-first mentality. It's easy to neglect scaling until your awesome app crashes at the awesomest time ever and you lose all of your awesome users and you awesome clients don't feel awesome about paying you an awesome amount of money.
I don't see how cookies are going to stop your scaling? Get user info and store it in a cache with TTL.