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.
Posted by Stefan Tilkov on Oct 14, 2008
In a new presentation, recorded at QCon London 2008, Mark Little, Engineering Director and Technical Development Manager of the SOA Platform at Red Hat and InfoQ SOA Editor, explains the history of SOAP/WSDL/WS-*-based web services and RESTful HTTP and shows that both approaches have their roles to play in any good architect's toolkit. He elaborates on where possible convergence could, or should, occur within the industry.
Mark has been involved in leading roles in the distributed computing industry for a long time. He starts off by highlighting some of the major milestones of machine-to-machine communication history. He explains both Web services and REST, and shows both similarities and differences.
In his opinion, both REST and WS-* have benefits, and he shows what each could learn from the other. He recommends adopting WS-* within the firewall, and REST/HTTP between firewalls. This would require appropriate (and not yet available) bridging between the two.
He finally concludes that neither WS-* nor REST/HTTP are perfect, and a lot of the investment that has been made in large-scale distributed systems R&D can be re-used to improve them.
Watch Mark's presentation (60 minutes).
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.
1 comment
Watch Thread Reply