As my organisation migrates everything over to AWS I do find myself questioning what the costs will look like when it is all done and we are completely locked in. AWS/Google/Microsoft cloud services put you in the position of an almost completely captive customer. What large corporation would ever sign up to that?
> What large corporation would ever sign up to that?
Ones with the power to have some very nice contract terms put into place to mitigate downsides in the medium term. If it's a problem long term then that'll be the next CEOs problem and the current one will have cashed in their $50m check already.
Less cynically, for many of them it's either being captive to their barely working IT department or being captive to a decently more competent AWS. So they choose the one that will give them better features for less money in the medium term. They can't make their IT work better because it's a two sided monopoly. Only one client who is guaranteed to not leave (until AWS at least). That inherently and unavoidably creates horrible incentives.
> for many of them it's either being captive to their barely working IT department or being captive to a decently more competent AWS.
It's more just being prone to sales tactics.
For the IT department you've seen everything - all the issues. You overlook the good parts.
For an external vendor you only hear about the good parts from the salesperson. They often over promise etc. You get told you'll save time and money, they can engage you with a consultant to help migrate etc until you realize no 1 has actually done the proper analysis and something doesn't work. There's going to be weeks/months of delay but by then you're already signed.
> so much so that the inefficiency of the cloud is more efficient than them doing the work themselves.
You jest. They just add so many "required" layers to the cloud to make it even worse. They create "frameworks", "controls", requirements, guidelines and this and that so that using the cloud is even more effort.
You used to request a server, get a login and be done. Now you have to deal with the cloud and a whole lot of confusion over what can and can't be done and request access to every small bit of detail.
That’s not new, it’s probably just shifting around who does it.
When I worked at a Fortune 500 company, that was me. I’d get a request for a server from a dev and have to fracture it into like 50 separate tickets. One to security to open up the firewall, one to storage to get disk space, one to the VM guys for CPU and RAM, a couple to the AD guys for a new group and user, etc, etc.
>> What large corporation would ever sign up to that?
Speaking of the banking sector, we are migrating our workloads to the public cloud as it allows us to be nimble and responsive to business needs. And we are getting a highly resilient and robust IT infrastructure that we could not implement on our own without having a very high headcount and associated bureaucracy.
As long as you are not using proprietor technologies e.g DynamoDB or GCP Firebase etc., you stack can be migrated from one cloud to another. It wont be easy or painless but it wont be impossible either.
>It wont be easy or painless but it wont be impossible either.
With data egress costs, all the security infrastructure built up is all bespoke to a provider, not to mention engineers relearning the new provider's APIs and all its warts. The cost would be HUGE. Would be something that would go to a board for approval.
The biggest problem is getting everyone aligned, designing a plan with minimal rework, and being able to hire incredible talent that is going to cost far more than most companies are willing to accept.
For most companies they'll try with their existing talent and it'll be +5 years and an absolute failure.
And the very sizable opportunity cost of the engineering time spent on that project and not in anything more pressing. If your platform team has nothing better to do then I guess that's 1.5 years well spent, but if they have nothing better to do I have some questions about your company's engineering decisions.
Everyone says this but very few know the true costs of keeping a private datacenter. Everyone looks at the aws final number and says oof that’s too high. Then ignore things like the 10 year old code base that is still being developed, causing outages and support requests that is not included in the on-prem cost.
When I did work for a var that was selling on-prem accounting software, that number was closer to a 20% difference in cost. Now add in large corporations discount for buying large amounts of compute and it suddenly becomes very palatable to use the cloud.
Small companies still benefit the most from on-prem.
At that scale it is cheaper. If you have a requirement for only a few dozen, then webhostingtalk is all you need. When you need 100k servers, you will be managing the hardware yourself
As a large org, you sign up for elasticity and mostly infinite rack space and power delivery. You basically turn capex into opex (though with reserved capacity you can get some capex back).
You can sidestep the worst parts of the compute lock-in by cloud-agnostic tools like k8s and terraform. Storage will always keep you hostage.
Anyway - the grass will be greener on the other side regardless of what you do.
would there be a scenario where you prefer to mark it as capex? opex has the advantage of reducing tax immediately and getting the tax benefit right away. I feel like that's always an advantage
Vouching for this, because if it's indeed a bad take, I’d like someone to explain why.
For the most part, it seems like a reasonable buy vs rent argument, except that if you try to build your own internal self-service cloud platform for the dev teams (or just have ops teams that are in charge of provisioning and running things), you also have a lot of complexity and employee time spent there, with it often being hard to get right.
I don’t thing orgs necessarily care that much about overpaying for some EC2 instances or load balancers when that lets them iterate reasonably quickly and have fewer compliance headaches and good SLAs.
I’m don’t 100% agree on this: this isn’t 2014 anymore, many solutions (“on prem $service”) have already been developed, are fairly known and have backing companies ready to sell you support and solutions rather than just asking you to pay rent. Example: cloudian or minio for s3-compatible storage.
I'm all for using on-prem self hosted options when available, personally I run my own mail server (though a pre packaged version), Nextcloud, Gitea and many other services. However, that's mostly for my own personal needs and to explore the software out there.
In many of the orgs out there, especially the larger ones, telling people that they should provision their own hardware because I want to run a self hosted piece of software instead of pressing a few buttons in a web UI somewhere (or having a few scripts written and run) to provision things would be a tough sell. Even if they could get me a dedicated box somewhere, I'd still have to be responsible for managing said software, instead of just taking on the SaaS approach and not having my career be on the line for not doing everything correctly.
in any decent organization you don't run any of the services yourself except for the software you write, an infrastructure and platform teams do that for you.
going back to on-prem doesn't mean developers need to manage their own mysql database or stuff like that.
The power company is almost entirely different; everywhere in the US I’m aware of caps utility profits so the “getting gouged” risk is literally illegal.
Commercial real estate leases are often for a long duration, also nullifying a lot of the gouging risk.
The downside of using S3 is that their billing model tends to create complexity around trying to use it as little as possible. Many projects will need to spend significant time on “how do we minimize S3 costs?”.
I would wager most consumers of S3 are not in the “has a high enough scale of data to have genuinely complex problems” crowd and would be basically fine with MinIO or any of the various on-premise storage vendors offering an S3 API.
The alternative to using S3 is to do it themselves?
Also, do you really specifically want S3? The value of S3 is working at scale but very few but amazon needs that scale. So many other solutions work just as well.
S3 in regard of vendor lock is a bad take since it's probably the easiest service on AWS to migrate from with dozens of fully compatible solutions existing outside.
Even EC2 (AWS's VMs) require more work to migrate from.
S3’s lock-in is financial rather than technical, especially if you’re using Glacier for backups that need to be moved. It gets really expensive to pay for egress on all that data.
No this argument is not analogous. I worked for a bank that upped and moved offices on a commercial lease renewal. Let me know when you hear of a bank migrating Cloud providers and I will reconsider. It is 100% vendor lock in, no escape.
The post seems to be assuming that multi threaded code is easy to build and maintain. From my experience it is horrible, every new thread means going from n bugs to nn bugs. As a programmer I prefer* async constructs in languages, and do not want to spin up and manage threads and all the state synchronisation that involves.
If TC39 Signals are merged this will be redundant. Signals are better than this as they keep track of the tree and don't do unnecessary traversals. With 'automatic useMemo' (this), the tree still needs to be fully traversed.
> you are sending a signal that days worked at home don't count
The majority of c-suite execs believe this to be true (except when they are out of the office or working from their summer rental for two months of the year) - why would you not signal it?
> Encourage workers back in with a carrot not the stick
Expensify tried this, making the best office they possible could, the end result was people would come in to try it, leave positive feedback then never go back.
Skimming the article, it feels they've focused on trinkets. The one thing that could make meaningful difference to their employees is giving everyone a room with a door that closes. The article doesn't seem to indicate they tried that. Free drinks and call rooms aren't going to offset the hell of an open-plan office; it's not surprising if people already used to WFH would pass on that.
At a glance of that article they improved some of their furnishings and facilities. Is that the only thing you are considering when I refer to a carrot and not a stick?
I think that’s definitely a thoughtful approach but there is no carrot big enough. 50% increase or double my pay, maybe. That’s how big of deal WFH is to most. My work is trying to develop some in office novelties that I think most won’t care about one iota. I miss the office sometimes but then I remember all the crap that comes with it.
The problem with your question is that they are there to show off their knowledge. I failed a tech interview once, question was build a web page/back end/db that allows people to order let's say widgets, that will scale huge. I went the simpleton answer route, all you need is Rails, a redis cache and an AWS provisioned relational DB, solve the big problems later if you get there sort of thing. Turns out they wanted to hear all about microservices and sharding.
This article is trying hard to sound like it is based on years of learnings, but honestly every point in here just reads like it was cobbled together after the xz incident.
Java is better than Javascript, I'm mystified. I have used Java and Javascript lambdas, the Java ones use 4 times the memory of the JS lambdas and are slower, to do the same thing.
I like that typescript catches when I need to do null checks so I don't end up with the most notorious runtime error seared into the brain of every JS developer "cannot read property of undefined".
Some parts are nice, like the string literal typing "this" | "that". Other things are hacky, like "branded types", gross.
But then I think of my commercial codebase which is extremely well tested, regular old JS, and wonder if is worth the hassle.
