Michael Foord discusses IronPython, the DLR, dynamic languages on .Net, static vs. dynamic typing, Visual Studio integration, Resolver One, Intellipad, Crack.net, embedding IronPython, the ScriptEngine, error handling, dynamic operations, functions as delegates, and the C# 4.0 dynamic keyword.
Phillip Ghadir presents a financial application that was initially built using SOAP, WSDL, WS-*, and was later migrated to use REST, Atom, and AtomPub, explaining the decisions made, the pitfalls and the lessons learned along the way.
Peter Pilgrim makes an introduction to the Java FX platform, presenting its scripting language, the standard deployment method of applications, client integration with the server and what’s planned for its future.
Many organizations will tell you that they are "doing" continuous integration. A boat anchor of a PC in the corner running an old version of CruiseControl might tick a few boxes, but is it really effective? As we get better at CI, we should see our feedback loop extend out past development. But what strategies do we have for doing this and keeping the feedback loop tight for the developers?
Jimmy Nilsson makes a case for DDD explaining that while DDD uses some similar elements as DB-driven design does, for example, entities and repositories, the difference is in how they are used, the way the design is approached and elaborated, building on collaboration and feedback, incorporating deep domain knowledge, having as end result: reduced complexity, testability, and maintainability.
This session takes an inside look at successfully delivering from concept to cash, showing the technical aspects of what's required to iteratively build a robust product that always performs, and the skill and discipline needed to deliver high-quality software to production every week. We know this because we wrote one of the busiest entertainment Web sites in the UK from scratch.
Rich Hickey’ presentation is organized around a number of programming concepts: identity, state and values. He explains how to represent composite objects as values and how to deal with change and state, as it is implemented in Clojure.
Paul Fremantle presents three case studies of organizations, small and large, which decided to implement SOA. He details on design, architecture, technologies used, lessons learned, and potential disadvantages of the solutions chosen.
Brian Oliver explains what the Reconciliation Process is, why the current approach to reconciliation based on client-server is no longer suitable and how data grids and event based reconciliation might help.
RESTful architectures are the subject of this presentation, specifically the way they are particularly attractive in solving many financial services integration problems. Kirk will present the advantages of a RESTful architecture to develop integrated systems in the financial services arena, in particular leveraging infrastructure, skills, and systems already in place at these firms.
This presentation addresses a key business-technology alignment principal: understanding priorities in terms of business value. Traditional ROI type measurements of business value are expensive, inflexible and boring. A Perception Index (and a necessary "square peg adapter") offers is a lean, appropriate and fun alternative, for a fast changing business.
Michael Nygard encourages us to have a failure oriented mindset in order to succeed. He presents many anti-pattern examples that lead to systems instability and ultimately lead to failure. He also presents the corresponding stability patterns that should be used instead.