Mark Richman, Skeleton Key, presented a packed session about FileMaker and WAN performance on Monday of the FileMaker Developer Conference. It was so popular he was rescheduled to repeat the session on Tuesday afternoon. Mark joined me for an interview to discuss his session and the latest happenings at Skeleton Key.
I guess that blows Anchor Buoy for any FMD looking to implement FileMaker as SaaS, et al. I look forward to watching the resulting debate on this.
I’m not sure it disqualifies a particular approach to data modeling out of hand, at least not yet
I plan to perform some additional tests with more sophisticated data models than the simple ones I compared here. It’s possibly in complex systems that either approach (or a combination of the two, which may be practical for other reasons) is justified, e.g. in terms of workflow.
I think this could have a HUGE impact on the community if performance over the WAN is proven to be significantly worse using Anchor/Buoy…especially with all of the access to systems using GO.
I thought it was great that scalability issues were addressed in so many ways this DevCon – WAN performance, faster reporting through caching/scripting.
I think generally with GO we’re looking at a whole new ball game, and the kind of code we write is just going to have to be significantly different (read: more streamlined UI, more transactional scripting, less dependence on complex relationships).
Very interesting and wish I could have attended devcon this year. Anchor / Buoy always seemed to be more about organization and controlled relationship development. I always thought it might perform slower but shocked to hear some of these results.
It does seem like mobile computing as a whole (not just FMPGO) is going to have everyone reconsidering their design and business workflows.