Part of the difficulty with any application design is ensuring that it's scalable. Sure your app may have originally only been intended for twenty or thirty people, so efficiency wasn't an issue. At least not until other teams caught wind of it, and then suddenly everyone in your organization wants to make use of your dashboard. Perhaps your manager eventually decides to incorporate your app into a larger portal, which has a much larger audience than you originally intended. Or perhaps its services got consumed by external sources that were not part of the original scope plan. Whatever the case, needs and demands change over time so it's best to ensure that your implementation is able to scale, up to a certain point.

During general development, it's a good idea to keep the footprint of the portlet and portlet WAR in mind. Efficiency is relative and your app will only go so far, but there are a few pitfalls you can avoid which will ensure that the application isn't being bottlenecked.

First we'll start with the largely unknown and unexpected. 

John Catona

 It has been just over four months since Davalen became a full-service partner with IBM. Our customer and potential customers, along with IBM, are already noticing a vast difference in Davalen's sales division. Before, Davalen had no direct sales footprint. Now, we have over $4 million in the pipeline and continue to grow a million a month. What a fantastic advancement, from an already very successful company.

Following the vision of Co-Principals Dave Jacobs and Len Barker, we transformed not only the way we do business, but also the way the whole ICS Brand in the Northeast and Mid-Atlantic does as well. Our commitment to excellence and dedicated customer service sets us apart from any other ICS IBM partner. Our cooperative approach to our IBM partnership, from the beginning of the sales cycle all the way through to the end, has proven unbeatable.

 Read more