If you followed Peter’s series on replacing Lotus he outlined some of the pitfalls, processes and decision points to undertake for success. I wanted to point out the technical side to a lot of those decisions. The short answer is that you need a tool to surface your domino data en-masse until such a time when decisions are made on each application. I have been working on that solution for quite some time now and I have to say, it’s complex.

Over the last month or so, I’ve been working on an application that pushes performance quite a bit. Last week I published a blog post about aspects of developing for performance. I’ll be writing a future blog post (maybe more than one) on the approaches I’ve taken for performance. But in this blog post I want to take a step back and discuss why I had to address performance, even after quite a bit of optimisation from the initial development.