Workers JSRPC Pricing
Hello, after searching through a good deal of the documentation and blogs concerning workers, there's one piece of information that's missing, but I think it's due to its very recent nature.
The pricing on workers is really clear and on this point I have no worries. But I'd like to know more about JS RPC.
When a worker makes an RPC call to another worker, does this count as several requests or just one?
If I were to create a microservice for CORS management, one for token management and other uses, I could easily come up with a request that counts as 3 if that's the case. This can quickly become quite substantial if badly managed, and could make me think entirely about my microservices architecture.
Thanks in advance for your reply.
5 Replies
A request with an RPC binding is billed as a request to the service you are calling. A function call on an RPCTarget is free(other than runtime cost)
For Target RPCs, it seemed logical since it's part of the worker that's loaded into memory, if I've understood how it works. But yes, if every call to an RPC binding counts as a request, that's going to make me rethink the whole architecture. I wanted to be sure, since it loads other workers into memory every time.
There was some talk about making calls to service bindings free, but not sure how far that has actually come
That would be unbelievable, but if each binding is indeed worth a worker startup, it seems logical to me that it should count as an additional request.
cc @Brendan Irvine-Broque this has come up in quite a few questions ever since you tweeted about it, any updates you can share? 👀