• English
  • Nederlands
HOME
SEARCH
CONTACT
NEWSLETTER
 
 
 
CONTENT
About us
Call for contribution
Contributions
The CIO talks
Proceedings
Blogs
Master thesis
Forum
Wiki
Events calendar
Links
Login/Register
advertisements
Zoek je een baan?
Zoek je hulp?
Zoek je een opleiding?
Zoek je een boek?
Zoek je een tool?












 
 
BLOGS
Report a comment

Thank you for taking the time to report the following comment to the administrator of this site.
Please complete this short form and click the submit button to process your report.

Name:
 
E-mail
 
Reason for reporting comment
 
 
 

Comment in question
Written by Lydia Duijvestijn on 13-09-2008 13:41
 
 
Hi Jack 
I agree with you that it is very hard, if not impossible, to convince people with a completely different agenda of the necessity of sound architectural decisions. But to my opinion, that should not be necessary! Every program or project should have some form of Design Authority that needs to give its blessing to the architecture under construction. Without the signature of the DA the program or project will not continue. This way of working gives the lead ITA the authority they have to have and prevents lengthy discussions. You're not a sales, after all, are you? 
On the other hand I'd like to warn you that an ESB is not the solution to all your problems in all cases. I have recently been involved in a project the goal of which was to replace a fully optimised 70% batch oriented mainframe application by a distributed SOA system, complete with ESB and process server, multiple loadbalancers, various pieces of software. In this case the advise of the lead architect should have been "DON't DO IT!", that is not for the whole application - only replace those pieces that lend themselves to interactive service oriented processing! This would have saved all parties many nightmares!

 

Via Nova Architectura is not responsible for the content of blogs, but authors and readers are asked to adhere the following guidelines. Authors are strongly encouraged to check facts, cite sources, present balanced views, acknowledge and correct errors. Respect copyright, fair use and financial disclosure laws. Please do not disparage organizations, or individuals. Being critical of someone's practice is acceptable, when it is done in a professional manner. Prevent usage of marketing statements. Comments should be relevant to the specific post they are attached to. Spam, flaming, personal attacks, and off-topic comments are not permitted. Readers are requested to notify This e-mail address is being protected from spam bots, you need JavaScript enabled to view it of any violations. The editor holds the right to remove any statements that, in the editors opinion, infringe the above guideline(s). The author receives a notification of this action.
feed image
ISSN: 1877-2994