tupshin

11 ms·

91.
by tupshin 10y ago
Citation would be nice. This article talks about them having rebounded after near extinction: http://news.cornell.edu/stories/2015/08/some-honeybee-coloni...
92.
by tupshin 10y ago
Recipe: Create a global Cassandra cluster with regional datacenters. Use one keyspace per region Use per-keyspace replication to only replicate that region's data locally, and to one or more additional datacenters Have stateless app se
93.
by tupshin 10y ago
Having just acquired a pixel c tablet, I am increasingly looking forward to being able to iterate on my rust projects while being highly mobile. I don't see it as a primary development platform in the near future, but absolutely invalu
94.
by tupshin 11y ago
You are precisely right, and people with a devops mindset are most of the people that are building the cloud platforms that will render the role largely obsolete. A typical developer just wants to code against an api, and shouldn't hav
95.
by tupshin 11y ago
Definitely not
96.
by tupshin 12y ago
Thankfully it's on a long slow slide to oblivion. https://www.google.com/trends/explore#q=php&cmpt=q&tz=
97.
by tupshin 12y ago
This works only so long as the receiving side is able to retain all messages (or message ids if those are guaranteed to uniquely reference a given payload). It does not work for outages of unbounded (or otherwise impractical) data size or
98.
by tupshin 12y ago
If this were not happening in main(), then the following would be one way of handling the errors. fn foo() -> Result<(),Error> { // Create an event loop let mut event_loop = try!(EventLoop::<(), u64>
99.
by tupshin 12y ago
Trollish troll is trolling. Rust has a myriad of ways to handle errors, and unwrap is the most blunt of those instruments as it explicitly converts handleable errors into panics. Alternatives such as try!, unwrap_or(), and many others, shou
100.
by tupshin 12y ago
The global banking system has always been eventually consistent (overnight reconciliation, etc). Eventual consistency is essential whenever communication latency exceeds the acceptable time to receive acknowledgement that an operation was
101.
by tupshin 12y ago
Which is basically just using the weak anthropic principle as a convenient excuse for a lack of verifiability.
102.
by tupshin 12y ago
If only rust had (optional only, please) fall through on matches, then you could skip a whole line :D
103.
by tupshin 12y ago
There are numerous users of the paxos/lwt feature of Cassandra to selectively guarantee immediate/strong consistency for operations that need it (some at very large scale). But I'm not aware of anybody using this type of leas
104.
by tupshin 12y ago
Cassandra's CQL is an SQL variant/subset (albeit without joins, which don't scale out horizontally anyway) that is adapted to variable partitions with rows grouped into partitions. It addresses the problem of locality by embe
105.
by tupshin 12y ago
1) Buy a box with 1TB of RAM. Very doable these days, albeit a bit pricey still 2) Scale out. Spark can easily handle hundreds of nodes in a single cluster. Aggregate RAM across all of them can be used. 3) Cache intermediate data sets and&#
106.
by tupshin 12y ago
Spark doesn't depend on much of anything from the Hadoop ecosystem, including HDFS. It supports S3, as well as NFS or any other locally mountable filesystem right out of the box. The FAQ talks a bunch about Spark's weak ties to Ha
107.
by tupshin 12y ago
Datastax is committed to a highly distributed workforce, and is hiring like crazy. Almost all of our engineering positions are "anywhere". http://www.datastax.com/company/careers (Most of the engineering jobs
108.
by tupshin 12y ago
Projects like Apache Spark have demonstrated the power of a more complex DAG (Directed Acyclic Graph) approach that allows for more precise control over the data-processing flow, compared with the simpler execution model of M/R. All of
109.
by tupshin 14y ago
Looks interesting but very similar in concept to Mongrel2 built on top of zeromq.