31–40 of 114 posts
Junior millennial hipster developers just discovered SELECT N+1 problem the hard way
No PaaS provider costs their DB instances on number of selects... Perhaps you're the Junior developer?!
I really wish cloud providers would allow users to set a hard budget that just stops the service if you exceed a threshold. I got a surprise bill from AWS this month (fortunately orders of magnitude less than this, but still ~15x my usual) and am thinking of moving from Lambda to a VPS just so the possibility of this doesn't keep me up at night.
Junior millennial hipster developers just discovered SELECT N+1 problem the hard way
How did you manage to make that a “millennial” thing
And millenial ~= trendy.
Earlier quoted context omitted.
You can press the X to close the “Pardon the interruption” overlay that asks you to sign in.
I also seem to have to pay 5$ a month now, I can get past it with some element hiding and cookie clearing but seems like medium is not the ideal solution anymore
It never was.
Junior millennial hipster developers just discovered SELECT N+1 problem the hard way
No PaaS provider costs their DB instances on number of selects... Perhaps you're the Junior developer?!
Earlier quoted context omitted.
block cookies on medium.com domain, seems to work OK
Yeah I can get passed it but damn it's become a mess, I understand they have to make money.
* Create quality service, prioritizing user experience over money
* Grow site to significant user base
* Start running out of money, because hosting and running a site does cost money
* Try to monetize service
* Get out-competed by another service still at step 1
The presence of VC money that's all about capturing market share now, and monetizing later does not help.
In the end, we have become accustomed to a world where things that cost money are given to us for free. When there are attempts to charge us so things remain sustainable, we get angry! It's a tough problem, and I don't know the solution.
TLDR: The huge bill was a result of an improper way the application was coded. They contacted Google/Firebase who were gracious enough to waive off the bill.
Glad to hear that Google has done something with it. Also that's one of the reasons I try to use the realtime database, and not firestore. But they still charge for bandwidth there (most if it is consumed by downloading the SSL certificates from the clients).
Junior millennial hipster developers just discovered SELECT N+1 problem the hard way
I really wish cloud providers would allow users to set a hard budget that just stops the service if you exceed a threshold. I got a surprise bill from AWS this month (fortunately orders of magnitude less than this, but still ~15x my usual) and am thinking of moving from Lambda to a VPS just so the possibility of this doesn't keep me up at night.
On (1), if you get to say the 14th of the month and run out of budget, what would be the expected behaviour? - shut down all your services? delete all your data so that's not incurring a charge too? It'd probably have to be configurable on a service by service basis, and that's an awful lot of complexity to introduce for a tiny minority of their revenue base.
On (2), their billing systems are almost certainly eventually consistent in logging and charging usage, so they'd either have to shut you down early in anticipation of delayed charges, or let any delayed charges bring you over budget. Either is liable to make customers fairly unhappy one way or the other.
The TL;DR version - it'd be nigh on impossible to have good UX with such a feature, would be complicated to implement, and it's not likely to move the needle on any metric they really care about considerably.