Boundary already has a bunch of open source stuff and more coming soon. https://github.com/boundary. Our first offering will be as a service. If you want to talk more ping me [email protected].
What I find objectionable about the video is not his identification of team quality being the problem. It's his total abandonment of responsibility for it as a founder. That he'd say he just woke up one day surrounded by B and C players he hadn't interviewed makes it seem like everyone else was running amok and he is not to blame. Trashing the reputations of his ex-employees in order to save face on a tech show is irresponsible at best, and at worst a demonstration that he is unfit to lead a team of any size.
In west Philadelphia born and raised. On the playground is where I spent most of my days. Chillin out, maxin, relaxing all cool, And all shooting some b-ball outside of school. When a couple of guys who were up to no good started making trouble in my neighborhood. I got in one lil fight and my mom got scared and said "You're moving with your auntie and uncle in Bel-Air." I Begged and pleaded with her day after day, but she packed my suitcase and sent me on my way. She gave me a kiss and then she gave me my ticket. So I put my walkman on and said I might as well kick it.
First class yo this is bad. Drinking orange juice out of a champaine glass. Is this what the people of Bel-Air living like? Hmm this might be allright. But wait I hear prissy, bourgeois and all that. Is this the type of place they should send this cool cat. I don't think, I'll see when I get there. I hope they're prepared for the prince of Bel-Air.
Well ah the plain landed and I came out. There was a dude that looked like a cop standing there with my name out. I aint trying to get arrested yet I just got here. I sprang with the quickness of lightning and dissapeared. I whistled for a cab and when it came near, the license plate said FRESH and it had dice in the mirror. If anything I can say this cab is rare. But I thought naw forget it yo homes to Bel-Air.
I pulled up to the house about 7 or 8. And I yelled to the cabby "Yo homes smell ya later". I looked at my kingdom I was finally there to sit on my throne as the Prince of Bel Air.
Your right. All this talk of distributed systems is making hacker news too nerdy. Lets go rate someone's startup and find a technical cofounder. Perhaps we might also watch a video of a prominent investor trying to promote his personal brand.
> My bank transfers to other banks take a couple of hours, but I don't live in the US. The money comes out of the account instantly though.
What happens between the time the money is debited from one account and it shows up in the other? Hint: it's not a transaction in the ACID sense of the term.
I would address the rest of what you say, but I'm afraid I cannot help you on your reading comprehension. I encourage you to read the article. All the words please.
What is this wonderful bank you use where transfers between accounts at a different bank happen instantaneously? Every time I've tried it the process takes 1-2 days and most likely has to go through an ACH.
As for credit and debit charges, my bank always has two transaction histories. Cleared transactions and pending transactions. Pending transactions are merely funds that have been reserved against your account and they may or may not clear after a period of time. Sounds like that fits pretty well with eventual consistency.
Sharding puts you in the same risk category as any other distributed database. Just ask the engineers and ops people at twitter, foursquare, and any number of other web companies that have dealt with sharded databases at scale. Also: sharding is eventually consistent, except you don't get any distributed counter primitives to help figure out which replica is telling the truth.
> Solving the problems of distributed systems is incredibly hard and not necessary if all you need is scalability and high availability.
Once one scales beyond a single node the system becomes distributed. Then by definition one must deal with distributed systems problems in order to achieve scale beyond the capabilities of a single node.
> When you decide to give up consistency, your application can no longer assume consistency ever. Giving up availability in case of network partition means few extra minutes of downtime a year.
Depends on the application. Giving up availability might mean cascading failures throughout your entire application. For instance if the datastore is unavailable for writes then any kind of queueing systems built around the DB (a common design pattern) run the risk of overflow during the downtime.
And I would make the argument that once an application scales beyond a single datacenter it cannot help but give up strict consistency under error conditions.
> I don't think he completely misunderstood distributed systems - I think he decided to completely side-step the entire field.
If he didn't misunderstand them then he is purposefully ignoring the hard problems. Which is worse?
