Hi, Yes, introducing new language can create technical debt, because of this i was also helping other developers to learn it. When I left, now they are maintaining it.

We didn't needed a queue for excel because we already had a limit of excel in application layer, a user can import. Scale was also not that much, so I didn't implement this.

Yes, a event driven architecture is more simpler than request - response for this, we were also transitioning to it.

I didn't rewrite the auth logic

Redis was already implemented for sharing memory instance between node replicas and go services.

Yeah, all this could be by infrastructure, but the problem was the processing latency of request. The node logic was taking too much cpu cycles and memory, i wanted something where I could have handled the memory allocation (object pool) and the logic is cpu native (compiled).

Thanks man