Eclipse Flux - A micro-service architecture for cloud-based developer tooling

Transcript

1. Eclipse Flux Eine Micro-Service-Architektur für cloud-basierte Entwicklungswerkzeuge Martin Lippert, Pivotal mlippert@pivotal.io @martinlippert
2. todays Desktop IDEs are great
3. but the world has changed
4. “Why can Google search the Internet in 10ms and Eclipse needs 5sec to open a type hierarchy?”
5. nowadays Ubiquitous, variable user interfaces Massively scalable compute and storage Seamless and automatic software and data delivery Always connected
6. developer tooling in the cloud ?
7. challenge #1 run in the cloud
8. challenge #2 no either-or, enable both
9. challenge #3 do not re-implement everything
10. http://www.eclipse.org/flux
11. Demo
12. the architecture
13. async
14. Eclipse IDE Asynchronous Messaging Workspace Repository Cloud Region A Backup Repository
15. Eclipse IDE Asynchronous Messaging Workspace Repository Cloud Region A Backup Repository File Sync
16. Eclipse IDE Asynchronous Messaging Workspace Repository Cloud Region A Backup Repository Browser Editor Local Storage
17. Eclipse IDE Asynchronous Messaging Workspace Repository Cloud Region A Backup Repository Browser Editor Local Storage File Sync &
 Live Sync File Sync
18. micro-services
19. Eclipse IDE Asynchronous Messaging Workspace Repository Cloud Region A Backup Repository Cloud Region B Java
 Service Browser Editor Local Storage
20. Eclipse IDE Asynchronous Messaging Workspace Repository Cloud Region A Java
 Service Browser Editor Local Storage Cloud Region B Scala
 Service Cloud Region C JavaScript Service
21. highly decoupled
22. Eclipse IDE Asynchronous Messaging Workspace Repository Cloud Region A Java
 Service Browser Editor Local Storage Cloud Region B Scala
 Service Cloud Region C JavaScript Service
23. Eclipse IDE Asynchronous Messaging Workspace Repository Cloud Region A Backup Repository Browser Editor Local Storage Cloud Region B Backup Repository …
24. highly distributed
25. Eclipse IDE Asynchronous Messaging Java Service Workspace Repository Cloud Region A Backup Repository Cloud Region B Java
 Service Browser Editor Local Storage
26. Eclipse IDE Asynchronous Messaging Workspace Repository Cloud Region A Java
 Service Browser Editor Local Storage Cloud Region B Scala
 Service Cloud Region C JavaScript Service
27. real-time data sync backbone
28. Eclipse IDE Asynchronous Messaging Workspace Repository Cloud Region A Backup Repository Cloud Region B Java
 Service Browser Editor Local Storage Live Sync &
 Service Results File Sync
29. the overall picture
30. Local Services Asynchronous Messaging Local Editors and IDEs Workspace Repository Cloud Region A Backup Repository Cloud Region B Java
 Service Browser Editor Local Storage GitHub Repository Cross- Reference Service JavaScript
 Service Scala
 Service Collab. Service Cloud Foundry Service Executor Service
31. design choices & early experiences
32. services are not “called” - they engage and react
33. there is no master - data sync in p2p style
34. decomposing existing IDEs into micro-services is hard - but possible
35. async is a different beast
36. everything is eventually consistent
37. offline remains a challenge
38. more Q&A
39. Thank You Martin Lippert, Pivotal mlippert@pivotal.io @martinlippert