3 ms·
It does not matter if you describe a service as a database or anything else. The implications are the same. A service must make architectural decisions. Thos
by stickyricky 5y ago
It does not matter if you describe a service as a database or anything else. The implications are the same. A service must make architectural decisions. Those decisions impose limits. And those limits are billed.
Regardless, HTTP servers are completely uninteresting on their own. No one makes a request to a web server to see how the server is feeling. The server's only function is to serve content. Content it must retrieve (i/o), store (memory), and transform (cpu). That store and transform step nukes your RPS and is completely unavoidable. And, in a high worker environment, will crash your system.
- srcreigh 5y agoWhat if your HTTP server is clock-as-a-service? Then you'd waiting for an unlimited, free external resource called "time".
- stickyricky 5y ago> If my Grandmother had wheels she would have been a bike[1]. 1. https://www.youtube.com/watch?v=A-RfHC91Ewc https://www.youtube.com/watch?v=A-RfHC91Ewc On a more serious note, describe the service for me and I'll give an opinion. Clock as a service is not specific enough.
- deleted 5y ago[deleted]
- srcreigh 5y agoIt's plenty specific. I give you X: float, you return after X seconds.