Presented at GR8Conf US 2016 in Minneapolis, MN. You've got your microservices, cloud config & Eureka servers running in development, but how do you take that to production? A single instance of each isn't a viable solution for these critical services. In this talk, we'll walk through how to configure and run the cloud config and Eureka servers in a high availability manner. We will also cover other production tasks like pushing config updates and monitoring all your Hystrix circuit breakers using Turbine. This is not an introductory talk and assumes a basic familiarity with the Spring Cloud Services.

1. SPRING CLOUD INTO
PRODUCTION
TODD MILLER

2. SPRING CLOUD INTO PRODUCTION
ABOUT ME
Atlanta, GA
Inc 5000 fastest growing companies 5 years in a row
Forbes 25 Best Small Businesses 2016
Father of four
todd@zifty.com
@ziftytodd

3. Microservices are great…
until you realize all the other 💩
it takes to run them.
Todd Miller
SPRING CLOUD INTO PRODUCTION

4. SPRING INTO PRODUCTION
MICROSERVICE “TAX”
▸ Configuration Management
▸ Service Discovery
(and registration)
▸ More faults to handle
(and more gracefully)
▸ Authentication & Authorization
▸ and so on…

6. SPRING CLOUD INTO PRODUCTION
WHAT IS SPRING CLOUD?
▸ Config management
▸ Service discovery
▸ Circuit breakers
▸ Intelligent routing
▸ Micro-proxy
▸ Control bus
▸ One-time tokens
▸ Global locks
▸ Distributed sessions …. and more!

7. SPRING CLOUD INTO PRODUCTION
CONFIGURATION - SPRING CLOUD CONFIG
▸ Separate server service
▸ Keep config in a repository
▸ YAML or Properties files
▸ Supports multiple services and
profiles
▸ Super simple client
▸ One config line
▸ One dependency

8. SPRING CLOUD INTO PRODUCTION
SERVICE DISCOVERY - EUREKA
▸ Separate server service
▸ Service registry
▸ Clients register and discover
▸ Some fault tolerance
▸ Add Ribbon for intelligent routing

9. SPRING CLOUD INTO PRODUCTION
CIRCUIT BREAKERS - HYSTRIX
▸ Part of your service’s code
▸ Circuit breaker
▸ Failure isolation
▸ Graceful degradation
▸ Built-in monitoring
▸ Use with Turbine to aggregate

14. SPRING CLOUD INTO PRODUCTION
EC2 CONTAINER SERVICE (ECS)
▸ Manages containers & cluster
▸ Define tasks
▸ Compose tasks into services
▸ Load balancing
▸ Auto-scaling
▸ AWS’s Docker registry (ECR)

21. SPRING INTO PRODUCTION
CLOUD CONFIG INTO PRODUCTION
▸ Which comes first? Eureka or Config?
▸ How do you find the Config Server?
▸ Use an ELB to point to config server instances

22. SPRING CLOUD INTO PRODUCTION
Gr8ConfigApplication.groovy
bootstrap.yml
Dockerfile

23. SPRING INTO PRODUCTION

24. SPRING INTO PRODUCTION

25. SPRING INTO PRODUCTION

26. SPRING INTO PRODUCTION

27. SPRING CLOUD INTO PRODUCTION

28. SPRING CLOUD INTO PRODUCTION

29. SPRING CLOUD INTO PRODUCTION

30. SPRING CLOUD INTO PRODUCTION

31. SPRING CLOUD INTO PRODUCTION

32. SPRING CLOUD INTO PRODUCTION

33. SPRING CLOUD INTO PRODUCTION

34. SPRING CLOUD INTO PRODUCTION
IT RUNS!
▸ Access via ELB’s endpoint URL
▸ But who wants to remember a URL like this?
▸ Plus, it’s not very portable
▸ Enter AWS Route 53 and private DNS

35. SPRING CLOUD INTO PRODUCTION

36. SPRING CLOUD INTO PRODUCTION

37. SPRING CLOUD INTO PRODUCTION
IT RUNS BETTER!
▸ Any service in our VPC can access via
http://config.gr8conf.vpc:8888/
▸ Private hosted zones do not work from outside VPC access
▸ Use public DNS records if external access is needed

38. SPRING INTO PRODUCTION
EUREKA INTO PRODUCTION
▸ How do you find a server?
▸ How do servers find each other?
▸ Route53 and DNS to the rescue again

39. SPRING CLOUD INTO PRODUCTION
Gr8EurekaApplication.groovy

40. SPRING CLOUD INTO PRODUCTION
bootstrap.yml

41. SPRING CLOUD INTO PRODUCTION
eureka-server.yml

42. SPRING INTO PRODUCTION
ROUTE 53 FOR EUREKA
▸ TXT record per region to point to AZ in that region
txt.us-east-1.gr8conf.vpc ->
us-east-1d.gr8conf.vpc
us-east-1e.gr8conf.vpc
▸ TXT record per AZ in region
txt.us-east-1d.gr8conf.vpc ->
ec2-##-##-##-##.compute-1.amazonaws.com
ec2-##-##-##-##.compute-1.amazonaws.com

43. SPRING CLOUD INTO PRODUCTION

44. SPRING CLOUD INTO PRODUCTION

45. SPRING CLOUD INTO PRODUCTION
A FEW TRICKS
▸ List of EC2 instances must use the expanded EIP hostname
▸ Separated by spaces
▸ Space at start, and space at end
▸ Failure results in Eureka servers using wrong hostname
and not recognizing each other properly

46. SPRING CLOUD INTO PRODUCTION

47. SPRING CLOUD INTO PRODUCTION

48. SPRING CLOUD INTO PRODUCTION

49. SPRING CLOUD INTO PRODUCTION

50. SPRING CLOUD INTO PRODUCTION

51. SPRING CLOUD INTO PRODUCTION

52. SPRING CLOUD INTO PRODUCTION
HOW DO OUR SERVICES USE THIS?
▸ Point to config server ELB
▸ Store Eureka config details for clients in config server
▸ EurekaInstanceConfigBean has to happen on services too

53. SPRING CLOUD INTO PRODUCTION
Gr8ServiceApplication.groovy

54. SPRING CLOUD INTO PRODUCTION
Gr8Controller.groovy

55. SPRING CLOUD INTO PRODUCTION
bootstrap.yml

56. SPRING CLOUD INTO PRODUCTION
gr8service.yml

57. SPRING CLOUD INTO PRODUCTION
DEPLOY TO PRODUCTION
▸ Same as we’ve seen
▸ Push Docker image to ECR
▸ Create Task Definition
▸ Create Service
▸ Public facing? Use an ELB to get a reliable URL

58. SPRING CLOUD INTO PRODUCTION

59. SPRING CLOUD INTO PRODUCTION
HYSTRIX MONITORING
▸ Use Hystrix Dashboard

60. SPRING CLOUD INTO PRODUCTION

61. SPRING CLOUD INTO PRODUCTION
http://techblog.netflix.com/2012/12/hystrix-dashboard-and-turbine.html

62. SPRING CLOUD INTO PRODUCTION
HYSTRIX MONITORING FOR THEM ALL
▸ Start a Turbine server
▸ Finds services to get Hystrix streams via Eureka
▸ Need AMPQ broker

63. SPRING CLOUD INTO PRODUCTION
http://www.programering.com/a/MDN3gzNwATE.html

65. SPRING CLOUD INTO PRODUCTION
THANK YOU
▸ https://github.com/ziftytodd
▸ todd@zifty.com
▸ @ziftytodd
▸ www.zifty.com