I'm also constantly surprised at how unpopular docker swarm is given that everyone already uses docker itself. Why do you think swarm is going away though? I love the idea of just using my docker compose file as my deployment config.
My company tried using Swarm 2-3 years ago and ran into the problem that it didn't actually work. Containers would just go missing from the network. Consequently we switched to Kubernetes. I imagine it does work now but it seems to be too late.
I've recently started using Kompose to autogenerate Helm charts from docker compose files and I've found that pretty satisfactory.
The second version of Swarm (the first version built into the stack) was really unstable. It got a bad reputation very quickly in one area that it could not afford to.
That said, I was at a conference, talking with a CIO of a K8s related company, back during the initial days of that startup ecosystem. I was told off the record that Google and Redhat were offering an "marketing budget" for companies that would come on board the Kubernetes ecosystem. The person rightly stated that K8s was going to roll everyone else because of it.
Can't validate that - it's hearsay, but I definitely think that it was a big factor
I'm not familiar with Docker Swarm, but the Kubernetes API is the major strong point for me (not saying that it's perfect): it has the right abstractions (CronJob, StatefulSet, ..) and is extensible (Custom Resource Definitions). There are many ways to run containerized workloads (ECS, Mesos, Docker Swarm, ..), but the de-facto agreement on the Kubernetes API is a game changer: now we can start building things on top of it :-)
"Going away" might be an overstatement, but I don't see much evidence of it being in use. When I search for help on topics, I don't see much beyond the primary docs. There doesn't seem to be much of a community for swarm out there, and now even the desktop versions of docker come with k8s.
Many game developers use Discord to organize beta tests, gauge feedback, share announcements and manage and measure their community following in general. The fans feel good for being included in the process and the devs feel good knowing roughly how many people they can expect to buy their games at launch time. I hope they figure out a good way to monetize this, since I see it as their killer app.
I've noticed this annecdotally when trying to buy a home on separate occasions in the New York and LA metro areas. I'm not sure it's foreign capital, but the majority of winning bids were all cash offers above the asking price.
I'd love to see a retrospective analysis on Vancouver's protective measures to see if they did actually help, or if buyers found loopholes, or it wasn't Chinese buyers to begin with.
I wish I could find the link now, but someone did a study on Vancouver and found that the tax had no effect on housing prices. The foreign buyers simply added it as another cost of parking their money outside of their country (usually China) and the math still worked in their favor.
It brought in some extra money to Vancouver though.
Of course it’s impossible to say with complete certainty, but... Vancouver’s housing market has stalled since the foreign buyer tax and vacancy taxes started to bite. Inventories are high and stubbornly stuck there rather than falling as they do toward the end of the year. Prices on high end homes are down a great deal - 20-30% for homes priced higher than $3M.
I would say that at this early stage it looks like the new taxes are working precisely as intended.
I think the confounding factor is that the tax would move the market whether or not foreign buyers are an issue. The price drops are also mostly at the top end of the market, which benefits wealthy buyers.
So just to clarify, the client code still connects directly to the actual redis instance, it doesn't connect to the failover daemon as a proxy? It would be useful to describe the connection algorithm in the README.
Also, the split of the reads and writes, that's done via opening connections to both the master and slave?
That's right. The client still maintains direct connections with the actual master/slaves. It's only when it fails to connect with one of them that it goes to the failover daemon to ask for the current set of available nodes. The split of the reads/writes is handled by the client, as it knows where to dispatch commands (to master for writes, and to one of the slaves for reads). I'll make this clearer in the README.
It's funny, when I went to visit a friend at Etsy after work hours, we were chatting in the kitchen and their CEO, Rob Kalin was washing dishes. My friend said to him, "That's awesome that you're the CEO and you're washing the dishes, Rob." And he replied, "Oh, it's better than when I was cleaning the bathrooms."
You should be comfortable hearing a sentence such as that. Horowitz is clearly generalizing, but a great company will always make a return on investment. Obviously in this particular case Groupon is going to give investors a smaller return now than it would have 6 months ago, but it's still a winning strategy. Great companies keep growing - which is more than a good reason to invest.
