I don't think so. We switched most our workloads from k8s to ECS (mix of EC2/Fargate launch types) because clusters were hard to maintain. Now everything is visible in Console and we now have tech support down to the ECS Task level. Before doing that, management pestered AWS about future of ECS. AWS insisted that it is actively developed, and lots of their internal stuff runs on ECS, not k8s.
You need to understand why AWS churns out silly services every month. Tomorrow there will be new HypedTech, and days later new AWS ElasticHypedTech service. It's just good business.
* the magic permissions ghost that runs in Azure whose job it is to inexplicably deny you resources to things won’t interfere
* Said Azure service will stay up long enough to be useful
* you finish writing the insane amount of config Azure services seemingly require before the heat death of the universe.
* Azure decides that it likes you and won’t arbitrarily block you from attaching things to your cluster/nodes because it’s the wrong moon cycle/day of the week/device type/etc
* you can somehow navigate Azures kafka-esque documentation got figure out which services you’re actually allowed to do this with.
It is only a slight exaggeration to say that Azure is the most painful and frustrating software/cloud product I’ve used in a long time, probably ever, and I earnestly look forward to having literally any excuse to migrate off it.
Azure’s enterprise sales machine will make sure your wait is long. They sell bulk block deals to CIO, not to devs directly.
> In 2030 it will rock!
Apart from _maybe_ VSCode, what has MS made that makes you go "this rocks"?
Fair play, I'm either ambivalent or not a fan of most of those - except maybe the Xbox, I have a PS4, but the X1 is pretty nice.
> Azure DevOps...one of the poorly documented services
So like, all of them? Hahahaha
> SQL Server on Linux
Next to Azure, this is the next biggest cause of issues at work for me, and I haven't seen any wild advantage of this over Postgres, with the disadvantage that pretty much every linux/macOS and open source tool I use is much happier to plug in to Postgres instead.
I really think that's unfair, untrue even. I work with a lot of services on a regular basis, and while it very frustrating to find something with missing documentation, it seems to be confined to certain services, and mostly then for new'ish features. In those cases, they are quite responsive on GitHub.
> Next to Azure, this is the next biggest cause of issues at work for me, and I haven't seen any wild advantage of this over Postgres, with the disadvantage that pretty much every linux/macOS and open source tool I use is much happier to plug in to Postgres instead.
I also personally prefer Postgres, and by a margin. But I have also worked with SQL Server on Linux, and haven't found any differences over SQL Server on Windows - it just works.
I was being a bit tongue-in-cheek here, but that is good to know they're responsive on GitHub.
> But I have also worked with SQL Server on Linux, and haven't found any differences over SQL Server on Windows - it just works.
Sorry I meant SQL Server in general, not specifically the linux one. You're pretty much relegated to using ODBC and messing around with all the requisite configs there, which is fine once it's working, but it's never as nice and straightforward as other db's ime.
So never dealth with Oracle outside Java?
I can't speak too broadly but mssql/tedious modules for node don't use the ODBC interface and work pretty well regardless of platform with minimal issues.
My biggest issues with MS SQL Server for Linux vs Windows comes down to some of the features that most dbms don't necessarily support in the first place.
> Next to Azure, this is the next biggest cause of issues at work for me, and I haven't seen any wild advantage of this over Postgres, with the disadvantage that pretty much every linux/macOS and open source tool I use is much happier to plug in to Postgres instead.
It's been a pretty great thing for me, if only to be able to get a better local experience with Docker. A lot of our applications are centered around MSSQL Server (for better or worse), I'll say that despite the costs, replication in MS SQL is night and day better than Postgres.
It really depends on how you use SQL Server because it doesn't support all the features of the Windows version and if software uses those features, it gets pretty ugly. That said, if you develop against the Linux version, you're unlikely to have issues deploying to the full version, or Azure SQL.
Of course on other projects we're using PostgreSQL and I tend to prefer it as binary json support is huge imo. Getting other devs to understand that you don't need to break off child records into separate tables that require series of joins, that's another story.
A big reason is that C# has always 'rocked' and now they've got a platform that can be deployed on linux that feels complete. That's super awesome of them. And their documentation for dotnet core is top-notch.
That said, the last windows 10 auto-update managed to cripple the UI and (for real) network speed of the computer it ran on. That definitely didn't make me feel great about MS.
It's a mixed bag. It's almost as if the company is huge and we cannot say much about it as a whole.
* no good working examples in docs
* docs hard to read
* docs are not consistent with reality
* the web portal UX is inconsistent and outright weird (when you navigate through resource group, you can scroll back horizontally to previous context/screen; what a joke)
* there are a gazillion preview api versions that never gets released officially.
* and if you’re lucky to work with azure devops, it’s like building a house of cards with different card types and sizes
I’ve worked with AWS and GCP in the past. Indeed Azure is often chosen by CIO’s rather than people that have to work with the service every day.
Docs being hard to read and inconsistent with reality is a big point. My favourite mismatch is the storage classes one: it turns out there's actually 2 different grades of SSD available, but their examples and docs only mention premium SSD's. I only discovered "normal" SSD because they happen to auto-create a storage class with them in your Kubernetes cluster. The adventure to figure out whether you can attach a premium SSD to an instance is a whole new ball game - trying to find which instances _actually_ allow you to attach them is like looking for a needle in a haystack. Why are they so difficult about it? AWS is like "you want an EBS volume of type io1? There you go, done". Azure: "oh no, you _can't_ have premium ssd. Because reasons".
I found a few instance types when I went looking, but their interface does not make it easy to figure out which ones are premium eligible, but I do remember the price going up not-insignificantly for a premium capable machine, which feels about like double-dipping if you’re also paying extra for the SSD.
Setting them up is a pain: why do I need a different set of permissions to set up a service connection for every single pipeline?
Why does my manager who has what we can only assume is a _marginally different_ set of permissions just see an approve button for the service connection but I get taken to page asking me to setup a service connection? (Which ultimately fails anyway)
Why does it want to create a Kubernetes secret on every deploy?
It does funny things with the output from Kustomise, and we discovered we had to add parameters in to make it stop adding characters to the end of the generated configs.
Did you once, look at a pipeline? Be prepared to get more emails from devops than an overly-eager marketing department.
If you have a Terraform in your Pipeline, Azure will lie to you about the status of you Apply's: it'll tell the pipeline that the resource was created, when it fact it was not successfully created, this will mess up your TF state.
If you deploy to a K8s cluster, and your application crashes during startup for some reason, the pipeline treats this as a failure, IMO that's beyond it's set of responsibilities: it should take care of making sure the deployment configs get to Kubernetes, application failing to start is the concern and responsibility of the developer, not the CI pipeline.
> Those configs feel like they're longer than a Russian literature novel
Assuming you mean pipelines YAML files, I can't agree - my pipelines are always quite terse, and you can also split them into multiple files if wanted. IME they are no longer than pipeline configs from AppVeyor, Travis etc.
> Setting them up is a pain: why do I need a different set of permissions to set up a service connection for every single pipeline?
IIRC, you don't - I'm sure there is an option when creating the connection to grant permission to all pipelines.
> Why does my manager who has what we can only assume is a _marginally different_ set of permissions just see an approve button for the service connection but I get taken to page asking me to setup a service connection? (Which ultimately fails anyway)
Working with service connections is definitely a PITA, but since you need to have the requisite permissions in Azure, I'm not sure there is a good way of handling things.
> Did you once, look at a pipeline? Be prepared to get more emails from devops than an overly-eager marketing department.
I work with pipelines all the time, and don't recall getting a single email from Azure DevOps marketing people.
Oh sorry I worded that poorly - I mean my inbox is absolutely crowded with emails from devops itself. I'm sure I can turn it off, it's just absurdly chatty out of the box.
> Assuming you mean pipelines YAML files, I can't agree - my pipelines are always quite terse, and you can also split them into multiple files if wanted. IME they are no longer than pipeline configs from AppVeyor, Travis etc.
Yeah I was, how long are yours? I've got a couple here that are bordering on 300 lines which is pretty wild considering I only need to build a container and push it to K8s... Best CI/CD I've had was with Drone: equivalent build YAMLS were probably 20-30 lines, tops
> Working with service connections is definitely a PITA, but since you need to have the requisite permissions in Azure, I'm not sure there is a good way of handling things.
Compared to AWS' permission model, my experience is that it's distributed amongst throughout a number of locations, and needlessly complicated to ensure that team members have the permissions they need.
As to the pipeline length, most of my interactions are npm/node scripts via package.json within various projects . Often even other language projects I'll use node/npm as a task runner which makes for decent glue code. That tends to keep my pipeline files much smaller as it's usually...
1: add tools
2: configure environment injections
3. run npm script(s)
At least then I have a little more control. Same for github, gitlab and others.It seems Azure and AWS permissions seem to be at opposite ends of the spectrum. I will say I find dealing with Azure's Storage services (Blob, Table, Queue) to be really nice for a lot of common use cases. At least the tables and queues.
As a random example, I have a pipeline that builds a multi-arch container image for both x64 and ARM and pushes it to ACR, and also builds, tests and deploys a Function App, and publishes artifacts. The main pipeline file is about 75 lines, and it makes use of 3 other files that setup docker buildx, login to ACR, set the build version, that kind of thing. In practice, I find these kind of "setup" tasks often use as many lines as the main file, but it's often reusable stuff, and splitting them out into templates is really helpful, I think.
In total, it's around 120 lines for all the pipeline files. I am keen on makefiles though, so a lot of the actual build script is in them, ensuring we can also build locally too.
Another example is a web app, where it builds, runs unit and integration tests in a container, and publishes build artifacts for a release pipeline to take over deployment. It also has a 2nd job where it builds some Windows-specific stuff in a Windows agent. Whole thing is less than 100 lines.
The simplest pipelines will be less than 30 lines - for example, the web app I mentioned could easily be done in 30 lines if tests didn't run in a container.
I don't mind taking a look at your YAML file if you think another pair of eyes would help (my email is in my profile, and you can anonymise bits of your file if you want).
Yeah, they are embracing more income. Not really that surprising.