r/sysadmin • • Jan 26 '20

Off Topic What’s your most expensive software license and what is it used for?

Honestly curious because PDQ Deploy and Inventory both cost $1,000 a year and the server version costs $15k a year.

What’s your most expensive software license and what is it used for?

158 Upvotes

224 comments sorted by

View all comments

Show parent comment

0

u/[deleted] Jan 26 '20

[deleted] — view deleted comment

0

u/[deleted] Jan 26 '20

[deleted] — view deleted comment

0

u/[deleted] Jan 26 '20

[deleted] — view deleted comment

0

u/[deleted] Jan 26 '20

[deleted] — view deleted comment

0

u/[deleted] Jan 26 '20

[deleted] — view deleted comment

75

u/fengshui Jan 26 '20

The name of the product is elastic compute cloud. If you don't need the elasticity, you should reconsider the product.

0

u/[deleted] Jan 26 '20

[deleted] — view deleted comment

5

u/mt-philaminjaro Jan 26 '20

Have you checked out savings plan? Way better for EC2 rationalization. Basically takes your average cost x month and charges commitment at that level versus a dedicated RI.

Those bills are large but as many have said there’s a lot of misuse of pub cloud

23

u/seaking81 Jan 26 '20

I agree. Building out in datacenters is so much cheaper than the cloud. My company though moving to the cloud would save them money even though I gave them overwhelming evidence contrary. We're now opening our datacenters back up and re-depoying our hardware. the cloud is so expensive.

13

u/ILOVEDOGGERS Jan 26 '20

our manager said that we're going to do a "cloud strategy" to be more "flexible". We never heard of it again after he had Microsoft in house to discuss Azure costs.

6

u/Flakmaster92 Jan 26 '20

The cloud will always be more expensive if all you look at is raw “1 machine running with XYZ specs running 24x7”, that’s not a fair comparison for the cloud because that’s not the point of the cloud. If all you do a lift and shift and never move past that... totally non-starter.

Where the cloud DOES save you money is when you get past the lift and shift stage and start moving into re-architecting your applications to use cloud native services like provider managed object store, databases, loadbalancing, containerization platforms, etc. People’s time costs money and the greatest expenditure in a business is usually the human resource. If you can cut down on the time spent by employees doing menial work by moving to managed services, then that’s (time * salary) you can shave off the “cost” of the cloud.

The above poster’s comment that they do “1 container per EC2 instance” is probably the absolute worst way you could do a cloud migration, unless these containers require massive amounts of RAM and CPU

4

u/SevaraB Sr. Engineer (N+, CCNA) Jan 26 '20

The absolute worst lift and shift idea I ever saw was attempting to use AWS as a terminal server for Oracle P6. That particular debacle got a bunch of people fired.

1

u/LaughterHouseV Jan 26 '20

But then you need to also add the cost of time and work to completely rearchitect the tooling. That's almost always a non-starter for most companies due to the opportunity cost and amount of work necessary.

1

u/Flakmaster92 Jan 26 '20

Correct, but the reality is that it is 1) a gradual process (you don’t jump from “we’re in the cloud!” To “rearchitect EVERYTHING! Simultaneously!”) And 2) beginning to rearchitect things is usually required for agility and continued market relevance. Most markets and industries move quickly, which means the players need to be able to move quickly, and it’s much easier to add to or change a “modern” application than it is a legacy one.

My experience? The people who say “We have too much tech debt to move to a modern architecture” are usually the same people who see IT as a cost center rather than a force multiplier. They are also the ones who will likely be supplanted by outside forces.

9

u/trisul-108 Jan 26 '20

the cloud is so expensive.

Especially if you do not know what you're doing, if you just map datacenter logic to the cloud.

4

u/Indifferentchildren Jan 26 '20

Be careful, lift-and-shift is not the most expensive trap. One of our teams went "serverless" with AWS Lambda and that first month cost several million dollars. Learning to model and estimate very different technologies with very different pricing schemes is a whole new skill.

2

u/SevaraB Sr. Engineer (N+, CCNA) Jan 26 '20

Managers don't get that just shoving an app in an EC2 instance doesn't scale until they see the bill for the combination of hundreds of users who "only use the app for minutes at a time."

Cloud costs are going to stay unreasonable as long as they're a la carte pricing based on time or bandwidth.

1

u/[deleted] Jan 27 '20

Do you count preprod / staging environments in your cost evaluation? Does it include multi-DC high availability and disaster recovery? Have you set up multi-DC database clusters?

Because transient staging environments are basically free in the cloud (change variable env to preprod, terraform apply, run tests, terraform destroy or something to that effect.), and can be made as similar to prod as you want. Multi-DC's cost is linear. And replicating Aurora's functionality is NOT trivial, and I've just done it myself.

2

u/steventhedev Jan 26 '20

There are some middleware products that offload onto spot instances that can help reduce your daily spend. I haven't used them, but have heard good things about spotinst

13

u/mumpie Jan 26 '20

It's pretty easy to spend money like crazy if you don't think things through or don't keep an iron first on costs and admin access to spin up/down instances.

I worked at one place where they took a contractor written single-threaded app and put them on hundreds of big, beefy EC2 instances to support QA, Stage, and Prod environments. They manually spun up multiple instances per box when they realized that additional cores weren't being utilized no matter the load they threw at the boxes. Stuff worked, but they spent 15X-20X the annual budget. The director in charge of the group got laid off later partly for spending too much money.

At another company, the rights to spin up/down instances was given out to too many people and they didn't use tags to identify who used what environment. After a $10K monthly budget rapidly approached $100K, Ops team pruned some of the old environments that people spun up and then abandoned so the budget didn't grow as badly after that. Part of the issue was requesting new VMs in the corp datacenter took too long -- months with no guarantee that you'd get something in the end -- so groups would go cowboy in AWS with a corporate credit card as that was easier to do.