2. Confidential and Proprietary2
• Building small reusable isolated components
• Multiple technology stacks JAVA/C++/NODESJS ..
• Shared components between multiple projects/teams.
WHERE WE STARTED ….
3. Confidential and Proprietary3
• Isolating logic in library/helper files
• Ctrl C Ctrl V
• npm modules and bower components
PAST SOLUTIONS
4. Confidential and Proprietary4
• Different technology stacks [JAVA/C++]
• Required teams to go through entire push cycle to get
updates.
• Out of sync components.
NPM AND BOWER DIDN’T WORK FOR US
9. Confidential and Proprietary9
Header
Footer
App
Merchant
App
Request header-footer.js
Response header-footer.js
Compiled dust templates
CDN
Request header-footer.css
Response header-footer.css
Render the template
Fires ajax calls in background to get
dynamic data
Response {JSON}
Renders
partials/components
based on response
10. Confidential and Proprietary10
• Technology stack agnostic
• Push updates rather than pull
• Same look and feel across teams and applications
• Release cycles drastically reduced.
• Template caching.
• Easy integration.
• Isolated testing
• No coordination required between teams.
BENEFITS
11. Confidential and Proprietary11
• Significant efforts to integrate with legacy code bases
• Not easy to test locally during integration, need to use npm
proxy or CORS.
• Single point of failure.
• Might have performance implications based on size of
javascript.
• Component CSS can get overwritten
CAUTION