Twoorl: an open source Twitter clone

[Yariv Sadan]

Hi,

I created an open source Twitter clone in Erlang called Twoorl. I
wrote it on top of ErlyWeb/Yaws. You can see it at http://twoorl.com.
The code is at http://code.google.com/p/twoorl.

I'll appreciate any feedback!

Thanks,
Yariv

[Nick Gerakines]

MySQL? Seriously?

I've heard from multiple sources database congestion is a major source
of scaling problems for websites. Why take MySQL over a fragmented
mnesia store or a set of hybrid services?

# Nick Gerakines

> _______________________________________________
> erlang-questions mailing list
> erlang-q...@erlang.org
> http://www.erlang.org/mailman/listinfo/erlang-questions
>

[Thiago Pradi]

Great!

This open-source project is really cool!

Thanks,

Thiago Pradi

On May 29, 2:26 am, "Nick Gerakines" <n...@gerakines.net> wrote:
> MySQL? Seriously?
>
> I've heard from multiple sources database congestion is a major source
> of scaling problems for websites. Why take MySQL over a fragmented
> mnesia store or a set of hybrid services?
>
> # Nick Gerakines
>

> On Wed, May 28, 2008 at 10:12 PM, Yariv Sadan <yarivsa...@gmail.com> wrote:
> > Hi,
>
> > I created an open source Twitter clone in Erlang called Twoorl. I
> > wrote it on top of ErlyWeb/Yaws.  You can see it athttp://twoorl.com.

> > The code is athttp://code.google.com/p/twoorl.

>
> > I'll appreciate any feedback!
>
> > Thanks,
> > Yariv
> > _______________________________________________
> > erlang-questions mailing list

> > erlang-questi...@erlang.org
> >http://www.erlang.org/mailman/listinfo/erlang-questions

[David Pollak]

Yariv,

Nice stuff.  A question and an observation:

Q: Are you planning to add a comet-based scrolling timeline?

O: The creation of a timeline from the backing store on request strikes me as one that is prone to performance problems (see http://twitter.com)

Thanks,

David

--
lift, the simply functional web framework http://liftweb.net
Collaborative Task Management http://much4.us
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp

[Yariv Sadan]

Thanks! Comet based scrolling is relatively low priority. There are a
bunch of other feature requests I'm working on. Twoorl users are a
small but pretty excited bunch :)
I'm not planning on keeping the current db-backed timeline rendering.
I realize it wouldn't well when users start having too many friends.
To avoid this bottleneck, I'm planning on keeping a per-user data
store (in mnesia or memcache) for the last 20 twoorls (=tweets) from
their friends. New twoorls would be broadcasted (ie copied) to all
(active) followers. It's a space/speed tradeoff. This solution
wouldn't allow paging (unless I increase the cache size) but I think
it's a good tradeoff.

I still have some way to go before I hit these scaling problems, though.

Yariv