Collaboration: At the Extremities of Extreme
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
How would you like to view the presentation?
Getting Started with Stratos - an Open Source Cloud Platform
A practical guide to choosing the right agile tools
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
18 agile and lean practices for effective software development governance
I'm sorry to correct Billy here, but he misses a point in just 2 minutes of his presentation. Redis does not use thrift and never has. Also, it supports an append-only log, so no data is lost (this was probably added after the presentation).
Oh, forgot to mention that Redis DOES support replication: code.google.com/p/redis/wiki/ReplicationHowto
The source code for the prototype implementation is online now at github. www.github.com/bnewport
Hi,
I think this kind of approach using key-value without transaction and locking only works for twitter-liked apps, where users do not accessing and updating one information in the same time.
Even in twitter-liked apps, user do not change data from other user.
How can this approach can be applied to business app like CRM, where 100-1000 user access and update information in the same time?
Regards,
Steve
This approach implements atomic operations on the supported primitives like numbers, lists or sets but without transactions then you can't atomically work with multiple entries. If you want that kind of control then just using WebSphere eXtreme Scale directly with our normal APIs gives you that kind of model. Full atomic transactions, locking, serialization of changes and so on.
I actually found the proposal to use closures to run code on different nodes pretty neat. Looking forward to the prototype!
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
6 comments
Watch Thread Reply