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?
Five Key Practices to Agile ALM
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
Agile Maturity Model Applied to Building and Releasing Software
Hi Craig,
I was able to understand your perspective on large scale software development model. One point which I am not convinced that if we do not set architectural constrains before starting development there are chances where each team can go in different direction to implement same common component. Example could be exception handling guideline or may be some common component. I have given two features to two development team and both the team may come up with different approach and different component for exception handling. This will not solve purpose of reuse of same component.
Thanks,
Ajay
Well, found this talk very impressive and I feel impressed by the framework 1 and 2 and how this scales to such great number of teams around the world. I imagine how great it would be to work in such environment.
Ajay, I understand your point, but I think this is a high level view and in daily practise there arise so much problems and complicated situations, which are not shown here. Your architectural question is one of them, but there are a couple of more, like adressing the "right" feature team, and let them come/work together to solve the problems.
I'll believe architectural issues are demistified while designing sessions if the teams are addressed and dive into the problem domain. The architecture documentation past release is great :-)
I do fully agree with the crossfunctional teams, the role of architecture (and architects, no powerpoint architects) in agile development.
It sounds to me more KANBAN than SCRUM though some SCRUM ceremonies are manifested.
Great job, Craig. I ordered the books immediately to dive more into the details and get more tips.
Hi Craig,
most interesting is that feature teams scale and component orientated teams did not. You are assuming bigger components that only one teams owns, right?
Are multiple fine grained components in some requirements area that "owns" a team similiar to your what you have called "feature teams"?
key takeway: component teams lead to waterfall.
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.
4 comments
Watch Thread Reply