The document discusses the importance of parallel programming in web development, highlighting the author's background as a CTO and the challenges faced with scalability and shared state issues. It emphasizes the advantages of using Erlang and AMQP for scalable web architectures and messaging infrastructure compared to other programming languages. The author shares insights on their experience with various technologies and the evolution towards adopting open standards for better performance and load balancing.

1. parallel programming
why does it matter to web development

2. who i am
• german expat in NZ
• text editor addict since age 14
• CTO ideegeo Group Limited
• erlounge Wellington

3. erlounge Wellington
• diverse crowd
• more about parallel programming
• once a month

4. todays topics
• message passing infrastructure
• erlang
• open standards

5. scale web based
projects
• one server
• separate functionality (some server)
• load balance (some more server)

6. loadbalance
• web servers is easy
• databases is harder
• business logic often not possible

7. the problem
• shared state
• shared data
• waiting for other processes

8. in general terms

9. global locking

11. sounds familiar?
looks like a parallel programming issue to me

12. i tried to solve ...
• scalability issues
• scale to many servers
• asynchronous processes
• process queues
• callback queues

13. i wrote
• a simple perl based environment
• my own message queue
• my own messaging format

14. what i actually did
without knowing it ...

15. i wrote a MPI
ok, a quite basic message passing infrastructure but it
was one

17. and to my big surprise

18. this thing worked
better as expected

19. ... but ...

20. i found erlang

21. erlang ...
• is a functional language
• has a built in MPI
• share nothing approach

22. feels like heaven on
earth

24. issues
• not compatible to my existing stuff
• feel the pain of custom protocols
• rewrite or compat layer or ...

25. the usual thing
happened

26. ... i left it aside ...

27. ... meanwhile ...

28. i started to play with
• CouchDB
• RabbitMQ
• ejabberd

29. all erlang
and open standards based

30. the more I played
the more I wished I could use them

31. the inevitable happened

32. iteration two

34. AMQP

35. open standard
• backed by major players
• around for some years
• RabbitMQ (erlang based)

36. JSON

37. open format
• used by many
• small footprint
• easy to read for humans and computers

38. erlang

39. fast and small
• compared to perl/php/ruby/...
• scales linear to 32 cores
• distributing processes is easy

40. perl

41. still in the system
• for compatibility
• for string processing
• for stuff where it makes sense

42. [your lang here]

43. language independent
• JSON is available in most languages
• AMQP is available in all major languages
• pick the one that makes sense

45. internet architectures
• scaling to many servers
• loadbalancing
• reducing global locks

46. multicore programming
• scaling to many cores
• loadbalancing
• reducing global locks

47. do we solve simmilar
problems here?

48. where to find me
• @norbu09
• http://norbu09.org
• http://github.com/norbu09
• http://slideshare.net/norbu09

50. thanks
• http://www.flickr.com/photos/dranidis/
• http://www.flickr.com/photos/samuellkim/
• http://www.flickr.com/photos/tbcave/