Re:A startup’s Firebase bill suddenly increased from $25 to ...
by weddpros on Wednesday May 17, 2017 @09:07AM
(#14358015)
With keep-alive you may not even need TLS session tickets (if the keep alive timeout is long enough).
keep-alive keeps the HTTP/TLS socket open.
TLS session tickets allow to close and "cheaply" reopen TLS session on a new socket for a new HTTP connection.
Using both keep-alive and TLS session tickets is optimal.
Re:A startup’s Firebase bill suddenly increased from $25 to ...
by alexfi on Wednesday May 17, 2017 @05:37AM
(#14356881)
Yeah it's no coding problem on purpose, but sth you could actually fix. But it's not good manner to not mention it from Firebase.
Re:A startup’s Firebase bill suddenly increased from $25 to ...
by mining on Wednesday May 17, 2017 @08:21AM
(#14357677)
It's absolutely good manners for Firebase to tell you "If you fix this thing, your costs will go down."
Re:A startup’s Firebase bill suddenly increased from $25 to ...
by izacus on Wednesday May 17, 2017 @09:26AM
(#14358155)
> It's absolutely good manners for Firebase to tell you "If you fix this thing, your costs will go down."
I wonder how many HN startup founders go around telling their customers on how to pay less.
And it's hard to call this a coding problem if the requirements of the API never specified that session tickets and keep alive were necessary.