A web portal's true potential lies in its ability to access multiple applications across an enterprise backbone, as well as applications residing on the public web. "Gadgets" have emerged as a lightweight alternative to build portal-like applications for the enterprise. Driven mainly by the fact that it is much easier to develop gadgets compared to portlets (and hence build applications faster), Gadgets are becoming increasingly popular. Many enteprise portal software vendors now support gadgets, albeit using different names like "Widgets" and "Blocks."
There are some similarities between gadgets and portlets, but you should understand key differences in terms of architecture, governance, ecosystem, standards, development processes, and so forth.
In our latest advisory briefing, How to Support Gadgets in Your Portal, we explain the similarities and differences, then outline two possible approaches for supporting gadgets within your portal environments.
Here's the table of contents for the advisory paper:
- Key Takeaways
- Contrasting Gadgets and Portlets
- When to Use Gadgets vs. Portlets
- Two Approaches for Supporting Gadgets in your Portal
- Related Articles
Our Portals and Content Integration Research subscribers can download the paper, as well as comment or ask questions directly on the page, after logging in.