5 ms·

> Robinhood said last week that a confluence of factors -- record account sign-ups along with highly volatile and historic market conditions -- led to unprecede

> Robinhood said last week that a confluence of factors -- record account sign-ups along with highly volatile and historic market conditions -- led to unprecedented stress on the firm’s infrastructure. > That heavy load caused the so-called Domain Name System, or DNS, to fail. Not a developer. Is it not customary just to hard-code IP addresses instead of domain names when the app is communicating with your own servers? I would assume that would make every interaction faster and is something that would be done anyway.

JacobHenner 7y ago
No, especially if DNS-based service discovery is being used.
zymhan 7y ago
Many services use DNS to distribute requests across regions or to balance load or for failover purposes. An IP address is less flexible for those purposes.
brianpgordon 7y ago
Certainly not. DNS is a good way to decouple logical service names from actual machines. This is particularly useful with containers so that you can put your services wherever the orchestrator wants them. It can also be used for load balancing and resiliency.
scarejunba 7y ago
No. You usually use service discovery and it's often DNS based. You can do that if you use Consul and stuff like that and it allows you to bring in new things on the fly.
salawat 7y ago
Not if you're using something like AWS since the IP is not guaranteed. If you're managing your own server farm though, yes, you can statically allocate IP's and cut out DNS in it's entirety. A practice to this day I do not understand why more places don't. Then again, I was always comfortable with memorizing phone numbers and the like.
- mr_toad 7y ago
  https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-... Much quicker to remap an elastic IP than wait for DNS changes to propagate.
ohiovr 7y ago
Straight ip addresses can't have tls certs afaik.
- gruez 7y ago
  counter-example: https://1.1.1.1 https://1.1.1.1
  - ohiovr 7y ago
    Interesting
- axaxs 7y ago
  It cannot be the common name(the main domain), but can exist as a SAN name and work just fine.

JacobHenner 7y ago

No, especially if DNS-based service discovery is being used.

zymhan 7y ago

Many services use DNS to distribute requests across regions or to balance load or for failover purposes. An IP address is less flexible for those purposes.

brianpgordon 7y ago

Certainly not. DNS is a good way to decouple logical service names from actual machines. This is particularly useful with containers so that you can put your services wherever the orchestrator wants them. It can also be used for load balancing and resiliency.

scarejunba 7y ago

No. You usually use service discovery and it's often DNS based. You can do that if you use Consul and stuff like that and it allows you to bring in new things on the fly.

salawat 7y ago

Not if you're using something like AWS since the IP is not guaranteed. If you're managing your own server farm though, yes, you can statically allocate IP's and cut out DNS in it's entirety. A practice to this day I do not understand why more places don't. Then again, I was always comfortable with memorizing phone numbers and the like.

mr_toad 7y ago
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-... Much quicker to remap an elastic IP than wait for DNS changes to propagate.

ohiovr 7y ago

Straight ip addresses can't have tls certs afaik.

gruez 7y ago
counter-example: https://1.1.1.1 https://1.1.1.1
- ohiovr 7y ago
  Interesting
axaxs 7y ago
It cannot be the common name(the main domain), but can exist as a SAN name and work just fine.