321–330 of 359 posts
Earlier quoted context omitted.
My experience is the opposite: AWS has more features on paper but most of them exist only to tick a checkbox. Azure has more integrations between their offerings, as well as Azure Active Directory, and Microsoft 365.
Why do I want AD or Microsoft 365?
AD = identity, access, privileging, SSO
Earlier quoted context omitted.
My experience is the opposite: AWS has more features on paper but most of them exist only to tick a checkbox. Azure has more integrations between their offerings, as well as Azure Active Directory, and Microsoft 365.
And Active Directory integrates horribly with everything outside Microsoft.
Earlier quoted context omitted.
Amazon's own chips are ARM. ARM requires somewhat specialized builds of software that are likely different than development instances, CI/CD, and/or local dev machines. It's not insurmountable but does certainly complicate usage.
Your local dev machines might be Macs though, in which case it might be easier for you to go with ARM servers than x86.
Earlier quoted context omitted.
"Multi-cloud from the outset" is probably the single-worst generic cloud advice that I think anyone could be given. In professional cloud consulting the rule of thumb is to do one cloud with excellence until you even think about another one. And even that is really just kicking the conversational can, as both becoming excellent and actually needing multi-cloud combined is one-in-a-billion.
On top of which, startups often don't have that luxury; you have often need to ruthlessly prioritise your effort.
Yes it’s weird that you have to ask them for instances which some actual physical person looks at your request, thinks about it and says yes or no to. Instead of providing you with a list of the resources they do have, you have to play this weird game where you ask for specific instances in specific regions and then within several hours someone emails back to say yes or no. If it’s no, you have to guess again where y…
I briefly worked on an Azure team, and what I remember hearing (a few years ago) was that they were building out data warehouses as fast as they can, but they simply cannot keep up with demand. A good problem to have, I thought, but maybe not in light of this news!
I just Googled it. Gartner estimated $125 billion.
https://www.fiercetelecom.com/telecom/cloud-and-colocation-d...
Earlier quoted context omitted.
Thanks a lot! You are totally right, it is for sure something we will find a solution for. But honestly, do I not want to. As a startup, you have very few resources and deliberately place some exact bets. Deprioritizing everything to work on something for a long time that was not prioritized, just to then end up again where you were before (a working cloud solution) is the last thing any startup should be forced to d…
I disagree with the other poster you should have been multiregion from the start. It adds a load of complexity and failure cases for early stage Startups. Very poor position to be in, apparently this happened in azure UK recently too.
People saying "shame on you for not being multi-region" are missing the point: This is a German company with German customers subject to German data residency laws. For them to store German data in a region besides Germany requires getting informed consent from the "data subject", who must be "pre-informed about the potential risks involved in cross-border data transfer". [1] This is why Azure has a dedicated German…
No reason why Azure can't run multiple "regions" within Germany proper. Their current region is in Frankfurt; no reason why they couldn't launch regions in Munich or Hamburg as well. Then German companies could go multi-region while staying fully compliant with German data sovereignty laws.