: Building software components and then integrating them with applications built by others has always been one of the most difficult challenges for any development team. In today's Web environment, developers are now being asked to build components that can be dynamically plugged into any application anywhere on the Web. In a conversation with Queuecast host Mike Vizard, David Johnson, CTO of IPCommerce, a company that specializes in distributed payment systems, explains how his company is rising to that very challenge.' />
September/October issue of acmqueue


The September/October issue of acmqueue is out now


Interviews

Component Technologies

Listen to an MP3 of this article  

Item not available


Tweet



Related:

Satnam Singh - Cluster-level Logging of Containers with Containers
Logging Challenges of Container-Based Cloud Deployments


Peter Kriens - How OSGi Changed My Life
In the early 1980s I discovered OOP (object-oriented programming) and fell in love with it, head over heels. As usual, this kind of love meant convincing management to invest in this new technology, and most important of all, send me to cool conferences. So I pitched the technology to my manager. I sketched him the rosy future, how one day we would create applications from ready-made classes. We would get those classes from a repository, put them together, and voila, a new application would be born.


Len Takeuchi - ASPs
The promise of software as a service is becoming a reality with many ASPs (application service providers). Organizations using ASPs and third-party vendors that provide value-added products to ASPs need to integrate with them. ASPs enable this integration by providing Web service-based APIs. There are significant differences between integrating with ASPs over the Internet and integrating with a local application. When integrating with ASPs, users have to consider a number of issues, including latency, unavailability, upgrades, performance, load limiting, and lack of transaction support.


Chris Richardson - Untangling Enterprise Java
Separation of concerns is one of the oldest concepts in computer science. The term was coined by Dijkstra in 1974.1 It is important because it simplifies software, making it easier to develop and maintain. Separation of concerns is commonly achieved by decomposing an application into components. There are, however, crosscutting concerns, which span (or cut across) multiple components. These kinds of concerns cannot be handled by traditional forms of modularization and can make the application more complex and difficult to maintain.



Comments

(newest first)

Leave this field empty

Post a Comment:







© 2017 ACM, Inc. All Rights Reserved.