|Message:||Don't get me wrong - I am a Domino fan.... the right tool for the right job. Domino works really well when you have small apps eg Document Libraries and discussion-style databases. Where it falls over is in the level of control you get over your programming environment and the data source. NSF files just don't cut it in bigger apps (consider something like a timesheeting app - people, projects, jobs, time entries etc - all related. Not to mention the inherent performance problems when you get a large number of documents in a single NSF file.
On a public/internet website you can't stop some of the Domino default behaviours which may compromise your databases. $DefaultNav is a nasty, along with ?ReadViewEntries. Then there's the custom login form problems, stopping people opening forms (easily) if they know the names, ...
Puakma is aimed at that next level up: More complex web apps. Obviously the multi-platform thing is great, and the server itself is incredibly extensible: write your own authentication mechanisms, develop your own custom server AddIns. The relational datasource is used cleverly and much of the RDBMS complexity is hidden from developers, but at the same time if you want to mess about with the gamut of JDBC you can.
If you have a large Domino environment, definitely don't throw it out! Puakma represents a very cost effective way to implement complex web apps. You can even leverage some of that Domino infrastructure: use it as your mail router, run LDAP so you can log in your Puakma users against it, use CORBA calls from Puakma to leverage the data in it, etc.
The world seems to be moving to a "mix and match" software environment, and Puakma acts as that glue very well.|