Kamil Fronczak

A long time ago, I found myself in a situation where I had to create a scalable system that could be capable of handling hundreds of simultaneous connections at not very high cost, and with reasonable, but not instant time of response. My first thoughts? Let’s move all create/edit/delete actions to the queue and notify users if their actions succeeded or not via WebSocket. But back then, I hadn’t much experience with WebSockets in production,

Recently, I’ve been thinking about how to make some of my crucial endpoints more secure when using locally stored JWT. It may not be the best practice for security (because of the possibility of XSS attacks), but this was a requirement not set by me. I had to adapt. So in order to make this more secure, I’ve found a solution, that, hopefully, will help you as well. The Problem I assume that we all