I've recently been diving into cloud architecture and trying to create serverless workflows, and I have to say, learning Azure has been a challenge. I'm already in IT, so I thought I'd be able to pick this up quickly, but Azure Functions have given me nothing but headaches. The function never triggers, and I feel there's a lack of helpful tips from Azure to guide me through the process. Additionally, certain function plans are restricted in the free tier, which complicates things further. I'm also struggling with the log system, as you have to set up queries just to see what's going on, unlike AWS where metrics are easily accessible. Has anyone else experienced similar frustrations with Azure?
6 Answers
In my experience, Azure Functions can be set up easily using the Core tools or VS Code. It took me some time to get used to, but once you understand the architecture and how the resources connect, it gets a lot easier. Getting your architecture planned out right is crucial, so maybe take a step back and really map things out. It can make a world of difference!
I totally get what you're saying. Azure can seem overly complicated, especially compared to AWS. I've had to jump through hoops just to get quotas increased or figure out confusing documentation. It makes you miss how AWS just keeps things simpler!
I've had a similar experience. I found Azure's documentation to be inconsistent and not very user-friendly, especially when trying to implement event-driven architecture. AWS has a more seamless event-driven approach, while Azure requires you to find dedicated services for that. It feels a bit clunky, and honestly, sometimes the communication via MS Graph can be a hassle due to undocumented limits. Just my two cents!
Right? I was looking into both platforms, and I just felt like AWS made everything so straightforward. With Azure, it seems like there's a lot of extra legwork to get things working.
Honestly, I've had my struggles too. Azure definitely challenges me at times, but I've learned to adapt. I lean on Azure for better role-based access control, which I find a bit easier to manage than AWS IAM. Documentation isn't the worst once you get used to it, though I can see where the inconsistencies throw people off. It just takes a little practice, I guess!
I hear you, but I still think AWS is way more intuitive than Azure. The roles and permissions in Azure are a mess!
I used to think Azure was going to be simple, but after using both AWS and Azure, I have to say AWS is way easier to get started with. I often feel like Azure's services are hyper-focused on enterprise needs, which makes it less friendly for developers. I’d generally recommend starting with AWS if you're new to cloud.
You're definitely not alone! Azure can feel really complicated at first. I think it has a steep learning curve that improves with time and experience. The documentation can be confusing, and it’s easy to get stuck on one problem. Just wait until you start noticing gaps in the docs—then you'll know you’re really getting the hang of it! But sometimes it can get frustrating when things don't work as expected. I’m rooting for you!
Seriously! I had a quota request that took me a week to get sorted—it's insane!