Easy microservices with JHipster

Easy microservices with JHipster

Easy microservices with JHipster.

32e6a76c61f41da3beca909251498c60?s=128

Sendil Kumar N

May 16, 2018
Tweet

Transcript

  1. Easy Microservices with JHipster Sendil Kumar N

  2. Sendil Kumar N • Full stack developer @Xebialabs

  3. Sendil Kumar N dev test uat prod [Cloud] Orchestration Stack

    Middleware NoSQL PaaS Containers OS OS OS IaaS Network Servers DB / Storage Security SOFTWARE DEFINED DATA CENTER / CLOUD RELEASE ORCHESTRATION Agile Backlog Management Provisioning/ Configuration Security ITSM / Service Management CMDB plan Project Management Issue
 Tracking ALM DEPLOYMENT AUTOMATION code SCM Code Analysis build Continuous Integration Centralized
 Repository test Test Tooling Test Visualization release ChatOps / 
 Collaboration Email/
 phone/ Excel operate BI /
 Monitoring Logging
  4. Sendil Kumar N • Full stack developer @Xebialabs • Core

    dev team member @JHipster
  5. Sendil Kumar N • Full stack developer @Xebialabs • Core

    dev team member @JHipster • Team member @webpack
  6. Sendil Kumar N • Full stack developer @Xebialabs • Core

    dev team member @JHipster • Team member @webpack • Pa@ of rust-wasm Working Group
  7. Sendil Kumar N • Full stack developer @Xebialabs • Core

    dev team member @JHipster • Team member @webpack • PaA of rust-wasm Working Group • Big open source lover & enthusiast
  8. None
  9. @sendilkumarn Anybody who has a twiJer here…

  10. Frontend? Bundler

  11. Backend?

  12. Deployment CI/CD?

  13. JHipster Greetings from Java Hipster

  14. 10K+ Github stars

  15. 420+ Contributors

  16. 200+ Companies

  17. 13K + Weekly downloads

  18. 84% test coverage 40K + lines of Code

  19. So what do JHipster do?

  20. Application Generator

  21. Monolithic / Micro-services / UAA

  22. Why Microservices?

  23. Independent Development

  24. Independent Deployment

  25. Fault Isolation

  26. Granular Scaling

  27. –Ma$in Fowler & James Lewis “If the components do not

    compose cleanly, then all you are doing is shi7ing complexity from inside a component to the connections between the components to a place that’s less explicit and harder to control”
  28. Complexities

  29. Service Registries

  30. Health Checkers

  31. Deployments

  32. Highly available

  33. “Adding highly available services and lot of moving pa?s…”

  34. “… without clear separation of models & design …”

  35. “… will result in lesser productivity and is always error

    prone …”
  36. “Adds a lot of boiler plate code”

  37. Microservices Architecture

  38. GATEWAY CONSUL JHIPSTER REGISTRY MICROSERVICES CONSOLE

  39. Deployments

  40. Demo time …

  41. JHipster conf June 21, 2018 @Paris

  42. Questions ?

  43. Happy Hacking