Thursday, June 25, 2009

Lifecycle Governance of your core assets

The SOA Gateway enables your core software assets, including data and business logic, to be exposed as standards based services that can be used from multiple client technologies. Once a service has been deployed and is in use from one or more systems, there are reasons why it may change:
  1. In order to improve the functionality available to the users.
  2. In order to improve the business process with which it was associated
  3. Users asked for something and didn't like what they got
  4. ...and so on
The problem with this is when a service is deployed, how does one control change to this service ? Many organizations implement multiple versions of a similar service when a well designed single service will do. The SOA Gateway is being modified to provide the facility to ensure that the lifecycle of a service can be controlled such that a single service and its clients may be enchanced in a controlled fashion as described here.

This is still a work in progress so we're always interested in ideas or feedback to the direction we plan to take.

Best regards,

John

Thursday, June 18, 2009

Want sub second response times with Rich Gui Interfaces ?

Those of us who have been around for more than a decade can remember the concept of sub second response times. A single 'second' was considered the maximum time between when a user hit 'enter' on their dump terminal and when they got a response from the system. This wasn't just a rule of thumb or some geeky idea of how a system works, there are many reports available which illustrate quite clearly that as response time gets longer, there is an increased reduction in transaction rates and essentially throughput falls. In other words, less work is done. Some might consider that this is just because of the longer response times but it has been illustrated that lapses in concentration add additional delays to the completion of a business process.

Since the advent of the PC and more so the Internet, we are being treated to vastly superior GUI displays which make like much simpler in terms of the usage and understanding of applications. However, this has been mirrored by a commensurate reduction in response times as GUI screens build and one must wait until this build process completes. This is probably quite acceptable for occasional users or those in Internet land prepared to wait. However, it leads to loss of productivity within organizations where employees are expected to plough through as much work as possible which is severely impacted by slow GUI response times.

The Enterprise Application Infrastructure described here provides an architecture that can deliver significant benefits and sub second response times while still delivering a rich user front end GUI. This is achieved through the use of the SOA Gateway and CaptainCasa tool sets which in turn achieve the result through a simple adherence to and usage of industry standards.

Check it out if you would like to reduce your user response times !

Best regards,

John

Wednesday, June 3, 2009

SOA Gateway now 'Ready for IBM DB2 data server software'

The SOA Gateway has now just achieved the 'Ready for IBM DB2 data server software' award from IBM. This means that the SOA Gateway has now proven itself while running with IBM's DB2 Database which is guaranteed by IBM themselves. More information on this award can be found here.