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 Charles Humble on Oct 04, 2007
Nexaweb hashave announced the latest release of their Enterprise Web 2.0 Suite, an application development and deployment platform for building Rich Client, Composite and Enterprise Mashup applications in JEE environments. Nexaweb is among a growing list of companies such as BEA Systems, IBM, and JackBe emphasing the use of mashup technology in the enterpise.
The Nexaweb Enterprise Web 2.0 Suite consists of four major components:
The client-side approach to processing the XML taken by Nexaweb's Universal Client Framework is unique in the context of Rich Internet Applications. Products like OpenLaszlo and Adobe's Flex work by compiling XML to the SWF binary format on the server which is then rendered by Adobe's Flash Player on the client. JSF and jMaki also do their XML processing server-side sending HTML and JavaScript from server to browser. By processing the mark-up and rendering client-side Nexaweb argue that their product allows developers greater flexibility in the client-side technologies they use to create their XML. For example, the UI could be built using XSLT, JSP or any JEE web framework capable of outputting XML.
The main emphasis on this release has been on Nexaweb Studio with a number of new features and enhancements including:
Nexaweb Enterprise Web 2.0 Suite starts at $17,900 (USD) covering the platfrom and support for three developers. Nexaweb state that the product has been used by 5,000 companies.
Mobile and the New Two-Tiered Web Architecture
18 agile and lean practices for effective software development governance
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
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.
No comments
Watch Thread Reply