Best practises for HTML5 servers (Devaamo Summit 2012)
•
0 gostou•1,502 visualizações
Presentation by Otto Kekäläinen at Devaamo summit on 2012-06-16
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Destaque
Destaque (8)
Semelhante a Best practises for HTML5 servers (Devaamo Summit 2012)
Semelhante a Best practises for HTML5 servers (Devaamo Summit 2012) (20)
Mais de Otto Kekäläinen
Mais de Otto Kekäläinen (20)
Último
Último (20)
Best practises for HTML5 servers (Devaamo Summit 2012)
- 1. Devaamo Summit 2012 Best practices for HTML5 servers Otto Kekäläinen Tampere 16.6.2012
- 6. What is HTML5? 1995 1997 HTML 2.0 HTML 4.0 1999 2000 2001 2008 2011 May HTML XHTML XHTML HTML5 XHTML HTML5 4.01 1.0 1.1 Working 2.0 Last Call Draft 2005: CSS3 2011 June: ECMAScript 5.1 never?
- 8. What is HTML5? CACHE MANIFEST SVG NETWORK: WOFF /checking.cgi WEBM CACHE: /test.css localStorage.setItem('key', 'value'); /test.js localStorage.getItem('key'); /test.png <header> <footer> <article> <nav> <video> <audio> <canvas> <input type=”range”> <input type=”color”> Mark Pilgrim http://diveintohtml5.info/ function displayPosition(position) { var p = document.getElementById("p"); p.innerHTML = "<table'><tr><th>Timestamp</th><td>" + position.timestamp + "<tr><th>Latitude</th><td>" + position.coords.latitude + " deg</td></tr>" + "<tr><th>Longitude</th><td>" + position.coords.longitude + " deg</td></tr></table>"; } getCurrentPosition(displayPosition, displayError);
- 9. Why is HTML5 important? Flash Silverlight Java Applets
- 10. Why is HTML5 important? The universal runtime Any browser, any OS, any device (+ XULRunner, Prism, PhoneGap)
- 11. Universal means Big audience Lots of €€€€€
- 13. The secret to global success? Leverage on open source! - small cost, forever - widely used, proven technology - best practices built in the most popular tools
- 17. If Google ran on Windows servers, could they ever really be a threat to Microsoft?
- 19. Why emphasize servers? - a security issue is more severe in server code than in client code - server failure is fatal - servers have running costs
- 20. Where do you want to go – directions: programming language framework storage http server caching delivery
- 22. for Python for Node.js Zend Framework for PHP ..or CakePHP Ruby on Rails for Java / J2EE
- 24. To SQL or NoSQL? Midgard2
- 25. Global popularity of http servers
- 26. HTTP server considerations forking vs. threading FCGI, WSGI Node.js? web sockets SDPY
- 27. Cache, Proxy, TLS, DNS ..
- 28. DevOps Test: Jenkins, Apache Bench, webpagetest.org Deploy: build scripts, snapshotting Monitor: Munin, Nagios/Icinga, logger, XMPP, Git hooks, services on the web (Pingdom, monitor.us) Manage: Know you Linux distro tools (Landscape, SUSE Manager)
- 29. Platform as a service Virtual servers as a service Hardware as a service Buy your own servers Build you own servers
- 30. See our blog at seravo.fi for nitty gritty details later this summer! http://wikitech.wikimedia.org/view/Presentations http://instagram-engineering.tumblr.com/post/13649370142/whatpowers-instagram-hundreds-of-instances-dozens-of http://www.slideshare.net/protocol7/spotify-architecture-pressing-play http://www.slideshare.net/adorepump/skytools-pgq-queues-andapplications
- 31. There is no one way. You should find you own path. Just remember that at a crossroad between an open and a closed source option, choose open source.
- 32. Product development success factors speed cost features Stay agile! quality
- 33. Contact Seravo Oy:n if you need Linux natives to develop and administer your Linux systems About the company: seravo.fi About the technologies: seravo.fi/blog