Download to read offline
Uploaded byMikita Manko
Developing of a high load java script framework
This document discusses the design and creation of a JavaScript framework for high-load websites. It describes architectural approaches like using isolated modules and events to improve performance. It also provides tips for optimizing frameworks for high loads, such as using content delivery networks, local storage, moving APIs client-side, and client-side profiling. The presentation encourages the single responsibility principle of creating separate modules for each task. It is given by Nikita Manko, a senior software engineer at EPAM.
More Related Content
Similar to Developing of a high load java script framework
Developing of a high load java script framework
- 1. Проектирование и создание JavaScriptframework'а для высоконагруженных сайтов Никита Манько / Mikita Manko
- 2. Никита Манько, sr. softwareengineer @ EPAM @MikitaManko
- 3. Проект • Front-end: UIWidgets • Back-end: services & DBs
- 4. Проект • Integration withsites of 70+ brands (real hell)
- 6. What is high-load? 1m+hits per day/hour/minutes?
- 7. Architecture • Core • Isolatedmodules/widgets • Events • Internal widgets
- 8. Architecture Single responsibility –for each separate task create separate module
- 9.
- 10.
- 11. High-load tips &tricks -Akamai
- 12. High-load tips &tricks -Report tracking
- 13. High-load tips &tricks -Local Storage
- 14. High-load tips &tricks - Move 3-rd party APIs to client
- 15. High-load tips &tricks -AppDynamics
- 16. High-load tips &tricks -Client-side profiling
- 17. High-load tips &tricks -jMeter load tests
- 18. High-load tips &tricks -Jasmine
- 19. High-load tips &tricks - Selenium web-driver UI tests
- 20. High-load tips &tricks - Mobile Optimized (OOP is here?)
- 21. High-load tips &tricks - Client-side error tracking
- 22. High-load tips &tricks - Move more stuff to front-end
- 23. A slide withno useful information at all • Just filling the gap between previous slide and the next one (which will be along in just a moment). • No need to write it down, unless you feel completed to do so. • In fact I’m not really sure why I bothered with it. • Nothing on this slide is examinable.
- 24. Никита Манько, sr. softwareengineer @ EPAM @MikitaManko gmail@MikitaManko.com Вопросы?