skip to main |
skip to sidebar
- A quite in-depth article on creating highly-scalable components in Java. Described are the ideas used to create the concurrent Java components in the Amino Library Project (a set of concurrent building blocks).
- Another SOA Design Pattern sample chapter from Thomas Erl' book "SOA Design Patterns": "Service Governance Patterns, comprising a number of 8 patters. Compatible Change and Version Identification deal with service versioning. Termination Notification addresses the final phase of a service, it’s retirement. Service Refactoring explains how to deal with changing service contracts. Service Decomposition, Proxy Capability, and Decomposed Capability include techniques needed to express coarse-grained services through multiple fine-grained ones. Distributed Capability helps increasing service scalability through processing deferral."
- To ESB or not to ESB? Including a nine points checklist. Note that the article is from the creator of Mule (a lightweight ESB). Check also the comments here.
- Interesting hack to reduce startup latency for mobile devices with HTML5: put the Javascript code in comments (thus /* */), such that is immediately downloaded but not evaluated. Then to load it when needed, parse the text, strip out the comment-tags & do an eval().
- Wondering whether you should add this new piece of functionality quick & dirty or take a bit longer, but cleaner? Taking the first one sets you up for a Technical Debt, as some more explained by Martin Fowler.
- "Test logic can be buried in this unrelated code, which has nothing to do with test logic itself, making test code hard to read and maintain. In this article, the layered architecture of test automation is presented to solve this problem. In this layered architecture, the test automation code is divided into three layers: (1) test cases, focusing on the test logic of the application, (2) the domain layer, modeling the system under test in domain terms, encapsulating http requests, browser control, result parsing logic and providing an interface for the test cases layer, (3) the system under test, which layer 2 will operate directly on."
- A good explanation of the Canonical Message Model in the context of an ESB, and why you'd need one within an SOA. Great description of different approaches for implementing a CMM in an ESB and their pros and cons.
A short introduction to CMM modelling (data model and message model) is described here.
- From The Open Group two free PDF books: "The Open Group SOA Integration Maturity Model (OSIMM) provides consultants and IT practitioners with a means to assess an organization’s Service Oriented Architecture (SOA) maturity level."
"This document describes a framework that provides context and definitions to enable organizations to understand and deploy SOA Governance."
- The JavaServer Faces 2.0 specification (included in JEE6) got finalised last May. Here's a reference to it and a set of references related to this specification.
- Check the elaborate 95 slides comparison of Javascript libraries at the bottom of this post. It's a presentation by John Resig, Mr JQuery. The presentation is very objective. Compared are: Prototype, jQuery, Yahoo UI, Dojo and Mootools. Another short comparison of 14 RIA/Ajax/Javascript frameworks shows jQuery as the winner, as seen by the User eXperience reviewer. Great news for jQuery this week anyway: both Nokia and Microsoft are adopting it as part of their official application development platform.
- Can't get enough of these RIA frameworks comparisons? Here's another one, which is a short comparison/intro of three Rich Internet Application frameworks: Adobe AIR, Google Gears and Silverlight. See also my (bit older) post here, which also includes JavaFX.
- Summary of an article by Martin Fowler on how Agile can be used in building SOA implementations. The answer: yes you can quickly get value out of it. The biggest proof is the internet: loosely coupled and many unexpected changes.
- Quick-start JSF book free for download. Only 65 pages. Beginners level, step-by-step. With some mixed "infomercials" about the soon to be open source Eclipse IDE extension Exadel Studio Pro, but not in an annoying way.
- Key API design points from Joshua Bloch, Chief Java Architect at Google
- An explanation why a canonical message model (CMM) is a "good thing" in SOA and ESB.
- How to manage and lead geeks in a team. For technical and non-technical teamleaders.
- What should you use in your SOA project: a BPEL process or an ESB?
- Part 4 in a series on SOA Design: why and how you should use canonical models in SOA. "The canonical data model defines the structure of an organization's information."
- SpringSource just released their SpringSource Tool Suite. Notice that it is different from Spring IDE. For example it helps you find common pitfalls and best Spring best-practices violations.
- Yahoo! has released new performance best practices for building webpages.
- Ways how you can run Firefox 3 beta 4 and Internet Explorer 8 while still being able to easily switch back to FF2 and IE 7.
- The new OpenHub spec version 1.1 from the OpenAjax Alliance now also includes IBM's contributed Secure Mashup framework (SMash). SMash provides for secure handling of third-party mashup components. OpenHub can be used by developers to "integrate multiple toolkits within the same Web page while toolkit developers can use it to allow toolkits to talk to other toolkits."
- Always interesting, a look inside "the kitchen of": the people from 37signals.com have provided some inside-info on the architecture of some of their sites: Backpack en Basecamp. For
example they are using RoR, MySQL, S3 and memcached.
- Post (related to the ESB entry in my post last week) regarding the rise of Tomcat as "application" server, in relation with the rise of Spring. Comparing Tomcat with WebLogic and WebSphere is more like comparing Oracle with MySQL. Tomcat is still not at the same level in certain areas as WebLogic and WebSphere, though it is making progress in these areas: clustering and high availability.
- There's a new revised version of the free e-book from Microsoft on the most important security engineering activities that you should have in your development process: The Developer Highway Code. Written by Paul Maher (Microsoft UK) and Alex Mackman (CM Group Ltd).
- Great news, version 2.0 of SoapIU has just been released. Improvements include webservice WSDL coverage and WS-Security completely refactored.
- Nice set of 10 lessons learned from designing and building a high transaction database (Microsoft SQL Server). The system was required to support 35K tps.
- Reasonable comparison of 3 open source applicationservers: JBoss 4.2, Geronimo 2 and Tomcat 6. Geronimo comes out as most complete. Tomcat is a bit odd in this comparison, it is more a servlet/web-container than a full applicationserver. Glassfish for example would have fitted better here. Here's some The ServerSide feedback on it.
- In this article Paul Fremantle discusses the fundamentals of the Enterprise Service Bus concept. His point is that the model of ESB sometimes might be converting into an anti-SOA pattern: the conversion of the formats happens in the ESB instead of happening at the service providers (the endpoints). Thus you would need a central ESB team that needs to deal with each application, its format and protocol the ESB needs to interface with. Note that the author is owner of the WSO2 ESB, his company and also works on Apache Synapse. As he claims these tools are designed from the ground up to match the original idea of SOA: the owners of the services take responsibility to define a clean and simple interface.
Del.icio.us
DZone
Reddit
Digg
