Beauty Is in the Eye of the Beholder
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
How would you like to view the presentation?
I think WS-BPEL and WS-CDL can and should live together, each one giving its best. As Hohpe said, WS-BPEL is intended for process execution, but focus just on one side of the conversation and in my opinion that difficults modeling large and loosely coupled systems. WS-CDL can help on modeling those system by giving a whole view of the conversations and allowing the automatic generation of the endpoints, even BPEL as described by Hohpe.
In my opinion WS-CDL is not yet enough mature and its xml syntax is not easily readable. For professional use we must get the help of tools like Pi4SOA.
Nice presentation!
Hi Floyd! The presentation system DOSE NOT works smoothly in my laptop with my ASL about 2M brandwidth. Is it possible to let us to watch InfoQ's presentation in off-portal style?
I agree completely. I would add three things specifically:
1. The pi4soa tool suite from Pi4Tech is now pretty robust and much easier to use. It is open source so try it out.
2. We have provided BPEL generation from WS-CDL for well over 1 year. Oddly enough few people seem to really want it, rather they generate Java directly or use UML generation.
3. BPEL is not the only end point executable language but it is an important one to have under your belt.
Gregor has done a great job in explaining what WS-CDL is for. I would say that it provides a standard-based language supported by formalism to ensure correctness and methodology to ensure that it fits in the grand scheme of things and that it is positioned as a means by which architects can describe their SOA in the large and realise the SOA through a number of executable language. All of this with formal type guarantees of correctness.
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.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.
Chris Richardson shows how he ported a relational database to three NoSQL data stores: Redis, Cassandra and MongoDB.
Jean Tabaka challenges the audience to reflect on what Agile practices they are employing, how they are using them, ending with the questions “Why have their organization chosen to go Agile?
3 comments
Watch Thread Reply