r/devops • • Jul 24 '21

I hate the cloud

Over last few years I designed or redesigned multiple different infrastructures (all as IaC, some with k8s stuff) and worked on few more. All of those were on prem stuff built on top of open source tools (with some proprietary bullshit I had no influence over, VMware, Oracle etc).

My growth as an engineer was mostly iterative, I was building skills on top of previous experience with similar standards and tools. It was all I wanted from my job, cause it was in sync with my views on software (foss first, proprietary vendor lock only if there is no choice).

Recently when I was looking for new client to work for (I run a single person business, it has some financial and freedom related benefits in my country), I've noticed that 90% of the job offers involve some kind of cloud environment, so I figure, it's time to get better idea about it.

I never held cloud in high regard, cause it seemed like a worst possible vendor lock in, just better marketed. Sadly it had to be done.

Few months into the project as a more of a cloud architect (though I write automation too), I find myself learning stuff that does not translate into anything else, but single vendor product. Unlike my previous experiences, none of this is going to benefit me if I have to change project into something that uses different cloud provider or even on-prem stuff.

I suspect without some legislation about standards in the cloud (like not allowing cloud providers to create proprietary APIs or vendor specific tools), this is only going to get worse.

0 Upvotes

47 comments sorted by

10

u/janora Jul 24 '21

I find myself learning stuff that does not translate into anything else, but single vendor product.

I assume you are learning the vendor specific implementation of the bigger concepts.

S3? Thats just Object Storage. Every Provider offers some kind of Object Storage. Azure has their "Blob Storage", Google calls it Cloud Storage and if you want something open source check out minio.

AWS Lambda? Thats just Functon-as-a-Service, Azure Functions, Google Cloud Functions or how ever they name it.

Most of the stuff is just common cloud concepts with added marketing.

1

u/[deleted] Jul 24 '21

The concepts of what constitutes a cloud are nothing new, all that shit is just what we were doing for decades, but with extra abstractions that are vendor specific.

The problem are implementations of those - apis, custom DSLs, custom cloud native apps that are just enough different from foss standards to make you learn them as something new.

6

u/ButtcheeksMD Jul 24 '21

"without some legislation"

Thats a dangerous statement. Also. Get over it. I've ported full production AWS stacks to GCP, I've built similar techs in both, with the same tools, etc. Its not that big of a deal. Not to mention, most companies are locking into huge contracts with the cloud providers anyway, so tech vendor lockin in is the least of your worries.

There is a lot of tech that spans across the major cloud providers, thats as far away as you're going to get. Tech evolves and changes, its not going to be the same as it was in the past, but you gotta adapt.

-8

u/[deleted] Jul 24 '21

If foss movement just "got over it" like you suggest, we would be still buying mainframes from IBM :)

11

u/[deleted] Jul 24 '21

I understand what you’re getting at. But the real power of cloud is in abstraction. You don’t have to understand the intricacies of the host with the advent of containers and a web app abstraction in the cloud. You can just spin up a web app and throw an image at it.

Your wariness isn’t unfounded. But the cloud’s effect on the market is not new. The OS provides abstraction for developers to not understand the intricacies of their kernel. APIs provide abstraction on top of abstraction so consumers don’t need to understand the intricacies of an application layer. The cloud is just that abstraction finally reaching our infrastructure.

There will still be domain experts on the stuff beneath any given abstraction. But you’re right, there will be less of them. This isn’t a bad thing, I don’t think. It’s just progress, and it’s just the way software development goes. The end result is that people in our field get to spend energy on how software can be more useful instead of dealing with the networking, or the hosting, etc.

I don’t think legislating away the differences is the solution. The competition comes with who can implement the better & more robust abstraction. I suspect given time the business will agree on standards for infrastructure abstraction in the same way that we are now seeing standardization across OSs to allow easier cross platform software, or standardization across web browsers so that web experience doesn’t differ so much across browsers. Just gotta let the market do it’s thing.

0

u/[deleted] Jul 24 '21

I understand what you’re getting at. But the real power of cloud is in abstraction. You don’t have to understand the intricacies of the host with the advent of containers and a web app abstraction in the cloud. You can just spin up a web app and throw an image at it.

It really is not that simple. If you have a single team and don't care about stability or security, maybe spinning a web app is just click away. But building infra for multiple teams, environments and staying compliant with stability and security standards, that's just as much work as with on prem, but you are learning only single vendor stuff that doesn't translate anywhere else.

Your wariness isn’t unfounded. But the cloud’s effect on the market is not new. The OS provides abstraction for developers to not understand the intricacies of their kernel. APIs provide abstraction on top of abstraction so consumers don’t need to understand the intricacies of an application layer. The cloud is just that abstraction finally reaching our infrastructure.

That OS is a collaborative effort of many companies, institutions and individuals and can be changed and adjusted to meet your needs. How it works is also a standard across different implementation with minor differences (bash is bash everywhere, so are containers, ansible or even in most cases best kernel settings ;) ).

There will still be domain experts on the stuff beneath any given abstraction. But you’re right, there will be less of them. This isn’t a bad thing, I don’t think. It’s just progress, and it’s just the way software development goes. The end result is that people in our field get to spend energy on how software can be more useful instead of dealing with the networking, or the hosting, etc.

I think it is terrible, we are giving all the power to three huge companies which do not collaborate on standards, but actually make sure stuff is complex and proprietary enough for engineer to have to be specialized in their own solution, which creates a ripple effect of vendor lock in across entire industry.

I don’t think legislating away the differences is the solution. The competition comes with who can implement the better & more robust abstraction. I suspect given time the business will agree on standards for infrastructure abstraction in the same way that we are now seeing standardization across OSs to allow easier cross platform software, or standardization across web browsers so that web experience doesn’t differ so much across browsers. Just gotta let the market do it’s thing.

I don't think that is going to happen - we had those standards for years (terraform, ansible etc), yet cloud companies keep creating their own DSLs for automation that are vendor specific.

4

u/[deleted] Jul 24 '21

Terraform you still had to write vendor locked IaC so that was never a standard. This is a tangent but also, HCL is absolutely terrible and I would even call it a step backwards IMO. I haven’t used Ansible but if your IaC is in a markup language or similar IMO it is subpar.

Regardless, I don’t really want to touch on every point you made, some of which I agree with and some of which I don’t. But I do think you’re being a bit defeatist or pessimistic about it.

2

u/[deleted] Jul 24 '21

Using cloud is no different than using Windows or MacOS, you are tied to something specific to a single company that doesn't really have your best interest in heart.

There is nothing to be optimistic about, I like foss and open standards, cloud is the opposite of that and our entire industry is moving into three incompatible with each other or anything else data centers :/

1

u/[deleted] Jul 24 '21

So let’s say you’re correct - infrastructure was vendor locked on-prem and infrastructure is going to remain vendor-locked in the cloud. Nothing has changed and we were fine until now so there’s nothing to worry about

2

u/[deleted] Jul 24 '21

How was it vendor locked on prem?

1

u/[deleted] Jul 24 '21

The OS. You could be a Windows Server guy. You got a bunch of certs for Windows Servers. This is no different than having knowledge in AWS/Azure.

2

u/[deleted] Jul 24 '21

But Linux is the standard OS in our industry. Windows Server is just what is left from the dark ages of internet.

And yes, good point, AWS/Azure is basically Windows and like any other proprietary software, creates similar issues for everyone.

4

u/[deleted] Jul 24 '21

No that is not my point.

My point is having knowledge in Linux does not translate to Windows in the same way that knowledge in AWS does not translate to Azure.

And I don’t know where you’ve worked, but everywhere I’ve worked used Windows Servers on-prem, standard or not.

2

u/gdahlm Jul 24 '21

Cloud vendors almost exclusively follow Service Oriented Architecture patterns or one of the derived microservices architecture pattern.

If you look at the source for botocore you will see how they use factory methods and simple shims to map between services.

This directly relates to Jeff Bezos' API mandate and explains why if you are not abstracting the back end services from your application you will run into issues.

Various SaaS options of various cloud providers simply cannot be full duplicates of each other because those teams have either different design choices or limitations of their in-house products. Google will use search related offerings and Microsoft will have to deal with restrictions on file locking and memory mapping due to the architecture of Windows.

If you choose to write architect your cloud deployment to use another flavor of koolaid than the cloud providers did, yes you will run into lockin.

If you choose to architect your deployment to decouple from the independent cloud vendors quirks you will have much more flexibility.

As each cloud vendor does have specific offerings that are best in the industry or which may offer a feature that is critical to your needs you may be locked into a single vendor.

But it is your choice on not drinking from the SoA/microservice model and hard coupling to one particular vendors solution.

There are design patterns like the Factory design pattern which are designed explicitly for decoupling the construction of objects from the objects themselves.

The hard part in designing for either on-prem solutions or cloud solutions is realizing and choosing to not fight against the reduction of degrees of freedom which are inherent in choosing a vendor or a solution.

Even companies that are on-prem due to their individual needs or cost structure are moving to more distributed type systems and will benefit from decoupling from the specific vendor's product (even if it is open source).

Decoupling isn't just a cloud concept, it is critical to having effective vendor mitigation options.

→ More replies (0)

2

u/gordonv Jul 24 '21

You can just spin up a web app and throw an image at it.

I feel like this is a mass oversimplification. Even if you were working with a VM like tools like EC2 or dockers, you have to set up region, AZ, VPC, Subnet, ACL rules, proprietary roles, and connect to services.

It's becoming image-less, serverless. Docker is sticking around, but that is subject to setting up cloud infrastructure, also.

You really are learning a new way to do things. It's as shocking as moving from Windows to Linux.

3

u/[deleted] Jul 24 '21

I feel like this is a mass oversimplification.

In Azure you can literally spin up a resource called a WebApp and point an image at it. Then all you need to do is hook up your domain.

The AWS equivalent is probably more akin to Fargate.

2

u/gordonv Jul 24 '21

AWS Amplify and Lightsail.

You write the code, upload it to CodeCommit (AWS Git), Hit deploy. It does everything else.

2

u/[deleted] Jul 24 '21

There ya go! Like I said, I don’t think this is a bad thing.

5

u/[deleted] Jul 24 '21

Only a small part of your story, but it’s “on premises” or “on prem”. A premise is a statement assumed to be true, a premises is a building or real estate owned by a company.

And, well, there isn’t any kind of popular open source Cloud vendor. And as you said, all companies desire Cloud experience nowadays. Things are always changing, but in the short term, we gotta go where the money is to stay relevant and influence the future.

4

u/AgentTyr Jul 24 '21

Openstack is trying to be the popular open source cloud, it just has a huge learning curve like k8s.

Setting openstack up gave me so much knowledge of how some of these cloud providers work, but you need some serious hard to really play with it.

-1

u/[deleted] Jul 24 '21

Only a small part of your story, but it’s “on premises” or “on prem”. A premise is a statement assumed to be true, a premises is a building or real estate owned by a company.

Thanks, I never really thought about it, so glad someone finally corrected me ;)

And, well, there isn’t any kind of popular open source Cloud vendor. And as you said, all companies desire Cloud experience nowadays. Things are always changing, but in the short term, we gotta go where the money is to stay relevant and influence the future.

Yep, money is basically the last thing that's keeping me on this cloud job.

3

u/[deleted] Jul 24 '21

"Yep, money is basically the last thing that's keeping me on this cloud job."

Sounds like you're in for a miserable career, to have to constantly learn about something you hate.

2

u/[deleted] Jul 24 '21

I love foss, like entire point of me going into the industry was passion for foss. But recently it's getting harder to get well paid jobs that do not involve some kind of cloud.

Thankfully there are still options, I imagine this will be last cloud project I worked on after I'm done (at least until I there is nothing else left).

1

u/[deleted] Jul 24 '21

Well as more businesses move to cloud, you may be more in demand for the late/never adopters. I would see it as eventually you become very niche, or obsolete. Hopefully your age/income let's your ride it out until retirement.

1

u/[deleted] Jul 24 '21 edited Jul 24 '21

I don't think on prem will ever become obsolete, having your own data center not tied to a US company has security advantage, especially now and in the future where cold war moved to the internet too ;)

I'm not worried about my financial future in this industry, I can adapt. This job used to be a passion though, but right now it's just money (which is not optimal way to live your life in my opinion).

1

u/[deleted] Jul 24 '21

Maybe, but personally, none of the companies I have worked for can do data centers better than Microsoft or Amazon from a capacity or security standpoint. I think more companies will realize that as time goes on, too.

1

u/[deleted] Jul 24 '21

I don't think having direct ties to US government should be dismissed. State actors are a threat too. Would you host your critical data in a Chinese or Iran owned data center? I really don't see the difference to be honest (objectively).

1

u/[deleted] Jul 24 '21

You get to pick what regions your software runs and I know at least Azure has government compliant regions or zones or whatever. So why rely on staff to build it out when I can just piggyback off what Microsoft has already done?

1

u/[deleted] Jul 24 '21

Government compliance is a shit show, seen it first hand (worked on few gov related projects). Whole process usually involves a lot of big tech sales people having relations with gov officials, everything else is a smokescreen.

2

u/lukasmrtvy Jul 24 '21

Its easy..., You have to go with market, not with things You know .. , cause there is no correlation between these, unless You want to stuck with sysadmin things... cloud and k8s is about abstraction, about generic layer.

1

u/[deleted] Jul 24 '21

k8s is an open standard we can adapt however we want though. I'm totally for k8s when it makes sense, I have problem with proprietary cloud native tools and APIs.

Also market is not always right, right now we see power grab by three huge companies which built their proprietary cloud empires. Hopefully it will correct itself eventually, but we could help it with proper legislation.

3

u/Dreadstar22 Jul 24 '21

I could rehash a lot of what people have already said but I won't because it seems to fall on deaf ears. You've clearly already made your mind up.

Find companies who still want their environments to look like they did in the 90s and 00s and do work for them. Any company that is looking to stay current with cloud or newer tech that relates to cloud pass that business up.

Hopefully there will be enough work for you until you hit retirement. Which knowing SMBs there probably will be. Example all those companies still running XP machines or the finance sector still using that 40 year old cobol code.

1

u/[deleted] Jul 25 '21 edited Jul 25 '21

I could rehash a lot of what people have already said but I won't because it seems to fall on deaf ears. You've clearly already made your mind up.

I think my intentions were pretty clear, I did not even ask any questions, this was all to spark a discussion and vent a little.

Find companies who still want their environments to look like they did in the 90s and 00s and do work for them. Any company that is looking to stay current with cloud or newer tech that relates to cloud pass that business up.

Clearly virtualization is a relict of previous era, that's why entire Azure, AWS and GCP runs on top of that, right? How do you think your cloud actually works under proprietary abstractions?

Hopefully there will be enough work for you until you hit retirement. Which knowing SMBs there probably will be. Example all those companies still running XP machines or the finance sector still using that 40 year old cobol code.

Yep, I always deploy my k8s clusters to XP machines and build my microservices in cobol :)

Cloud only looks easy and cost effective to those who have no idea how any of this works (and spawn a WebApp on Azure then call it a day, who cares about reliability or security).

7

u/rswwalker Jul 24 '21

Like Rock n Roll, the Cloud is here to stay, so better expand your mind to fit in the vendor APIs.

1

u/Kevin_fish Jan 21 '22

Get the feeling you missed his point; he wants to learn Cloud, he doesn't want to Learn XYZ way of doing cloud. its Skills he can tranfer anywhere he goes in IT. Openstack probably the closest to a standard to be honest.

1

u/rswwalker Jan 21 '22

I understood what he was complaining about and I understand there are alternative choices, but if his clients are looking for public cloud architects then he’s going to have to learn the proprieties of each public cloud. Good, bad or indifferent.

3

u/angry_mr_potato_head Jul 24 '21

Idk, object storage is pretty similar across vendors. Everyone asvertises their object storage as s3 compatible despite how stupid I think the boto3 api is

2

u/juniper_dreamer Feb 01 '23

https://frankdenneman.nl/2014/11/11/vcdx-abstract-way-things-indefinitely/

"However sometimes I get the feeling that this level of abstraction becomes an excuse to not understand the underlying technology. As an architect you need to do your due diligence. You need to understand the wheels and cogs that are turning when dialing a specific knob at the abstracted layer. But sometimes it seems that the abstraction level becomes the right to refuse to answer questions"

The sysadmins of old are today's "cloud engineers" and "SREs" yet the old ways are lost as these abstractions become more prevalent. As these next gen "cloud architects" lean on these layers of abstraction as a crutch, they use them excuse to not understand how systems architecture actually looks like.

Classic responses are accusations of being stuck in the 90's and 00's. Yet once "cloud" reaches a critical mass where no one is left to understand how things were done in the past, that's when the price abuse and lockin happens and that is what's truly terrifying.

It's the lack of people who know how to design scalable application services and infrastructure apart from these infrastructure providers. It is truly sad to see you speak so much common sense and get so down voted by the masses.

1

u/Plappippy May 16 '23

You're definitely not the only one who hates the cloud. There are too many services with too many cute proprietary names and it confusing as all get-out. To make matters worse, companies give you every reason to think you're saving a document locally in their interfaces to make the experience "seamless". Looking for the filepath in which you're trying to save a document should be EXTREMELY easy. It's not. Saving files should be a painless process and companies have gone out of their way to make it a task to find your local drive and that, to me, is inexcusable.

I just spent a half hour trying to save a measly Microsoft 365 resume to my external SSD on my MacBook Pro. I actually had to RESEARCH that process. No one should have to research that! And I'm not a n00b! I've been working in IT for years now!

1

u/wingerd33 Jul 24 '21

I agree with you. People will chime in with a lot of hate and disagreement on this post, I imagine. But I've worked extensively in both environments, and with each in different types of organizations (large companies to startups, poorly managed to beautifully managed).

I think the reason many people have a bad taste in their mouth about running physical infra is they've only experienced it under poor management.

I could talk for an hour or two on this subject and give some very detailed and experience backed examples and reasoning. But most of the industry can't see the forest through the trees when it comes to the cloud vs self hosted argument.

It's disgusting how much money people spend on engineer time just trying to finger fuck AWS IAM policies, and then don't even trust themselves at that because it's an overly complex piece of shit, so they then (on top of paying engineers to spend 1/3 of their time on it, or building dedicated teams for it) pay for expensive automated tooling and outside consultants to look for flaws in their IAM configurations. And then they'll proceed to argue with you until they're blue in the face about how they've saved so much money by not paying someone to run a network. And that's just one facet of running in the cloud.

Here's another thing - organizations will rewrite their apps to be abstracted from the infrastructure, more fault tolerant and scalable so that they can run them more easily and efficiently in the cloud, and then attribute their gains in developer efficiency and labor cost savings to their move to AWS. Like bruh....... I can auto scale and automate deployments across a fleet of Linux VCRs if the code is abstracted away from the infrastructure. HP does CI with printer firmware for fuck's sake, which by nature can't be abstracted from the hardware. I've run on commodity and refurbished servers, using Proxmox and XenServer as the hypervisor, and we had full CI and the ability to auto scale, service discovery, containers, could still use IaC, etc - all the trendy DevOps words you can imagine.

But I guess it makes more sense to pay the same number of, if not more engineers, third party vendors, and pay AWS' engineers and profit margins too, and still require them all to know a bunch of complicated shit (that's why we're paid well, right?) than to learn how to PXE boot some servers and create VXLAN networks and secure an ssh config file.

"Oh but we converted our CapEx to OpEx!" - I just don't even know what to say to that one other than J.F.C. First of all, you'll spend FAR more money sending Bezos to space than you'll pay in interest if you want to finance equipment. Then for all the IAM engineers you don't need, you can take 1/10th of that money and pay your equipment loan and use the rest for gold teeth or strippers or whatever tickles your fancy. So then it looks like OpEx on your budget sheet, but in 24 months or whatever, you own it and the expense goes away for like the next 6 years (oh yeah and don't even get me started on 3 years "refresh cycles" for servers - as if we're all not running 6-8 year old Dells in our basement full of dust and humidity and they're just fine).

0

u/[deleted] Jul 24 '21

[deleted]

-5

u/[deleted] Jul 24 '21

First point(...)

This is what I recommend when asked - avoid the cloud. If you need worldwide presence, edge computing and CDNs are the way to go.

Second Point(...)

I don't think any cloud is better for anyone. I honestly can't think of a use case where cloud makes sense. Maybe when your engineering resources are mostly wordpress related and you don't really care about stability or security, but want to ship something fast by clicking stuff.

Final, third point(...)

Oh believe me, I tried... We even HAVE to use cloud specific VMware implementation (due to proprietary, but core application requirement) where we deploy and configure using terraform and ansible, but no... we can't just use that for everything else, we have to go NATIVE.

2

u/BzlOM Jul 25 '21

I don’t think any cloud is better for anyone. I honestly can’t think of a use case where cloud makes sense. Maybe when your engineering resources are mostly wordpress related and you don’t really care about stability or security, but want to ship something fast by clicking stuff.

Most of the things you listed here are factually incorrect: Stability and security is just better in the cloud. You cannot replicate the stability of a resource on premises with the same ease you can in cloud.

Even when using multiple DC's which in itself is a lot of hassle won't give you the same piece of mind any cloud does. You have to rent or collocate hardware, always keep you eye on failures, interact with DC engineers when something goes wrong etc etc etc. And you usually need more than 1 engineer responsible for all that stuff and a lot of time is spent on maintenance.

Well the cloud cuts on all of that. Your servers will be up and running basically forever - the hardware upgrades happen behind the scenes, the software stack upgrades happen without a hitch with minimal to no issues if you know your stuff, everything will keep working if you did your redundancy properly.

The same works for on prem but with a much bigger cost attached moneywise and timewise. In cloud you have "infinite" resources basically for any requirements at your fingertips - you can spread your loads and backups globally and never encounter ANY downtime even if a whole DC or even geographical zone encounters an outage. It's very inefficient to do all of this on your own.

The same goes for security - your infrastructure is automatically patched for you as soon as there's a vulnerability patch, or you get notified about it and can implement the fix as soon as you are able. No more need to stay subscribed to security sites, and you still have the flexibility to secure you software stack as you see fit.

Reading your whole thread feels like a child's tantrum. Look we get it - you don't like vendor locking, it's fine. This doesn't mean cloud has no uses only because you can't see any or don't wanna adapt to the changing industry.

1

u/[deleted] Jul 25 '21

Most of the things you listed here are factually incorrect: Stability and security is just better in the cloud. You cannot replicate the stability of a resource on premises with the same ease you can in cloud.

Ofc you can if you know what you are doing.

Even when using multiple DC's which in itself is a lot of hassle won't give you the same piece of mind any cloud does.

Cloud doesn't really invalidate multiple DCs, you still in most cases need a second infra that is in another cloud region for disaster recovery. How is that different? Do you think that cloud is some complete abstraction that any resource is automatically replicated across entire world or something?

Azure, AWS and GCP are just big pools of many data centers and only some stuff works across regions without setup on your end. Cloud is not that different than traditional data centers, it just adds bonus abstractions on top of standard services.

You have to rent or collocate hardware, always keep you eye on failures, interact with DC engineers when something goes wrong etc etc etc. And you usually need more than 1 engineer responsible for all that stuff and a lot of time is spent on maintenance.

If you think that you can get away without that by using the cloud, you are delusional. All of that is just shifted into different level of abstraction behind proprietary APIs and tooling.

Well the cloud cuts on all of that. Your servers will be up and running basically forever

Not forever, as long as you will cover your bills which eventually will eclipse your old DC investment which would still be running at the cost of minimal maintenance if it was done right.

the hardware upgrades happen behind the scenes

Sure, but also you can't really optimize anything. You have to increase your monthly/annual billing to get more performance instead of a one time purchase of extra ram, different CPU or even entire new machine that will pay for itself eventually.

the software stack upgrades happen without a hitch with minimal to no issues if you know your stuff

Yea, no, this is not how any of this works. Maybe some native services like functions or storage accounts, but those are not always optimal, everything else requires as much effort as on prem (VMs, containers etc).

everything will keep working if you did your redundancy properly.

Same on prem, but cheaper :)

The same works for on prem but with a much bigger cost attached moneywise and timewise.

Initially. In long run your 10 year old machines if maintained properly will outperform any cloud today.

In cloud you have "infinite" resources basically for any requirements at your fingertips - you can spread your loads and backups globally and never encounter ANY downtime even if a whole DC or even geographical zone encounters an outage. It's very inefficient to do all of this on your own.

If you need worldwide presence, you can use CDNs and edge networks to achiev similar scenario at lower cost. Hell, you could even use THE CLOUD in that capacity, but all data center providers are much cheaper than holy trinity.

The same goes for security - your infrastructure is automatically patched for you as soon as there's a vulnerability patch, or you get notified about it and can implement the fix as soon as you are able. No more need to stay subscribed to security sites, and you still have the flexibility to secure you software stack as you see fit.

Yea, let's fire all engineers and rely on Microsoft people to keep your infra up and running and safe, after all they have such a good track record of reliable services and solutions :D

Reading your whole thread feels like a child's tantrum. Look we get it - you don't like vendor locking, it's fine. This doesn't mean cloud has no uses only because you can't see any or don't wanna adapt to the changing industry.

And you sound like a manager with very little engineering experience that bought into Azure/AWS/GCP marketing and PR.

2

u/BzlOM Jul 25 '21

I'm not trying to convince you here - I just stated that what you're saying is simply wrong. Whether you accept it or not is not something I care about.

Ofc you can if you know what you are doing.

Also you clearly don't understand the difference between "you can do it" and "you can do it with more ease".

Not gonna bother having an argument with a person without a basic common sense.

1

u/[deleted] Jul 25 '21

Not gonna bother having an argument with a person without a basic common sense.

There we go, you did not disappoint ;)

0

u/[deleted] Jul 24 '21

[deleted]

-1

u/[deleted] Jul 24 '21

Disagree, mostly on your second point. You mostly have to look at the features and the pricing. If you're already using Azure AD for example and a few other things, stay there. If you're using Microsoft products in general, I've found Azure will handle it better (obv). SQL Server may be more expensive on Azure SQL Database, but I find that it spins up faster, fails over faster, everything faster than on AWS. I've had some nightmare moments on AWS if your RDS DB isn't sized right.

Yea, but using Microsoft products was already a mistake, so you are just doubling down on bad decisions :) I'm sorta serious there, I understand that some stuff is hard to replace and it's better to iterate.

As for not getting security or stability, I'd highly disagree. Even simple stuff like firewalls are mandatory via security groups, etc.

But you have to setup that environment first, by default most resources just become public after deployment. Configuring your enviroment to be secure is as complicated on prem as it is in the cloud.

I see scary stuff on on-prem environments all the time. People try to squeeze every bit of juice out of their hardware purchases and end up creating some stupid configs.

That is true, but you can fall into that trap in the cloud the moment you start optimizing your billings ;)