- About the author
- Questions and Issues
- Edit and Contribute
- Introduction
- 1. Workshop Overview
- 2. KnockoutJS
- 3. Background
- 4. Features/Blades
- 5. Apps & Aspects
-
6. Services & the ServiceRegistry
- 6.1. Services
- 6.2. ServiceRegistry
- 6.3. Problems Solved
- 6.4. Developer Environment Dependencies
- 6.5. Required Dependencies
- 6.6. No Backend Dependencies
- 6.7. Configuring Services
- 6.8. Workbenches
- 6.9. Modular App Services
- 6.10. Modular App Services
- 6.11. User Service
- 6.12. Chat Service
- 6.13. Exercises Overview
- 6.14. Exercise: Input Blade & Services
- 6.15. Exercise: Messages Blade & Services
- 6.16. Exercise: User Card Blade & Services
- 6.17. Retrospective
- 7. Apps & Aspects (again)
- 8. Extras
- 9. That's a Wrap!
- 10. Reference
What are Features/Blades?
At Caplin we use the term Blade to represent an application feature. This is because it represents a full slice of application functionality containing everything required to fullfil a business requirements. So, "Feature" and "Blade" are generally inter-changable.
Typical JavaScript Application Structure
Application Structure By Feature
What would a Blade look like in GMail?
