Eventually Consistent HTTP with Statebox and Riak
Bob Ippolito explains how to solve concurrent update conflicts with Statebox, an open source library for automatic conflict resolution, running on top of Riak.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
How would you like to view the presentation?
Agile Development: A Manager's Roadmap for Success
Mobile and the New Two-Tiered Web Architecture
A Guide to Branching and Merging Patterns
In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!
it's way better !
+1
Especially when one has an iPad, and there is no flash support!
I watched this today 11/23/10. It says it all.
I was going to going to add Ninject IOC to my project code I am working on today , I had already coded and tested the dependency injection, but I don’t think that it fits the Simplicate Pattern and totally violates the Simplicate Principle (which states that IOC (like many things you mention in your video) makes the code totally unreadable and un-maintainable)
I asked the smiling PEZ pumpkin on my desk whether I should add Ninject or not and the pumpkin says NO.
Or two have an iPad.
Listen to the pumpkin. The pumpkin is wise beyond its years.
I agree with your point wrt complexity and frameworks. Neat presentation approach too. More specifically though, do you consider unit testing to be important (in some cases)? If so, how do you do it without some kind of dependency injection (even if it's overridable/virtual object methods)?
Loved your talk. Had lot of laughs too :)
About DI, I found its simplicating ,rather than complicating. Agreed that its one more jar(with few more .jar as dependencies)
But it hardly took 3 to 4 hours to understand and start using it. And Not using load of features it comes with. (FYI, By the time I started programming, DI was there)
Whats your views on Groovy? Simplicating or Complicating?
Is it possible for you to share any of your Simplicated project structure or article?
Regards,
Nachiket
This was recommended (effusively) by Russ Miles at his Skills Matter session last week (Getting Architecturally Agile with Event Driven Architectures).
He was right. Great talk. Thanks Dan. I won't even try to praise it - just watch it. I've forwarded to our corporate socialcast site, which takes some b*lls. Now I just wish I had the b*lls to stick to Keep It Simple!
Duck talking trumps duck typing. I'm going to get myself a yellow duck.
<humor>This sounds like Shaving The Yak pattern mentioned in the talk by Dan - the problem is not the talk text, the problem is the iPad :)</humor>
Bob Ippolito explains how to solve concurrent update conflicts with Statebox, an open source library for automatic conflict resolution, running on top of Riak.
Erik Onnen attempts to demonstrate that Java is still the best programming language for the JVM if simplified idioms are used along with proper tooling.
Approaches to integrating data are changing with emergence of cloud computing.
Michele Ide-Smith presents the lessons learned in the process of introducing UX principles and techniques into a large organization through a series of small steps.
Dave Farley and Martin Thompson discuss solutions for doing low-latency high throughput transactions based on the Disruptor concurrency pattern.
Rajneesh Namta shares his thoughts, experiences, and some of the critical lessons learned while implementing software test automation on a recent Agile project.
Dale Schumacher presents several patterns of actor interaction that can be used in collaborative programs written in any language.
Rúnar Bjarnason discusses Scalaz, a Scala library of pure data structures, type classes, highly generalized functions, and concurrency abstractions to perform functional programming in Scala.
10 comments
Watch Thread Reply