The Bleeding Edge
- 1. The Bleeding Edge Richard Warburton and Martijn Verburg http://www.jclarity.com
- 2. "Toto, I’ve a feeling we’re not in Kansas anymore" - Dorothy, Wizard of Oz
- 3. Who are we? ● jClarity - We solve performance problems ● Richard - Engineer, Author, Speaker ● Martijn - CEO, Author, Speaker, Cat Herder
- 4. The Status Quo What is jClarity building? How we pick Technology Technology Scorecard A Brave New World
- 6. We have a lot of Java EE Experience ● LJC is on the JCP Executive Committee ● Martijn is a CERTIFIED BEA Weblogic ○ Something, something, something Darkside ● Lots of experience and deep community
- 7. But what if you don’t use that?... … we don’t!
- 8. The Status Quo What is jClarity building? How we picked Technology Technology Scorecard A Brave New World
- 9. The Answer ..to your performance problems Easy Access, Lightweight and Low Impact
- 11. Daemon, Aggregator & UI ● Daemon ○ Needs to be Low Impact, Low Traffic, Self-Updating ● Aggregator ○ Non-blocking I/O, Sockets > HTTP, High Availability ● UI ○ Rich Browser App, Accepts server-push events
- 12. Doesn’t really fit the Java EE World ● Daemon: Java EE is not low impact ● Server: Java EE is mainly about req/resp ● UI: Java EE lacks support for push events ○ Java EE 7 has Websockets now
- 13. The Status Quo What is jClarity building? How we picked Technology Technology Scorecard A Brave New World
- 15. Our Methodology Stolen ‘Adopted’ from Matt Raible 1. 2. 3. 4. 5. Identify Ranking Criteria Weight each criteria Score each solution Multiply and add Prototype top two choices
- 17. Observations ● Cons ○ Still Subjective ○ No guarantees ● Pros ○ Incorporates diverse feedback ○ Avoids bike-shedding ○ Avoids Technology Dictatorship
- 18. The Status Quo What is jClarity building? How we picked Technology Technology Scorecard A Brave New World
- 19. What Tech Stack did we pick?
- 21. AngularJS ● Client-side Javascript framework ● Model-View-Whatever (MVC or MVVM) ● Two-Way Data Binding ● Directives used to encapsulate components
- 22. AngularJS - Positives ● Html5 concepts without adoption issues ● Declarative - easy to understand and read ● Simple code structure ● Client side templating
- 23. AngularJS - Negatives ● Karma Framework doesn’t integrate well ● Use of $scope.$apply ● People are familiar with jQuery ○ Declarative learning curve. ● Javascript tooling still kinda sucks
- 24. AngularJS - Scorecard "Real win over hand rolled Javascript"
- 25. MongoDB ● NoSQL Document Store ● “Scalable” - easy sharding ● “Fault Tolerant” - easy data replication ● The new DB sexy!
- 27. MongoDB - Positives ● Document Modelling ● Nice API ● Easy to adopt and get started ● Easy Replication and Sharding ● Can be Fast*
- 28. MongoDB - Negatives (1) ● Security ○ we compiled an SSL-enabled mongo ○ pwning folks? Find out if they use Mongo! ○ tool support ● Data Integrity Concerns ● Split Brain - election algorithm failures
- 29. MongoDB - Negatives (2) ● Difficult to automatically sysadmin ● Immaturity of Drivers/Connectors (PHP) ● Document model is limited ● New query language to learn ● Poor timezone support
- 30. MongoDB - Scorecard "Consider your security strategy well." "Is a document store what you really need?"
- 31. Vert.x ● Polyglot Reactive Programming Framework ● Message Passing Oriented ○ Lightweight Eventbus ○ No Shared Mutable State ● Non-blocking I/O ● Websocket Support
- 32. Vert.x ● Polyglot Reactive Programming Framework ● Message Passing Oriented ○ Lightweight Eventbus ○ No Shared Mutable State ● Non-blocking I/O ● Websocket Support
- 34. Vert.x - Positives ● No shared state, easy concurrency ● Eventbus to the browser! ● Community++ ● Polyglot ○ We used Groovy and Java
- 35. Vert.x - Negatives ● Immaturity: ○ Released 2.0 without supporting 1.3 ○ Testing Framework not quite there ● NIH Logging ● Inter Machine Eventbus Security ○ Not originally designed for the open internet
- 36. Vert.x - Scorecard "It's perfect…. for the RIGHT use case."
- 37. Chef ● Automates server configuration ○ Centralised repo of pre-built recipes ○ Ruby based DSL ● Can also automate application deployment ○ Run update to deploy config/binaries
- 38. Chef - Positives ● Lots of Java/JVM recipes ● Ability to set roles and override properties ● Centrally controlled configuration ● Provides structure and deployment model
- 39. Chef - Inconsistent knife cookbook upload apache2 knife role from file roles/foo/bar.rb knife data bag from file users john.json
- 40. Chef - Negatives ● Managing dependencies is difficult ○ Use Librarian to help ● Not Declarative ○ e.g: doesn’t remove old config ● Still very complex ○ Steep learning curve
- 41. Chef - Scorecard "Chef, it's way better than shell scripts"
- 42. Common Bleeding Edge Themes 1. Immaturity 2. Lack of tooling 3. Problems at the boundary
- 43. The Status Quo What is jClarity building? How we picked Technology Technology Scorecard A Brave New World
- 46. What are you paying for? ● What does your support contract get you? ● Who does it get you? ● What’s the lock-in?
- 47. A La Carte Open Source ● Popular with $0 budget startups ● Commercially funded tech ● Strong Community Support ● Benefits elsewhere
- 48. The 'A La Carte' Relationship ● Be part of the community ○ We participated in Vertx IRC/London meetings ● Don’t diverge - upstream Patches ○ Vert.x, mod-mongo, Jacoco ● Open Source your plumbing ○ https://github.com/johnoliver/release-version-plugin
- 49. How do I do this? ● Low risk project ○ 20% time? ● Ask for forgiveness, not permission! ● Don’t fear “them”
- 51. Q&A Get your Free Trials at: http://www.jclarity. com @jclarity