hussachai

When I wanted to decode JWT or format the JSON that I got from the system, I searched for those tools in Google. I'd choose one from the top results and use it. But every time, I felt like this was wrong. What if they intercepted my JWT? What if they saved my JSON? Those files sometimes could have personal information or even worse, actual access to the system.

My laziness won over my guilt every time, but not anymore. AI can generate those tools easily. I just built one for myself (took a couple of hours to perfect it). You can use mine, build from mine, or you can even generate your own from scratch. Those web utilities out there are security risks. Don't use them. They will be dead soon.

https://devtools.wsgrok.com (Runs entirely in your browser)

https://github.com/TailrecIO/devtools (Open source that you can build yourself or use as a starting point)

https://github.com/TailrecIO/devtools/releases/tag/v0.0.2 (Desktop version provided by Tauri, built from the attached source that you can review)

The site above is for my own use. If you trust me, you can use it. Otherwise, build your own.

With serverless, the options are quite limited and the technology is well.. locked in. While some parts are portable, most are not. I use a binary protocol (Protobuf) over WebSocket. Yes, it'sslower than local tunnel services that operate at a lower level like TCP, but it's fast enough for most scenarios.

Scaling is a major challenge. Most serverless compute engines rely on an internal load balancer, and all instances are ephemeral. This means instance-to-instance communication is not possible. Scaling can be achieved through a message bus like Pub/Sub, but this introduces another problem. Requests and responses published to topics are replicated across all active instances, which is inefficient.

Other annoying limitations are that the compute process is bound to a request and ends immediately when the request completes. Another is the need to hack subscription leaks caused by the ephemeral nature of the instances (I really hate this).

Cons:

- Scaling is inefficient.

- WebSocket is stateful, which defeats the purpose of cost optimization for serverless. If a client stays connected, the cost can exceed that of running dedicated servers.

- Protocol and platform options are limited.

- Strong vendor lock-in.

Pros:

- Performance is good enough for most use cases.

- Scaling and infrastructure are fully managed.

- No usage means no cost, while the service remains available.

- Small usage is often free, as most cloud providers offer free tiers.

I think building this as a SaaS is a bad idea. It does not reduce costs, in fact it increases them, and it adds significant complexity. Running it as a SaaS is very likely not profitable in today market I assume.

That said, do you think any organization would be interested in an open source version? It is scalable, costs nothing to run aside from initial setup time, and can be more secure if they can properly manage network access. I am not even sure if anyone would be willing to pay a small fee for this.

Maybe I'm building trash. I'm asking here to find out if it could be someone's treasure.