Distributed architectures in Drupal What to do when your site is getting cramped? Drupalcamp Timisoara 2010
Introduction Kristof Van Tomme Co-founder  PRONOVIX.com Drupal, Distributed architecture
Goals of this session <ul><li>Highlight 2 important code trends
Classify architecture options
Highlight the most important technologies
Share our battle plan for world domination </li></ul>
One-off modules -> API modules
<ul>Site > code on your server </ul>
Easy to reuse Easy to connect Custom code one-purpose sites Frameworks - One-purpose modules Installation profiles Framewo...
<ul>We are moving from websites to webservices </ul>
<ul>All in one  sites  pro </ul><ul><li>reduced maintenance costs
greater flexibility (easy to put a block from one business application on a page of another)
no data transfer required (bandwith)
better performance (no network latency) </li></ul>
All in one sites  contra <ul><li>module overbloat (slower performance and potential integration issues)
Permission conflicts between sections
Over-abstracted to accommodate different use cases
Content pollution from other sections
Navigation might become a mess </li></ul>
What to serve? <ul><li>Content
Users
Functionality </li></ul>
Functionality = data mapping <ul><li>data transformations
data mediation
data relationship discovery
data masking/de-identification
data consolidation  </li></ul>
Sharing options <ul><li>Common resource
Just in time
Upcoming SlideShare
Loading in...5
×

Drupal distributed architectures

3,326

Published on

Slides for the presentation I gave in Timisoara

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
3,326
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
16
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Drupal distributed architectures

  1. 1. Distributed architectures in Drupal What to do when your site is getting cramped? Drupalcamp Timisoara 2010
  2. 2. Introduction Kristof Van Tomme Co-founder PRONOVIX.com Drupal, Distributed architecture
  3. 3. Goals of this session <ul><li>Highlight 2 important code trends
  4. 4. Classify architecture options
  5. 5. Highlight the most important technologies
  6. 6. Share our battle plan for world domination </li></ul>
  7. 7. One-off modules -> API modules
  8. 8. <ul>Site > code on your server </ul>
  9. 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
  10. 10. <ul>We are moving from websites to webservices </ul>
  11. 11. <ul>All in one sites pro </ul><ul><li>reduced maintenance costs
  12. 12. greater flexibility (easy to put a block from one business application on a page of another)
  13. 13. no data transfer required (bandwith)
  14. 14. better performance (no network latency) </li></ul>
  15. 15. All in one sites contra <ul><li>module overbloat (slower performance and potential integration issues)
  16. 16. Permission conflicts between sections
  17. 17. Over-abstracted to accommodate different use cases
  18. 18. Content pollution from other sections
  19. 19. Navigation might become a mess </li></ul>
  20. 20. What to serve? <ul><li>Content
  21. 21. Users
  22. 22. Functionality </li></ul>
  23. 23. Functionality = data mapping <ul><li>data transformations
  24. 24. data mediation
  25. 25. data relationship discovery
  26. 26. data masking/de-identification
  27. 27. data consolidation </li></ul>
  28. 28. Sharing options <ul><li>Common resource
  29. 29. Just in time
  30. 30. Just in time + caching
  31. 31. Aggregation </li></ul>
  32. 32. Common resource architectures <ul><li>Organic groups
  33. 33. Domain access
  34. 34. Shared tables
  35. 35. Spaces/features </li></ul>
  36. 36. Not flexible
  37. 37. Just in time <ul><li>Services
  38. 38. SPARQL </li></ul>
  39. 39. Network latencies
  40. 40. Aggregation <ul><li>RSS
  41. 41. Table wizard + migrate
  42. 42. Deploy </li></ul>
  43. 43. Not always up to date
  44. 44. Just in time + caching <ul><li>Content staging
  45. 45. Remote blocks
  46. 46. Remote nodes </li></ul>
  47. 47. Best of both worlds
  48. 48. Processed data <ul><li>Remote blocks
  49. 49. i-frames
  50. 50. JSON objects </li></ul>
  51. 51. The internet will be a collection of Service Providers and Mashups
  52. 52. Drupal is already really good at consuming services
  53. 53. Drupal is already really good at consuming services
  54. 54. Drupal is pretty good at serving content
  55. 55. What about the missing services? <ul><li>data transformations
  56. 56. data mediation
  57. 57. data relationship discovery
  58. 58. data masking/de-identification
  59. 59. data consolidation </li></ul>
  60. 60. If we can get better at producing easy to consume services we can conquer the world
  61. 61. http://pronovix.com/blog
  62. 62. @kvantomme
  1. Gostou de algum slide específico?

    Recortar slides é uma maneira fácil de colecionar informações para acessar mais tarde.

×