Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Scaling ideas and principles

3 883 vues

Publié le

A quick talk on concepts of making web applications scale - non-technical as the crowd was mixed sales and marketing

Publié dans : Technologie, Business

Scaling ideas and principles

  1. 1. Scaling ideas and principles. Chris&an Heilmann Launch 48, London, England, June 2010
  2. 2. It is very easy to build things and put them on the web.
  3. 3. Making them work for a lot of people is much harder.
  4. 4. You can however do things to prepare yourself for the future.
  5. 5. The first thing to remember is to delegate to experts.
  6. 6. Not a good driver.
  7. 7. If you want to scale as a business, don’t try to be Pinky.
  8. 8. Instead, partner with experts do to expert work for you.
  9. 9. Pick a big goal
  10. 10. And then chunk it up into parts you should deal with.
  11. 11. And others that are already services you can use instead of re-inventing them.
  12. 12. Hosting of your product should not be in one spot.
  13. 13. Separate your product interface and the data you provide or store.
  14. 14. And pick specialised services and technologies for each of them.
  15. 15. Amazon S3/EC2 Google App Engine Joyent Microsoft Azure (...)
  16. 16. If you don’t get the base right...
  17. 17. You don’t have a chance to look into the distance.
  18. 18. Data is your main product.
  19. 19. If you make it easy for people to reach, store and enrich data you have a good start.
  20. 20. Have total separation of information and display.
  21. 21. This allows you to offer information in a format that other people can innovate for you.
  22. 22. It also allows you to build in parallel and create a great experience for your end users.
  23. 23. Obvious things that will keep you from scaling:
  24. 24. 1) Maintaining your own technical infrastructure.
  25. 25. 2) Building a monolithic product rather than a modular system.
  26. 26. 3) Lack of resources and manpower.
  27. 27. The third issue is easy to solve...
  28. 28. Do not re-invent the wheel but research what you can use and pick and mix.
  29. 29. http://winterolympicsmedals.com
  30. 30. http://www.guardian.co.uk/news/datablog/ 2010/feb/11/winter-olympics-medals-by-country
  31. 31. YQL     h>p://developer.yahoo.com/yql/console/
  32. 32. YQL     h>p://developer.yahoo.com/yql/console/ select {what} from {where}  where {condi&ons}
  33. 33. select * from csv where url="http:// spreadsheets.google.com/pub? key=tpWDkIZMZleQaREf493v1Jw&output= csv" and columns="Year,City,Sport,Discipline,Countr y,Event, Gender,Type" and Year="1924"
  34. 34. http://developer.yahoo.com/ypatterns
  35. 35. http://developer.yahoo.com/ypatterns/wireframes/
  36. 36. http://developer.yahoo.com/yui/grids/builder/
  37. 37. http://developer.yahoo.com/yui/
  38. 38. Top tip - use the web to build for the web.
  39. 39. Use the web as your data source. CMS
  40. 40. Don’t build your own login system!
  41. 41. For extra speed and less resource burning tweak the interface.
  42. 42. h>p://developer.yahoo.com/performance/
  43. 43. h>p://developer.yahoo.com/yslow/
  44. 44. Don’t fall into the personnel trap!
  45. 45. Churn of technical staff will slow down your product and cost you a lot.
  46. 46. Instead of relying on one wizard to do all the work, build a team.
  47. 47. This means people can get sick, can leave and you will still be around.
  48. 48. And it is a lot of free PR for your company - happy techies tell others to come.
  49. 49. Christian Heilmann http://wait-till-i.com Thanks! http://developer-evangelism.com http://twitter.com/codepo8