Hacker Newsnew | past | comments | ask | show | jobs | submit | woot01's commentslogin

It's probably time to call it virtual-first, rather than remote-first, cause remote makes people think isolated.


> cause remote makes people think isolated

Which, of course, it is.

Isolated: "separated from other persons or things; alone; solitary" [0], "separate from others" [1].

Remote: "far apart; far distant in space; situated at some distance away" [0], "separated by an interval or space greater than usual" [1].

[0] - http://www.dictionary.com

[1] - https://www.merriam-webster.com


Taleb's book often came back to the example of the relatively free market that is a city's restaurants. Any one restaurant is fragile, but the entirety of the restaurant business in a city is antifragile - failure of the worst makes the marketplace better.


this is what Salesforce does - they have publicly visible shards in the url (na11, na14, eu23, etc) and login.salesforce.com redirects you to your shard when it figures out who you are.


For anyone considering this, reconsider. It bit me many times.

In general, over time, load on some shards will increase while others decrease. Migrating a customer from one shard to another will likley cause a short outage for them, and many bugs down the line when they've bookmarked all kinds of things.


You need to preserve the name<->customer association and maintain another key that you can use to split traffic at the LB in case a customer outgrows their shard. But personally I think it looks hokey and should not be something a customer sees anywhere but perhaps a developer tool or sniffer.


could that not be resolved with a reverse proxy or load balancer trickery? ie; hide the shard name externally.


HTTPS does not protect you against sending data to a host owned by another company.


Yes it does, the cert presented by api.othercompany.com would not pass validation when you're trying to open a connection to api.intendedcompany.com.


Correct, but they wouldn't be able to decrypt the data.


The data doesn't even get there, the handshake kills the connection before that.


Except it's really hard to provide treatment for those illnesses if you can't find them regularly, so giving them a home, first, and then bringing services to that home is the only policy that makes sense. Seems to be working in Utah.


So, people should just stop trying to improve things?

XKCD 927 should be considered harmful, as while it is true that's how things sometimes happen, to start quoting it everywhere is to try to shut down people from innovating, and that's anything but helpful.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: