Thanks & Regards,<br />Chandramouli Ram
Thanks & Regards,<br />Chandramouli Ram
www.classic-and-class.com - www.evalulearn.com
Interfaces are the glue of OO.
Thanks & Regards,<br />Chandramouli Ram
Originally posted by Thomas Taeger:
: EJBs ("the heart of J2EE")!
Originally posted by Thomas Taeger:
S: Project estimation: Provide project estimations to project managers and also appraise of them of any technology related project risks.
A: No, not at all. What do we have a Project Manager for? Time estimations must be actively asked. How could the architect concentrate on his work anymore?
Originally posted by Thomas Taeger:
S: Configuration management: This includes deciding a source control tool, setting it up, creating branches for developer groups, responsible for merges and releases.
A: No, not at all. What do we have a Project Manager for?
Originally posted by Ram Chandramouli:
2.I am not making an attempt to define the duties of an architect, as your responses seem to reflect - but just what architects did in the projects I worked on.
www.classic-and-class.com - www.evalulearn.com
Interfaces are the glue of OO.
S: Coding: In many cases, architects are the ones to write the first end to end code �all the way from presentation to persistence layer.
A: Duty of the developer team led by the architect.
Originally posted by Peer Reynders:
The estimates need to come from the team(s) � if they do not, your project is in trouble even before it starts.
www.classic-and-class.com - www.evalulearn.com
Interfaces are the glue of OO.
Originally posted by Thomas Taeger:
Then nearly 100% of projects were in trouble, if not the project manager goes around and actively asks a) each single developer and b) maybe additional the team(s) as groups what the state of their work packages is.
Originally posted by Peer Reynders:
... stop buying into Sun's propaganda! A significant share of J2EE installations don�t even use EJBs that much � the occasional stateless session bean maybe.
Originally posted by Peer Reynders:
If you are lucky, somebody may notice that you are behind all the good decisions and ultimately give you the job � just don't forget where your roots are.
www.classic-and-class.com - www.evalulearn.com
Interfaces are the glue of OO.
It is true, during the last weeks all day long I received requests for any mix of architect and what else jobs, and much too often I had to defend or convince that an architect is an architect and a craftsman is a craftsman, and so on.
Thanks & Regards,<br />Chandramouli Ram
Originally posted by Thomas Taeger:
ultimative Web Services
Originally posted by Thomas Taeger:
But when I came across EJBs I understood one special architectural thing: Whilest the Client/Server architecture was N:1:N, J2EE introduced N:N:N. i.e. by giving clustering an architectural concept
Originally posted by Thomas Taeger:
Because I actually tend to design for local access to entity beans the switch to EJB-3 will be moderate in the Data Access Layer.
Originally posted by Thomas Taeger:
That is too modest for my situation. As a freelancer I must be up and running.
First Law of Distributed Object Design: Don't distribute your objects!
Originally posted by Ram Chandramouli:
When I said estimation, I actually meant at a gross level. Who does generally estimate a project when there is a only a proposal?
Thanks & Regards,<br />Chandramouli Ram
Originally posted by Peer Reynders:
I'm not sure exactly what you are getting at.
Originally posted by Peer Reynders:
Also I'm pretty sure that clustering is not mandated by either the EJB or Servlet specification; i.e. clustering is a value added option by application server vendor, not an inherent feature of J2EE.
Originally posted by Peer Reynders:
So clustering is implemented in a vendor proprietary manner ...
Originally posted by Peer Reynders:
IT architecture has always "recognized" clustering as "the" horizontal scaling and/or failover option � without being tied to any particular brand of technology, framework, or architectural design.
www.classic-and-class.com - www.evalulearn.com
Interfaces are the glue of OO.
Originally posted by Ram Chandramouli:
My point here is that whether or not architects do a certain thing, do they need to be aware of these aspects to be an accomplished architect or not.
www.classic-and-class.com - www.evalulearn.com
Interfaces are the glue of OO.
Originally posted by Peer Reynders:
As a freelancer you cannot afford to have tunnel-vision of any kind even the EJB kind.
www.classic-and-class.com - www.evalulearn.com
Interfaces are the glue of OO.
Originally posted by John Waugh:
How an organisation decide that this application needs an architect or not?
www.classic-and-class.com - www.evalulearn.com
Interfaces are the glue of OO.
SCJA, SCJP, SCBCD & SCEA (Part I)
Open Group Certified Distinguished IT Architect. Open Group Certified Master IT Architect. Sun Certified Architect (SCEA).
Thanks & Regards,<br />Chandramouli Ram
Originally posted by Vagner Freitas:
I've read an interesting article about the Characteristics of a software architect.
Sreenivasa Majji
Originally posted by Thomas Taeger:
Even though clustering is an optional feature of J2EE, those vendors who realize it in a J2EE compliant way are [ideally] replaceable by each other. That is what I mean with "gave clustering an architectural concept" - instead totally vendor specific or even hardware solutions. I think the presence of the huge J2EE market justifies my evaluation.
Originally posted by Thomas Taeger:
the other extreme like "you must know every architecture" is not needed.
EJBs are a good solution to problems of distributed applications and complex transaction management. However, many applications don't encounter these problems. EJB adds unnecessary complexity in such applications. An EJB solution can be likened to a truck and a web application to a car. When we need to perform certain tasks, such as moving large objects, a truck will be far more effective than a car, but when a truck and a car can do the same job, the car will be faster, cheaper to run, more maneuverable and more fun to operate.
Originally posted by Thomas Taeger:
Because I actually tend to design for local access to entity beans the switch to EJB-3 will be moderate in the Data Access Tier.
The availability of declarative transaction management via CMT is the most compelling reason for using EJB
Thanks & Regards,<br />Chandramouli Ram
It would give a normal human mental abilities to rival mine. To think it is just a tiny ad:
Smokeless wood heat with a rocket mass heater
https://woodheat.net
|