• filcuk@lemmy.zip
      link
      fedilink
      arrow-up
      6
      ·
      edit-2
      15 hours ago

      I work with an azure database and 15% (!) of the time the connection handshake times out for no reason known to man.
      This is well documented on their end. The solution? ‘Implement a retry logic’

    • addie@feddit.uk
      link
      fedilink
      arrow-up
      19
      ·
      1 day ago

      Azure’s documentation is the worst fucking bullshit that I’ve ever read in all my days, and just about every single page or tool (including the CLI) has an integrated slopbot that routinely recommends commands and REST endpoints that don’t exist; it’s slow as fuck, and to do even the simplest things is agonising. But to give them their dues, their recent uptime has been pretty good.

      Truth be told, I’ve even come round to thinking that I prefer using Azure to Google Cloud Platform. Using any of Azure’s features is a pleasure akin to cutting yourself with a rusty nail and then falling in a sewer, but at least it has some features. GCP is like they implemented a quarter of the very basic functionality and then got fed up, decided to call it a day.

      • GreenKnight23@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        19 hours ago

        I worked with some Azure devs a few years ago. they looked tired. I mean real fuckin worn down.

        compared to the Amazon guys, it was like night and day. not to say AWS docs are much better, but they are better.

      • Teppa@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        edit-2
        19 hours ago

        I’ve been using it for a while now and am surprised how shitty it is. I remember not having a routing table and it allowed a single packet to be routed to the endpoint and then stop, it doesnt even make sense how that can happen. Intune is even worse, its missing extremely basic functionality, you cant even clone a device config its that bad.