justinsb

31 ms·

241.
by justinsb 12y ago
Figuring out a good business model (or a way to survive without one) is indeed the challenge here! I'm not sure that AWS's margins will support this (and historically they haven't been great at supporting open-source anyway)
242.
by justinsb 12y ago
Thanks - great input (and the Gollum suggestion is a good starting point!) On multiple VCS: On the one hand, git is so dominant (for better or worse) that I don't know if the complexity is worth it. On the other, perhaps git is so dom
243.
by justinsb 12y ago
Probably based on JGit/Gerrit. It is much easier to build "cloud" git (i.e. reliable, redundant git) that way than it is to make your disk reliable. Github went the reliable-disk route with DRBD, AFAIK, which is why Github
244.
by justinsb 12y ago
Would you consider open-sourcing / documenting / blogging how you do that (or even providing some pointers to help get me started)? I'm playing with kubernetes and AWS, and it isn't clear what the best networking soluti
245.
by justinsb 12y ago
I've thought about building GitHub / BitBucket tools (issue management, pull requests etc) that work with data stored in git repositories, as opposed to one big tool that owns the git repository and manages the data in a locked-up
246.
by justinsb 12y ago
Interesting. Which SDN are you using?
247.
by justinsb 12y ago
I prefer the Unix model - many programs that work together. That might not be practical for networking (a natural plug-in, probably), but feels like it should be the way for orchestration. The Docker image registry and image management sho
248.
by justinsb 12y ago
This looks very interesting - it'll be really useful to have something like Docker that isn't so monolithic - it should be much more composable in new ways.
249.
by justinsb 12y ago
I'd recommend Google Gson; it works either with model classes, or with a generic JsonObject. Jackson is good, and more powerful in terms of model mapping, but I find it much more complicated to work with.
250.
by justinsb 12y ago
And Guava has Map<String,User> userIdMap = Maps.newHashMap() which uses Java's type inference rules, and works in 1.6 (I think even in 1.5)
251.
by justinsb 12y ago
I find Java much more pleasant without Spring; I much prefer Jetty+Jersey+Guava+Guice. It sounds like that's pretty similar to how you're using Scala.
252.
by justinsb 12y ago
Would love to have seen the Schlage locks included in the comparison - I think they're the front-runners. Perhaps I'm overlooking some terrible flaw?
253.
by justinsb 12y ago
Why not pass a dummy value to satisfy the spec?
254.
by justinsb 12y ago
They say it's Gerrit
255.
by justinsb 12y ago
I think your suggestion of using a pressure sensor is a great mechanism. Then, as you say, you need to be able to restore the keys (stored offsite) so you can do maintenance. This is an engineering problem: how secure do you want to be; h
256.
by justinsb 12y ago
I think distributed backup (of encrypted files) could be a great use case. But (like the CDN case mentioned elsewhere) this is also more demanding of bandwidth than CPU, which isn't really what you want here if your goal is to produce
257.
by justinsb 12y ago
Rather than cracking the problem of practical fully homomorphic encryption, I think they're probably cracked the problem of deleting the keys when the physical security of the cabinet is compromised.
258.
by justinsb 12y ago
What is the attack you're envisaging? Presumably they detect unauthorized case-intrusion and immediately delete the keys. This isn't foolproof, but it's probably good enough to stop anyone except the people that are going to
259.
by justinsb 12y ago
True (and I'm guilty of this). However... dinner times are a very culturally dependent thing. Dinner at 7:30PM might mean "food served at 7:30", or it might mean "I will be thinking about turning on the oven at 7:30&quo
260.
by justinsb 12y ago
I have no objection to your editing your comment to include a summary of how you put the go pieces together. Redemption is so much better than guilt ;-)
261.
by justinsb 12y ago
A suggestion: I think your statement would be much better received if you phrased it positively, rather than negatively. "Go is great; here's how I use it" is much more helpful than "Go is great; you're doing it wr
262.
by justinsb 12y ago
It's a trade-off: C vs A. If you can't lose data, Kafka's current configuration is unacceptable. There's an open issue, but it isn't fixed yet, and this means Kafka is (currently) unsuitable e.g. for use as a tran
263.
by justinsb 12y ago
Fair enough. Thank you for the very thorough answer - and for saving me the effort of putting together the patch!
264.
by justinsb 12y ago
I believe that active data is stored twice (once in the Postgres buffer pool, and once in the FS cache). This is not ideal, because it is not making optimal use of RAM. To minimize this effect, PG recommends a relatively small buffer pool
265.
by justinsb 12y ago
The simple answer is to use PostgreSQL, unless you have a good reason not to. There are definitely cases where PostgreSQL is not the optimal choice, but if you don't know why you're not a good match for Postgres, you're proba
266.
by justinsb 12y ago
Interesting - do you use LXC? Do you give root?
267.
by justinsb 12y ago
If it's static, then run it from S3. It'll be cheaper, and there are no servers to secure.
268.
by justinsb 12y ago
My understanding is that Raft has been proven formally correct in one of the author's PhD: https://ramcloud.stanford.edu/~ongaro/thesis.pdf (Chapter 8)
269.
by justinsb 12y ago
Wow - this looks like a great implementation. Who is cloud-software-foundation? Is this the software that powers WANdisco?
270.
by justinsb 12y ago
Interesting - thanks for the libpaxos link. Is it any good? I'm curious: what are these edge cases you're talking about? I've worked on a Raft implementation, and I don't remember any particular edge cases (though it&#

More ›