151–160 of 397 posts
If very few people visit a side-project, that's probably bad for Google search. Its crawler will be detecting slow response times and Google can penalize you in search results.
What a complimentary business strategy :)
I have used it for work-related reasons and indeed the service is quite nice. But I don't use Google Cloud Run for personal projects for two reasons: - No way of limiting the expenses AFAIK. I don't want the possibility of having a huge bill on my name that I cannot pay. This unfortunately applies to other clouds. - The risk of being locked out. For many, many reasons (including the above), you can get locked out of…
Cloud hosting is great for businesses, that's why I believe that every web developer should experiment with those services. It's not great for personal use for the reasons you've stated - the risk of your service going down due to it being viral is much easier to bear than the risk of having to pay outrageous amounts of money for those services in that event. If your hobby project goes down for a while nobody will re…
Your liability is not capped anywhere. I better stick to 5$/mo DO for my side-projects.
From the article: > The service will create more and more instances of your application up to the limit you defined The docs confirm an instance maximum can be set and the price per instance can be less than $5/month.
The thing I really want out of these services is the ability to set a payment cap. It’s probably never going to be an issue, but I have anxiety, and I can’t sleep easily knowing that if I fuck up, if someone sinister abuses my application or whatever I may be stuck with a giant bill.
If you do allow some kind of ordered shutdown of service, what is the UX going to look like? What is the API going to look like?
Having a cap is not an easy feature to design or implement. And on a backlog, it is going to be a “multi quarter, low impact” item—meaning it will never get built.
Might be a mindset thing but if my side project needed scale I would not think of it as a side project.
My 3 side projects got reddit frontpaged (also here) and I got better at handling it. Fortunately I always had scale in mind (at peak got thousands of requests per second) but the first time was not a pleasant experience because I would have to pay more than I could if that kept going on. Fortunately I found a solution while keeping my site online and over the time the project paid me very handsomely. If I didn't plan ahead, those would be dead in the water.
Earlier quoted context omitted.
It seems absolutely within amazon's technical ability to allow you to prepay for usage, and then evaluate your use on a per-hour basis. I have a side project that uses AWS at the moment, and while stuff like serverless RDS instances are really cool, it scares me that somehow amazon is going to have a bug which empties my checking account. I've read as much of the documentation as I can find and have done everything I…
Checkout privacy.com you can set merchant daily, monthly or yearly spending limits.
I've been using Cloud Run for my GPT-2 text generation apps ( https://github.com/minimaxir/gpt-2-cloud-run ) in order to survive random burst, and also for small Twitter bots ( https://github.com/minimaxir/twitter-cloud-run/tree/master/h... ) which can be invoked via Cloud Scheduler to utilize the efficiency benefits. It has been successful in those tasks. The only complaint I have with Cloud Run now (after many usab…
I'm currently serving an api that uses a 500mb resnet v2 model. The bootup takes to long, so now I have a single instance that can't handle any peaks and costs too much. Doesn't your model take to long to spin up before being able to serve a request ?
As a noob I have a question as to what advantages I have using docker compared to just a service like Heroku where I just push the application to them... and I don't bother with docker? To me with my limited understanding this seems like just another step. Now granted when it comes to work, I'm using docker with specifics that I know why I would want / can specify with docker ... but for personal projects this ever c…
The thing I really want out of these services is the ability to set a payment cap. It’s probably never going to be an issue, but I have anxiety, and I can’t sleep easily knowing that if I fuck up, if someone sinister abuses my application or whatever I may be stuck with a giant bill.
A “cap” feature isn’t as easy to implement as you’d think. What happens when you hit the cap? Does it start shutting down instances? If yes, which ones and in what order? And don’t say “I don’t care” because you do care—you are allowing your provider to basically cause an outage in your service. If you do allow some kind of ordered shutdown of service, what is the UX going to look like? What is the API going to look…