Hi folks,
Many of you know me from the early JUG days... Back to 1995 if I recall
correctly. My, how Java has changed. It seems a little more complicated
these days. :)
Anyway, it's been a some time (like, four years) since I've done direct
development, and I'm beginning a significant project for a customer. I am
looking to identify the best-in-class technology stack, with an emphasis on
open-source, to get the job done. I would like to avoid significant vendor
lock-in, and of course would like to keep things inexpensive. Most
importantly, I stepped away from development as J2EE was maturing, so I need
to get up to speed on J2EE quickly.
(PS - if you like startups and know your stuff, maybe there are some further
discussions to be had).
I will be building a highly-scalable transaction system, with some web-based
user interface features, but primarily for machine-to-machine interaction.
It will need to be fast, reliable, flexible (in terms of interfacing to
myriad legacy systems), and secure.
With those vague guidelines, here are my preconceived notions of what I'll
begin to assemble. I would appreciate suggestions, comments, corrections,
etc.
Development
* Build Management: Ant (I will miss make)
* SCCS: Probably perforce since I have experience with it..
* Coding: Slickedit (I will always be a vi bigot, eclipse fans flame away)
* I am still looking for a good pre/post-analysis lint-like tool
to do things like complexity analysis, etc. Suggestions?
Tech stack
* Hosting: Have used Inflow and IBM in past. Current favorites? We'll
be providing our own hardware, just need good managed cages.
* Boxes: Dell rackmount..? Any IBMers out there want to give me
a reason to look elsewhere?
* OS: RedHat Linux..? Or do folks prefer BSD?
* DB: MySQL... Who will vouch? I used Oracle previously... But it's
expensive and the tentacles get deep.
* J2EE: (Warning, I have not delved into J2EE personally, so what
follows are sure to be dumb questions... But do have substantial
servlet/JSP experience and I know the concepts, having had to
invent them in-house prior to J2EE out of necessity)
* The basics: I have prototyped some systems using servlets
based on Apache/Tomcat/Jakarta.
* App Server: JBoss? Does this subsume what's provided
by Apache/Tomcat/Jakarta? How does it compare to
BEA or WebSphere? Pros/cons?
* UI: I've heard nice things about Tapestry. What's the
best (most flexible/maintainable) UI framework these days
for web-based UIs?
* What other components do/should I need? Would like to
keep things as simple as possible.
* Monitoring: I used to use RedAlert. New ideas?
Thanks everyone.
David
_______________________________________________
Juglist mailing list
[email protected]
http://trijug.org/mailman/listinfo/juglist_trijug.org
