I was reading an article on WWF vs. LiveLink Workflow and reminiscing with my time working with WWF in beta on a big .NET project here in Perth. We came across some stumbling blocks with the persistence layer, which has been rewritten for SharePoint so that it stores it within it's database natively.

One of the key criticisms of LiveLink Workflow was that it is written in it's own language and not in a more accessible one such as Java or .NET. There's been lots of promise of LiveLink and it's newly acquired little brother eDocs (Hummingbird) being rewritten, but I'd have no idea of when this is going to be released. I guess it reemphasises the comments I made in a recent post around SharePoint being built in .NET and on one framework. A lot of the other vendors are built on various platforms due to them being acquired over time.

Following on from this I was reading a very concerning post by Dave Wollerman that explained that after 60 days in a Workflow, the workflow association is purged. This basically means that anything after 60 days expires. This seems like a big flaw because there are often business processes that will include more than 60 days and over time frames! Reading the comments (where all the answers seem to be these days), it seems that there is a solution within Central Administration.