Marc J. Schmidt

> I think one issue with RPC is that it's inherently stateful whereas REST can simply round-robin between a 100 containers, with any number of them shutting down for upgrade...

@marcus-sa Not sure what you mean, but Deepkit RPC works fine in frontend backend communication as it uses WebSockets.

I'm sorry if I was unclear with that statement. I was talking about type-safety in TypeScript land. Yes, GraphQL has types, but only their own types. Those GraphQL types have...

@CMCDragonkai 1. RxJS streaming via Observables/Subjects which can be from server->client (server controller) or vice-versa (client controller). Since connections are stateful you can control the stream with an arbitrary RPC...

@NexZhu rather hard since you'd have to write a client implementing the protocol yourself, at least the header: https://github.com/deepkit/deepkit-framework/blob/master/packages/rpc/src/protocol.ts#L37-L74 the body is then regular BSON which can be parsed in...

Client to server, server to client, peer to peer, everything happens through the same connection. So yes this is already possible.

> And none of the examples work That's a bold claim. While it can be you didn't set up correctly, it is very unlikely that all these examples do not...

@fergusean thanks! merged

We use a few key methods of the TypeScript compiler API (for example to resolve types or module import expressions) to be able to correctly embed type informations as bytecode....

We have "loader" capability now in master since https://github.com/deepkit/deepkit-framework/commit/30939492b96fd90d027728fc7a3030e8d8d24bf3. We can try to test SWC/esbuild now using https://github.com/deepkit/deepkit-framework/blob/master/packages/type-compiler/src/loader.ts