638 karma · joined April 7, 2020
https://docs.aws.amazon.com/apigateway/latest/developerguide...
This is a hard no from me.
How is AWS going to even know what to shutdown/remove? What if it's storage causing my bill to overextend?
Yeah, not just no, but hell no.
Businesses, the entities that are paying the most money to AWS, will NOT want a hard shutdown. When you generate revenue off of your SaaS service maybe you'll understand.
No, I won't be pushing my TAM to enable a forced shutdown due to budget metrics.
Not to mention, how does AWS decide what to shutdown and what to delete? It's not like it's only running resources that cost money, what about all my data that's stored???
I'm counting on being luckier than those guys more than anything.
EDIT: Not necessarily YOU will have to clean it up at some point, but the next guy most likely will.
Spend your early time working on your core business. If your core business isn't cloud agnosticism then you shouldn't be investing your resources there.
We're all in on AWS and don't care about lock-in.
The vendor lock-in argument isn't worth considering for most businesses.
Security through obscurity is just some feel good bullshit.
This kind of stuff is widespread in Florida. Sheriff Gualtieri, Grady Judd, Billy Woods, Darryl Daniels, ex Sheriff Mike Scott, Ric Bradshaw, and I could go on and on and on.
Look across the vast swaths of rural land in the landlocked parts of Florida and you'll find the only industry are prisons and policing.
Nothing worse than having to spin up more and more instances and manage more and more hardware/virtual hardware/services as your customer base grows.
Stopped reading here.
Thought this was going to be an experiment on privacy. Like, blocking trackers and not using the giant providers SaaS offerings.
When I hit a problem and solve it I'll usually make a blog post about it on my personal blog. I try to share as many random learnings and other tidbits from my career on my blog. There are even some search terms where my blog comes up in the top 1-5.
There aren't any less blogs now than there ever have been, other content is just more prolific these days.
You're not missing anything. There are still some use cases for on-prem hardware or for not building out on a single cloud provider but they're getting harder and harder to justify. The main use case I can see for running your own hardware is if you need massive egress. There comes a point where it can make sense to run it yourself, I luckily work at places with large enough margins to still leverage cloud solutions for this though.
Some guys don't know how to build things out on the cloud and are stuck in their way. When I was getting into the industry the old guys were still stuck on bare metal vs VMs. You should know how that went, most apps migrated to VMs no problem and a few apps stuck to bare metal for their own reasons.
A lot of small/mid size companies don't have the manpower to properly move an app to the cloud. Sometimes products/companies have enough steam to build an app and barely support it but not quite enough to keep it competitive and current. Basically, it can be easy to get a profitable company/app started with a couple amateurs building the product. It can get very expensive when you need professionals. A lot of places don't have the margins to support a robust team of professionals.
These companies don't always lack the foresight, sometimes it's impossible to get some breathing room to see the big picture or to get project funding instead of just upkeep funding. It can be expensive migrating something to AWS/Azure/etc and not just money but also manpower.
We could spend time making sure we use the smallest aurora instances possible in AWS or we could standardize on a version to support and use the smallest size of that version that's available. We spend a lot on this extra capacity in some places, but it greatly increases our speed in other places.
It's all about trade-offs and what your organization values.
The portability also brings other benefits.
> We assume that operating costs for personnel, loading, and monitoring will be approximately the same per package for truck as for drone delivery.
but at least they included
> There are additional drone costs such as: setting-up and running the drone delivery stations, the investment in research and development, and lobbying the FAA. Other costs include: buildings and land associated with the drone stations, computers and monitoring software systems for drone flights, computer technicians and drone monitors on site, robotics engineers for maintenance and upgrades to drones on site, utility costs of running the building, logistics management team to oversee operations, potential insurance and legal fees associated with drones, and potential air and/or radio frequency rights for drones, etc. There is also the potential for legal costs in some of the following situations: drones are found operating in unauthorized airspace, drones are shot down by civilians, a drone lands in an unauthorized space, etc
There's also mention that the drones can only deliver up to 5lb packages.