(Found in a blog, "Versioning is as inevitable as security.") SOA development
practice isn't much different from other software development practices
except for design and maintenance. Multiple self-containing and aggregated
services that interact with others have their own lifecycle and evolution.
The loosely coupling model of SOA services significantly simplifies design
but creates additional difficulties in maintenance, especially in the
interoperability of different service versions.
To better understand the requirements of SOA service versioning, let me ask
several questions and see if we can answer them easily:
Is SOA a structure of interfaces such as Web Services or it is a structure of
services with interfaces? Who is the master in SOA - the client or service
(p... (more)
From the first days of Rich Internet Application (RIA) technology, many
enthusiasts found an analogy between RIA and service-oriented architecture
(SOA). Some of them talked about the benefits of a would-be-wonderful use of
SOA in RIA; others saw RIA as a SOA face. Nonetheless, there are experts who
see a discrepancy between RIA and SOA concepts.
The major disagreement between RIA and SO... (more)
Application architects have heard about the increased importance of security,
but in many cases they really don't know how to approach this issue. In this
article, I'll share my experience and define a few basic steps and
checkpoints for building application architecture with security in mind.
This year, architects have started to face several domestic (SOX and HIPPA)
and even internation... (more)
This article describes a workaround design that allows a Portal to survive if
its resource starts hanging request threads.
Business Task
How frequently does your Portal experience user requests hanging in the
resource? Not frequently, I hope. However, if this happens and the resource
continues hanging user requests, the Portal is exposed to a fatal risk of
spending all of the configured c... (more)
The requirements for different user-facing applications frequently say
something like: "User has to see/read/be shown only
funds/records/itineraries/policies he or she is entitled to." Permissions in
these cases usually depend on multiple factors related to the user profile
(job role, locale, etc.), to the protected data (data origin, storage,
approval status, etc.), or to both. This rep... (more)
Michael Poulin works as an enterprise-level solution architect in the financial industry in the UK. He is a Sun Certified Architect for Java Technology, certified TOGAF Practitioner, and Licensed ZapThink SOA Architect. Michael specializes in distributed computing, SOA, and application security.
Keith Bergelt
Ricardo Aravena
Gaurav Mantri
Aditya Banerjee
John Karamitsos
Kaj van de Loo
Bob Little
Alois Reitbauer
Chris Schin
Richard Gordon
Anil Parambath
