Go micro with microservices

34be88398f623c109b61d23e8215bd23?s=47 Mariusz Gil
August 20, 2016
Programming
5
390

Go micro with microservices

34be88398f623c109b61d23e8215bd23?s=128

Mariusz Gil

August 20, 2016
Tweet

Want more?

34be88398f623c109b61d23e8215bd23?s=48 mariuszgil
1
200
34be88398f623c109b61d23e8215bd23?s=48 mariuszgil
0
25
34be88398f623c109b61d23e8215bd23?s=48 mariuszgil
1
150
3ab1249be442027903e1180025340b3f?s=48 reverentgeek
4
210
A9a491b0fcbe0fbce3d64063a37add99?s=48 rmw
1
110
766b9746b59e6f09e280cd33cf4ed419?s=48 skipperchong
0
87
61857dafbd287b3027c4dcea9008ad3c?s=48 carmenhchung
5
190
06f8b41980eb4c577fa40c41d5030c19?s=48 keathley
5
170
C0390e8b11079f8761c0cd3274ed61cb?s=48 productmarketing
2
230
C35e01544a0dd94a2cf1619ee8a42ebb?s=48 clairelew
3
460
6bb82b13cda86d3b821fa44100335ddf?s=48 thoeni
1
120
B3ace07412a5178ea778e7eec161fc0a?s=48 jcasabona
4
210

Transcript

  1. 1.

    MICROSERVICES Go micro with Mariusz Gil mariuszgil

  2. 2.
    None
  3. 3.
    None
  4. 4.

    THE STORY YOU KNOW

  5. 5.
    None
  6. 6.
    None
  7. 7.
    None
  8. 8.
    None
  9. 9.

    MONOLITHꊾ Product Management UX Developers QA DB Admins Sys Admins

    Net Admins SAN Admins
  10. 10.
    None
  11. 11.
    None
  12. 12.

    REASONS…

  13. 13.

    T D D

  14. 14.

    T D DHINK ESIGN EVELOP

  15. 15.

    MICROSERVICES

  16. 16.
    None
  17. 17.

    LOOSELY COUPLED SERVICE ORIENTED ARCHITECTURE WITH BOUNDED CONTEXTS Adrian Cockcroft

  18. 18.

    Product Management UX Developers QA DB Admins Sys Admins Net

    Admins SAN Admins
  19. 19.

    Microservice Microservice Datastore Datastore Microservice Datastore Microservice

  20. 20.

    Microservice Microservice Datastore Datastore Microservice Datastore Microservice

  21. 21.

    INTEGRATION

  22. 22.
    None
  23. 23.

    UI COMPOSITION ESI / SSI / AJAX / IFRAME

  24. 24.

    COMPOXURE MIDDLEWARE FOR EXPRESS

  25. 25.
    None
  26. 26.

    <div> <p>Widget 1</p> </div> <div> <p>Widget Two</p> <div cx-url='{{server:local}}/application/component1'></div> </div>

    <body> <div cx-url='{{server:local}}/application/component2'></div> </body> <body> <div cx-url='{{server:local}}/application/component2'> <div> <p>Widget Two</p> <div cx-url='{{server:local}}/application/component1'> <div> <p>Widget 1</p> </div> </div> </div> </div> </body>
  27. 27.

    <div cx-url='{{server:local}}/application/widget' cx-cache-ttl='10s' cx-no-cache="\{{cookie:userId}}==={{authorId}}" cx-cache-key='widget:user:{{cookie:userId}}' cx-timeout='1s' cx-statsd-key=„widget_user"> This content won't

    be cached if the user is the author of the widget </div> <div cx-url='{{server:local}}/application/widget' cx-cache-ttl='10s' cx-cache-key='widget:user:{{cookie:userId}}' cx-timeout='1s' cx-statsd-key="widget_user"> This content will be replaced on the way through </div>
  28. 28.

    API GATEWAY

  29. 29.

    API Gateway Microservice Datastore Microservice Datastore Microservice Datastore

  30. 30.

    BACKEND FOR FRONTEND

  31. 31.

    STRUCTURING

  32. 32.
    None
  33. 33.

    TOOLING CONFIGURATION DISCOVERY ROUTING OBSERVABILITY DATASTORES OPERATIONS DEVELOPMENT POLICY

  34. 34.

    TOOLING Docker Spinnaker CONFIGURATION Archaius Habitat DISCOVERY Zookeeper Consul ROUTING

    Compose
 Linkerd OBSERVABILITY Zipkin Histrix DATASTORES SQL
 NoSQL OPERATIONS Mesos
 Kubernetes DEVELOPMENT Docker Hub
 Artifactory POLICY Security and arch compliance
  35. 35.

    YOU NEED A SKELETON

  36. 36.

    THERE AIN’T NO SUCH THING AS A FREE LUNCH MILTON

    FRIEDMAN
  37. 37.

    DISTRIBUTED COMPLEXITY

  38. 38.
    None
  39. 39.

    DISTRIBUTED LOGGING

  40. 40.

    EVENTUAL CONSISTENCY

  41. 41.

    ONE SERVICE MAY RUIN EVERYTHING

  42. 42.

    Microservice Microservice Datastore Datastore Microservice Datastore Microservice Timeout Budget Failed

    request Failed request OK request
  43. 43.

    $factory = new Ejsmont\CircuitBreaker\Factory(); $circuitBreaker = $factory->getSingleApcInstance(30, 300); $userProfile =

    null; 
 if( $circuitBreaker->isAvailable("UserProfileService") ){ try{ $userProfile = $userProfileService->loadProfileOrWhatever(); $circuitBreaker->reportSuccess("UserProfileService"); }catch( UserProfileServiceConnectionException $e ){ // network failed - report it as failure $circuitBreaker->reportFailure("UserProfileService"); }catch( Exception $e ){ // something went wrong but it is not service's fault, // dont report as failure } } if( $userProfile === null ){ // for example, show 'System maintenance, you cant login now.' message // but still let people buy as logged out customers. }
  44. 44.

    ARE MICROSERVICES FOR ME…?

  45. 45.
    None
  46. 46.
    None
  47. 47.

    MICROSERVICES Go micro with THANKS! mariuszgil