15. Why did we build it?
- Personal projects
- Need code reuse
- Uncertain future (who will be the next big player)
- Change in web frontend landscape
- Change in web backend landscape
- Change in deployment landscape
- Need to roll your own
19. Semantic model in mu.semte.ch
- Semantic model is the applicationโs domain
- Each microservice is an actor
- Integration is easy
- [FUTURE] Evaluate reasoning for complex or evolving applications
20. Automatic integration of services is awesome
โฆ it is the bulk of what we explain to the un-indulged ...
โฆ but you already know that ...
โฆ give a taste of semantic technologies without a full buy-in.
26. - Some backend services have standard frontend components
- The road towards web components
- Not semantic
[Ember addons] Sharing frontend code
> ember install ember-mu-login
= application.hbs =
{{login-form}}
28. - A step towards semantic applications
- Extensive sharing of code
- Encourages experimentation
- State-of-the-art frontend applications
- Itโs just a step
In conclusion
29. <Thank You>
need more?
Erika Pauwels
- erika.pauwels@tenforce.com
- @ErikaPauwels
- http://github.com/erikap
- erika.pauwels@gmail.com
Aad Versteden
- aad.versteden@tenforce.com
- @impulsater
- http://github.com/madnificent
- madnificent@gmail.com
http://mu.semte.ch - http://tenforce.com - http://github.com/mu-semtech
This study was funded by yourdatastories.eu, as were parts of the microservices.