Talk about swinging an elephant to scare the flies away:
You can find it on Google if you search, but we actually built a few 1-page static HTML pages (1 per domain) which was forced to be created on BEA Portal ($40k/cpu) with a commercial CMS ($35k/cpu). It had to be developed with the BEA standard tools + the CMS (so not allowed to just make a JSP and that’s it). Total dev costs $15k (which is cheap considering the above). So total 1-page site; ($40k+$35k+$15k) + ($10k/month for hosting + 15% per year for support) = $223500 for the first year. 1 page site.
It might not make much (any?) sense, but at least there’s an architecture behind that single HTML page. There’s a change control strategy behind it, and you know it will scale!
Architectures are important, they breath life into everything they touch. This quote is just half the summary of this introduction-level article:
Rich Internet Applications (RIAs) promise the dynamism and functionality of desktop applications through the browser. One of the key characteristics is moving your presentation layer to the client and backing it with a robust RESTful service layer on the server. This idea is being popularized with buzzwords like SOUI (Service Oriented User Interface) and SOFEA (Service Oriented Front End Architecture). Many organizations are pursuing a Service Oriented Architecture (SOA). This is often done to make your architecture more agile, allowing your business to more rapidly evolve. Of course, you probably have another pressing initiative in your organization: to modernize your user interfaces into a Rich Internet Application. It can be tough to deal with both buzz words, SOA and RIA.
Seriously? SOFEA? SOUI? A “pressing initiative” to modernize the UI by throwing more architecture at it?