While there are many different ways to skin this cat, our workplace (and my previous one, and the one previous to that) uses an MVC approach utilizing the Spring framework, Sitemesh (to handle the header, navigation, and footer portions of the presentation) and Freemarker as the view technology.
This approach has worked incredibly well as it allows our rather large applications to be split up amongst several developers, each of whom have strengths in different areas (although each can code in any layer, be it presentation, business logic, web services, or data layers).
In essence, we use Spring based controllers to handle the GET/POST requests, build the model (which is then exposed to Freemarker), and pull in the presentation view (which is obviously Freemarker based).
Sitemesh is used as a filter to decorate the Freemarker-generated web pages (presentation) with headers/footers and whatever navigation is relevant on that particular page.
All in all, a very nice setup, with good separation of powers (ie., MVC).
Sybase uses a concept called "Devices". Sybase supports up to 256 devices per server. If each "device" was really a 2gig disk or a 2gig file, then that would be 2gig * 250+ (you have to subtract for certain system devices that are already used) of available space. To support a 30-40gig DB, you would only need about 15-20 devices (or 2 gig files). We have done this on Linux already and it is quite easy. Of course, All the usual stuff about Administration is in effect (ie., backups, dbcc's, etc.) but with Sybase its extremely easy for a single admin to administer many DB's (and I won't even get going on the Database "Holy War" between Sybase and the Other BIG Relational DB companies).
Slashdot Mirror
Whats a blackberry? Is it like one of those old rotary dial phone thingies I've heard tell of?
While there are many different ways to skin this cat, our workplace (and my previous one, and the one previous to that) uses an MVC approach utilizing the Spring framework, Sitemesh (to handle the header, navigation, and footer portions of the presentation) and Freemarker as the view technology.
This approach has worked incredibly well as it allows our rather large applications to be split up amongst several developers, each of whom have strengths in different areas (although each can code in any layer, be it presentation, business logic, web services, or data layers).
In essence, we use Spring based controllers to handle the GET/POST requests, build the model (which is then exposed to Freemarker), and pull in the presentation view (which is obviously Freemarker based).
Sitemesh is used as a filter to decorate the Freemarker-generated web pages (presentation) with headers/footers and whatever navigation is relevant on that particular page.
All in all, a very nice setup, with good separation of powers (ie., MVC).
Sybase uses a concept called "Devices". Sybase supports up to 256 devices per server. If each "device" was really a 2gig disk or a 2gig file, then that would be 2gig * 250+ (you have to subtract for certain system devices that are already used) of available space. To support a 30-40gig DB, you would only need about 15-20 devices (or 2 gig files). We have done this on Linux already and it is quite easy. Of course, All the usual stuff about Administration is in effect (ie., backups, dbcc's, etc.) but with Sybase its extremely easy for a single admin to administer many DB's (and I won't even get going on the Database "Holy War" between Sybase and the Other BIG Relational DB companies).