The Inappropriate Bundling of Services SAMIT Video
-
Registrar, DNS, Service Host or ISP, Email and VOIP? I talk about why tightly coupling such different services together increases risk, and often cost, and how we can think about and approach service decoupling to protect ourselves from combined failure domains.
-
There is more expense in managing this though. At least from the person managing it point of view.
It might not be much, but it's not zero. -
@dashrender said in The Inappropriate Bundling of Services SAMIT Video:
There is more expense in managing this though. At least from the person managing it point of view.
It might not be much, but it's not zero.That can be the case, but often is the opposite. Using best of breed services, or purpose selected, and reducing cross talk can make things easier. For example, managing DNS in CloudFlare is a fraction of the effort of managing it in GoDaddy. For one it is "what they do" for the other it is "what they have to do and hope you do as little as possible." Keeping lots of cooks in their own kitchens rather than sharing a kitchen also makes things less friction, rather than more. Bundling rarely decreases effort, even though it sounds like it should bring it.
-
@scottalanmiller said in The Inappropriate Bundling of Services SAMIT Video:
"what they do" for the other it is "what they have to do and hope you do as little as possible." Keeping lots of cooks in their own
Let's use GoDaddy as an example, short of them not supporting a record type, what's the issue with GoDaddy DNS and registrar in one account - specifically?
-
@dashrender said in The Inappropriate Bundling of Services SAMIT Video:
@scottalanmiller said in The Inappropriate Bundling of Services SAMIT Video:
"what they do" for the other it is "what they have to do and hope you do as little as possible." Keeping lots of cooks in their own
Let's use GoDaddy as an example, short of them not supporting a record type, what's the issue with GoDaddy DNS and registrar in one account - specifically?
That's a good one to look at specifically.
- GoDaddy DNS is cumbersome to use and wastes time. This is a vendor issue, not a bundling one.
- GoDaddy DNS has a less than stellar uptime track record. This isn't a service they are known for, they don't really care as serious customers don't use it for this.
- Under normal operations, non-IT staff should never have access to DNS records and IT staff should never have access to corporate identity records. Using GoDaddy for both removes the possibility of keeping those highly critical roles separate and puts the company in danger of IT running off with the company identity and business people of accidentally taking services offline.
- As above, there is no safe means of using contractor support for simple IT tasks.
- GoDaddy doesn't offer key DNS related features like caching.
- You are either stuck using a single registrar (often not even possible as different registrars offer different domains) or stuck managing DNS is multiple locations. It lowers flexibility.
- An outage from your registrar can take out your DNS with your risk mitigation removed as part of the outage. Otherwise a DNS outage can be protected against from the registrar and a registrar outage has no production impact. This is the biggest issue, it creates a whole form of risk that need not exist.
