January 27, 2021
Hot Topics:

Reuse and the Portal Onion

  • By Jeffrey Ryan
  • Send Email »
  • More Articles »

The implications of the portal onion are that an overall architecture is needed to guide use of the portal framework and to reap the benefits of a common set of services and portlets which are reused across user experiences.

Is your organization seeking to improve user experience while lowering development and maintenance costs? When looking at reuse, has your organization considered how it might reuse assets among its many front-end applications? Do you have an overall architecture for your front-end applications that promote reuse? If your answer is no to any of these questions, you would do well to consider utilizing a portal framework, and the concept of a portal onion, to reap the many benefits of reuse. The rest is up to you!

About the Author

Jeff Ryan is an enterprise architect with twenty-four years experience architecting and implementing thoughtful solutions to business problems. Jeff regularly uses the concept of the portal onion described in this article to explain front-end reuse to his business and IT stakeholders. Click here to browse Jeff's catalog of articles on enterprise architecture, front end architecture, portal, SOA, Java, XML, and XSLT.

Page 2 of 2

This article was originally published on October 8, 2008

Enterprise Development Update

Don't miss an article. Subscribe to our newsletter below.

Thanks for your registration, follow us on our social networks to keep up-to-date