IT/Software career thread: Invert binary trees for dollars.

Sheriff Cad

scientia potentia est
<Nazi Janitors>
31,166
73,991
Cloud computing's revenue model works like drug dealing. Get people hooked cheap, get them dependent, then ramp up the cost when you have set the hook and they cannot go back. This is going to be the gameplan with AI as well, with a side of surveillance state thrown in to sweeten the pot.
I get thats the plan, but why can't you go back?
 

Sheriff Cad

scientia potentia est
<Nazi Janitors>
31,166
73,991
Curious. Before I expound. How familiar are you with large scale information systems, the underlying hardware needs to host it yourself versus the cloud.
I have a computer science degree, worked as a software engineer for 10 years before going to law school. I did C/C++/Java back in the day (I stopped in SW in 2007).

Almost all hardware was on site then, so where my knowledge gaps are is in AWS/Azure etc because that shit did not exist then.
 

TomServo

<Bronze Donator>
8,660
15,382
So, at a very high level using my corp as an example. We currently have a hybrid of AWS running the majority of our enterprise apps, with on prem legacy mainframes and data stores, with a smattering of Azure. To move everything to AWS isn't just a turn key operation. Switching from on prem virtualization to AWS Virtualization is complex and rather lengthy. You are trying to replace apps while they still need to run in parallel. Let's say you reach the end goal of everything being in the cloud 100% native all, SaaS, 3rd party integrations are successful. You would have to maintain the power, hardware, staffing, and contracts for ISPs active for whatever length of time in order to cut back to your own data center at some point in the future. That is a massive spend. Which is why its all in and once you are in AWS or whatever you get raped 10 ways from sunday because now you're captured. I'll give a really small portion of our current opex bill. to record the API write events to a single S3 storage bucket for our data intelligence team in a calendar year, this is not including storage, just recording the API write events, not the API read events. is $1.6 million a year.
 
  • 1Mother of God
Reactions: 1 user

Sheriff Cad

scientia potentia est
<Nazi Janitors>
31,166
73,991
So, at a very high level using my corp as an example. We currently have a hybrid of AWS running the majority of our enterprise apps, with on prem legacy mainframes and data stores, with a smattering of Azure. To move everything to AWS isn't just a turn key operation. Switching from on prem virtualization to AWS Virtualization is complex and rather lengthy. You are trying to replace apps while they still need to run in parallel. Let's say you reach the end goal of everything being in the cloud 100% native all, SaaS, 3rd party integrations are successful. You would have to maintain the power, hardware, staffing, and contracts for ISPs active for whatever length of time in order to cut back to your own data center at some point in the future. That is a massive spend. Which is why its all in and once you are in AWS or whatever you get raped 10 ways from sunday because now you're captured. I'll give a really small portion of our current opex bill. to record the API write events to a single S3 storage bucket for our data intelligence team in a calendar year, this is not including storage, just recording the API write events, not the API read events. is $1.6 million a year.
I understand all that but it still doesn't make sense why, if AWS/Azure results in these ridiculous bills, are the on-site bills even more ridiculous? If so then you're getting the cheapest deal already. If not, then why not pull it back on site, even if it costs more in the short term?

Is the issue that on-site costs less in the long term, but nobody wants to eat the short term spend?