Q: Scaling and backing

[cmundi]

Poet strikes a very nice balance between control and usability. Coolness. I don't see a wiki. I did see the invite to tweet, but that format is a bit limiting. :)

Do I understand correctly that Poet parses all of the posts and keeps all of the posts in memory? If so, can someone comment on scaling? Would it make sense to add hooks for a backing db? I realize this would come at the cost of the simple files store plus watch() model.

[ChrisMcKenzie]

I have been thinking about this for a while now. I have been thinking about a possible Google drive back end much like this tutorial by Addy osmani http://www.html5rocks.com/en/tutorials/webcomponents/yeoman/

[cmundi]

@ChrisMcKenzie ... That would be pretty cool and take away my last good excuse for not blogging when I'm traveling.

[jsantell]

It does store all the posts as memory.. not sure of scaling, although it would be interesting to see what happens with 1000+ posts. Something to check out!

And in terms of DB backing, #53 is related -- other sources of posts would be cool, and could be DB or Google drive based. In terms of alternative post source, discussion should be in #53, but I'll leave this open for discussion on scalability, in terms of posts once imported NOT being stored in memory.

Thanks!