Slides for the presentation I gave in Timisoara

1. Distributed architectures in Drupal What to do when your site is getting cramped? Drupalcamp Timisoara 2010

2. Introduction Kristof Van Tomme Co-founder PRONOVIX.com Drupal, Distributed architecture

4. Classify architecture options

5. Highlight the most important technologies

6. Share our battle plan for world domination

7. One-off modules -> API modules

9. Easy to reuse Easy to connect Custom code one-purpose sites Frameworks - One-purpose modules Installation profiles Frameworks - API modules Installation profiles with features Drupal service clouds - modular sites features

12. greater flexibility (easy to put a block from one business application on a page of another)

13. no data transfer required (bandwith)

14. better performance (no network latency)

16. Permission conflicts between sections

17. Over-abstracted to accommodate different use cases

18. Content pollution from other sections

19. Navigation might become a mess

21. Users

22. Functionality

24. data mediation

25. data relationship discovery

26. data masking/de-identification

27. data consolidation

29. Just in time

30. Just in time + caching

31. Aggregation

33. Domain access

34. Shared tables

35. Spaces/features

36. Not flexible

38. SPARQL

39. Network latencies

41. Table wizard + migrate

42. Deploy

43. Not always up to date

45. Remote blocks

46. Remote nodes

47. Best of both worlds

49. i-frames

50. JSON objects

51. The internet will be a collection of Service Providers and Mashups

52. Drupal is already really good at consuming services

53. Drupal is already really good at consuming services

54. Drupal is pretty good at serving content

56. data mediation

57. data relationship discovery

58. data masking/de-identification

59. data consolidation

60. If we can get better at producing easy to consume services we can conquer the world

61. http://pronovix.com/blog

62. @kvantomme