Most of the portlet / portal usage I have seen is for corporate intranet applications. Is it a good idea to use portlets for a internet application. I want to provide some customization / personalization for my users, is it advisable to go for a portal software only for this reason. How is the general performance of a portal software under high volume, and other scenarios related to an internet application.
Portal is very awesome, and some open source portals are pretty fast, such as JetSpeed.
Portal makes managing an overall website theme very easy, and it makes changing and managing the theme of the portal very easy. It also makes it easy to delever new content to a user by simply adding new Portlets, which are Servlet-like content delivery vehicles.
The other big benefit is the ability to integrate a portal with content management systems. That seems to be the big push with IBM.
Still, as much as I love JetSpeed and WebSphere Portal, I think it's overkill for a standard website. Good design patterns and practices should make developing your own, customizable and user centric website possible without having to go beyond the capabilities of JetSpeed.
Oh. I'd also say that many large companies have portals, because it's easy to sell a portal to a big company. Whether they are using the portal effectively is a different story.
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop