Building Realtime User Experiences

Building Realtime User Experiences “What,” “how,” and “monetizing that bitch.” TimesOpen 2.0 - Ted Roden @tedroden

What’s going on here? • Introduction ← you are here • What is it? • How does it work? • Show me the money.

Who is this guy?

Ted Roden

Ted Roden @tedroden tedroden@gmail.com tedroden.com

Who are you?

Mall Directory • Introduction (nailed it) • What is it? ← you are here • How does it work? • Show me the money.

Realtime A quick discussion of realtime. I’ve ﬁgured out how to do background colors!

On the web On the web • Not the spider web!

The way things were/are A history

The LAMP Stack You know it, you love it. Fits like an old glove

Or perhaps you’re a Rails nerd?

The LAMP Stack You know it, you love it. Fits like an old glove

LAMP is Fantastic at what it does Short/Fat/Fast Requests

Great for... • Holding the internet together • Serving documents • Scaling in ways we’re comfortable with • Maintaining backend state

Bad for... • Concurrent Users • Messaging • Realtime anything • Getting into the pantry... again!

Enter the new kids

Less about serving documents More about sending messages

What’s happening? What are the ground rules?

There is only one rule on the realtime web Go to your users.

Do not expect your users to know when you’ve got something to say.

“I’ve got something to say”

Do not wait for your users

Do not wait for your users Go to them.

Do not wait for your users Go to them. Via SMS, email, phone calls, whatever.

Mall Directory • Introduction (nailed it) • What is it? (twice? two times) • How does it work? ← you are here • Show me the money.

Long polling

Push vs Pull

The Old Way • Check for messages • Wait for a while • Check again...

The New Way™ • Check for messages • No messages? The server waits until there is one.

Can I see the difference in the form of a line drawing?

One trillion* Fewer Requests * it’s science

Why is it better? Because I said so.

Can keep things up to date That’s the whole point.

Fewer requests means... • Less strain on the database • Less strain on the browser • More room for everything else

We’ve got problems. • Message routing • Browser limitations • Blatant disregard for image licensing

Checking for messages It used to be so simple.

Message Routing Is very complicated • When a message is sent it needs to be routed to the correct client. • Cannot rely on waiting for the client to reconnect and searching the DB.

Luckily, all this is handled.

It’s a big problem for...

Mall Directory • Introduction (nailed it) • What is it? (twice? two times) • How does it work? (get to the point...) • Show me the money. ← you are here

The future

Building Realtime User Experiences “What,” “how,” and “monetizing that bitch.” TimesOpen 2.0 - Ted Roden @tedroden

http://tedroden.tumblr.com	53
http://safe.tumblr.com	13
http://superfeedr.tumblr.com	13
http://tedroden.com	9
http://storify.com	6
http://open.blogs.nytimes.com	2
http://paper.li	1
http://flavors.me	1
http://www.tumblr.com	1
http://lanyrd.com	1

Building Realtime User Experiences

by tedroden on Nov 03, 2010

Accessibility

Categories

Upload Details

Usage Rights

10 Embeds 100

Statistics

Building Realtime User Experiences Presentation Transcript