Just a thought for Internet Web Development departments. Many times a department will make a decision to use another technology (for example, an open source Java library) which is free. Its quickly implemented, but the department and the company never stop to calculate the true costs. When adding any new technology, there will always be a learning curve, not only for the current employees but also for any new employees brought on in the future (whether out of growth or for replacement). As well, now that an additional skill set, or API knowledge is needed, it might increase what the company has to pay to hire an employee.

The added technology may solve a real problem, and may not cost the department anything up front. But the question is, how much company time and money will it cost down the road? Will it be harder to replace any employees who have this new knowledge? Will other employees in the department need training? How quickly will they be able to pick it up? Will it unnecessarily complicate your application?

All important questions to ask.

[tags]IT Management, Web Development[/tags]

In a previous post, I suggested I’d like to see a much looser coupling between the front-end, or GUI portion, of a web app, and the back-end, which handles data persistence, business rules, and all other types of data processing. Really, what I’m suggesting, is that these areas be broken down into separate unique services. The further we break components down, the easier it is to design them, code them, test them, and maintain them (at least to a point, you can go too far with this).

If you aren’t yet familiar with Service-Oriented Architecture, then read this post from several years ago on webservices.xml. It’s a good introduction to the concepts. So far in my experience, I think the GUI is being asked to do far too much; to be far too smart for its own good. I’d rather all the brains of the user interface be provided by services, and the front end simply stick to the role of providing a visual interface to those back-end services.

I still believe that Java is ideal for the back end portion of a web site or Internet application. When I say “back end”, I am referring to the data manipulation including the use of business rules and data persistence.

Its the use of Java on the front end, the web gui, that I’m not so sure I’m convinced of at this point. When JSP first came out, it seemed so simple, but then we began to get so concerned over separating roles and markup, content, and logic. Now creating a web site is just too much work. Lately, I’ve been using Word Press to do my blogs, and using Open Reports to create a reporting web site. Both of these are great examples of the simplicity in creating web sites. Open Reports creates forms to fill out with a simple web gui interface. Both of them require no “coding” in order to add further pages, change the look and feel, etc. They aren’t as custom as would be needed for most of the web applications I’ve worked on, but, I think we should be able to get to a point where the web front end is as simple as using Word Press, Open Reports, or any of the other CMS type web tools.

Read the rest of this entry >>