natevancouver
natevancouver on Hacker News
Usually because the company already pays an AWS bill. No one will care if you add another Lambda function, but to use an alternative you’ll have to get past some gatekeepers.
Does the project have a testing framework in place? How is the project built and distributed? Can testing be integrated into its CI/CD pipeline? Is there a CI/CD pipeline? Adding frameworks and infrastructure to a project is one of those things that is a lot more work than it appears to be. They should do it, for sure, but I wouldn’t dismiss it as trivial on a decades-old system that was never built for it.
In my town Google Maps has traffic “data” for every side street and it’s usually wrong or irrelevant. A red light at an intersection will show up as a traffic jam and then I’ll get weird routes trying to go around it.
Traffic for freeways, on the other hand, is amazing.
This likely has to do with the quality of traffic data provided by the municipality. But Apple Maps doesn’t have the same problem. Their side-street traffic data is reliable around here – very surprising.
Note this applies to Fremont. I have no idea about the other DDoS attack affecting Newark.
And even though this got my servers back up, they are responding slowly. At least requests are being served.
The problem is at Linode’s DNS resolvers. For my own servers, I worked around it by changing to Google DNS, and ensuring it was listed
before Linode’s own DNS servers.
https://gist.github.com/natesilva/11409605
There is mapping data, and then there is place data (where a business is located).
Google and Apple must use the same mapping data, because I see the same errors in both apps. Of course with Google, after I report the error it gets fixed. I can’t say the same for Apple. And Navteq* has more detailed and accurate data than either of them.
What Google has is superb place data. Apple has… Yelp.
*Assuming you have recent Navteq data. Not the nav system in your car that hasn’t been updated in 2 years.
* Due to the nature of patents, “patent-free” tech does not exist.
* At scale H.264 is crazy cheap. It costs $6.5 million for YouTube to serve 72 billion hours of video. Still, it is infinitely more expensive than free.
SERVFAIL doesn’t mean they dropped the records (that would be NXDOMAIN). It does mean their nameservers aren’t responding.
It depends on what your local DNS has cached. Also, I’m finding that 1 out of 5 of their DNS servers is still responding from my location (not too far from Vancouver).
Where did you get this information?
When I looked at their site I didn’t see information about what kind of SSDs they are using and, based on the price, assumed they are MLC (consumer grade). I’d never want that on a server.