Spring Boot & Spring Cloud on PAS- Nate Schutta (2/2) at SpringOne Tour Chicago

1. Works with Spring
Security and Steeltoe.io.

2. SSO service secures access to
applications and APIs on PCF.

3. Native authentication,
federated SSO, authorization.

4. Operators can use SAML to
configure authentication.

5. OAuth 2 secures the resources.

6. Developers select the authentication
method for application users.

7. Can be UAA or external
identity providers.

8. CredHub.

9. Centralized credential management.

10. API for storing, generating, and
retrieving credentials.

11. Supports credentials of
different types.

12. Strings, passwords, certificates,
keypairs, JSON objects.

13. Pluggable Hardware
Security Modules.

15. Java Buildpack!

16. Immutable Infrastructure.

17. Build Containers from a
single control point.

18. Improved JVM memory calculation,
resulting in fewer app terminations.

19. Improved JVM Out of
Memory Behavior.

20. Failures now include useful
troubleshooting data.

21. Uses standard Java memory flags.

22. Robust JRE/JVM
Framework options.

24. Buildpacks give enterprises a a
point of governance.

25. More responsibility falls on the
platform operators.

26. New Java version? No worries.

27. That heritage app needs a
different version? No problem.

28. New app wants to
push ahead? Great!

29. Need a custom setup for
certain apps? Tweak away!
https://docs.cloudfoundry.org/buildpacks/custom.html

30. Spring Cloud and
Spring Cloud Services.

31. Microservices aren’t,
in fact, a panacea.

33. Despite what some
developers may have said.

34. Turns out, we need a few things
to really make it work.

35. Need to maintain a healthy
micro(services)biome.

36. You’ll need service discovery,
circuit breaker, config servers…

37. Eureka, Hystrix and Spring
Cloud Config anyone?

38. SCS for PCF packages
server-side components.
https://docs.pivotal.io/spring-cloud-services/1-5/common/index.html

39. Makes them available as
services in the Marketplace.

41. Create instances on demand.

42. So you can just bind to them.

43. You don’t have to manage them.

44. Focus on building
your microservices.

45. SCS is a BOSH release.

46. Fully Cloud Foundry managed.

48. Service Registry for
Pivotal Cloud Foundry.
https://docs.pivotal.io/spring-cloud-services/
1-5/common/service-registry/index.html

49. Service
Registry
ConsumerProducer
1. register
3. connect
Service
RegistryService
RegistryService
Registry

50. Service Discovery pattern.

51. Where would you say your
service is located now?

52. Good luck doing that by hand.

53. Dynamic discovery FTW.

54. Client registers providing
metadata about itself.

55. Host and port.

56. Registry expects a regular
heartbeat message.

57. Heartbeat fails? Service Registry
removes that instance.

58. Based on Eureka.
https://github.com/Netflix/eureka

60. Circuit Breaker Dashboard.
https://docs.pivotal.io/spring-cloud-services/
1-5/common/circuit-breaker/index.html

61. Closed
on call / pass through
call succeeds / reset count
call fails / count failure
threshold reached / trip
breaker
Half-Open
on call / pass through
call succeeds / reset
call fails / trip breaker
Open
on call / fail
on timeout / attempt reset
trip
breaker
reset
trip
breaker

62. Our services do not live alone.

63. In fact by themselves they
probably can’t do much.

64. We don’t want failures cascading
up to the user now do we?

65. Services will fail.

66. Failures, uh, find a way.

67. Awfully useful to have some
fallback behavior.

68. Circuit breaker watches the calls.

69. Once they exceed a failure
threshold, the circuit is opened.

70. Redirects to the
fallback mechanism.

71. Periodically checks to see if the
service is repaired.

72. If so, circuit is closed.

73. Based on Hystrix.
https://github.com/Netflix/Hystrix

75. Config Server for
Pivotal Cloud Foundry
https://docs.pivotal.io/spring-cloud-services/1-5/common/config-server/index.html

76. app C
greeting: hi
app B
greeting: hi
app A
greeting: hi
Config Server
2. Source config
1. Push config
1. Pull config
Hashicorp Vault
Git Source Repos
greeting: hi
2. API keys, secrets
Dev Desktop

77. We’re going to make updates.

78. Who likes downtime?

79. Just for a configuration change?

80. Externalized application
configuration service.

81. Central place to manage an
application’s external properties.

82. Manage the configuration
between environments.

83. Supports labelled versions of
environment-specific configurations.

84. Wide range of tooling for
managing the content.

85. Default implementation of the
server storage backend uses Git.

86. HashiCorp Vault is also supported.

87. Spring Boot Actuator
adds refresh endpoints.

88. Refreshes any bean annotated
with @RefreshScope.

89. Based on Spring
Cloud Config Server.
http://cloud.spring.io/spring-cloud-config/spring-
cloud-config.html#_spring_cloud_config_server

90. That’s not all, act now…

91. Microservices encourage change.

92. Always Be Changing.

93. Spring, Spring Boot and Spring
Cloud enable us to to that!

94. But we have to get that
code to production.

95. Deployments cannot be a
one off thing anymore.

96. Deploy early, deploy often!

97. https://mobile.twitter.com/ntschutta/status/938109379995353088

98. How do we move fast safely?

99. We need a well worn
path to production.

100. Repeatable.

101. Deployment pipelines.

102. Pipelines are critical for velocity.

103. We all know we should have them.

104. But it can be a real pain to
create them #amiright?

105. How many times have you built
a pipeline from scratch?

106. Traditionally they’ve been
bespoke, artisanal.

107. #

108. Wait. I’ve seen this movie before…

109. Much as there is a better
way to infrastructure…

110. Spring Cloud Pipelines.
https://cloud.spring.io/spring-cloud-pipelines/

111. Best practices from
Pivotal’s experience.

112. Opinionated approach to pipelines.

113. Jumpstart your pipeline.

114. A template for your pipeline.

115. Set of editable bash scripts.

116. Concourse, Jenkins.

117. Can target PAS or PKS.

118. Monitoring.

119. Monitoring is critical.

120. Especially when you’re
using microservices.

121. Of course when calls bounce
between 20 services…

122. Where is the problem?

123. Who do you page?

124. Spring Cloud Sleuth.
https://cloud.spring.io/spring-cloud-sleuth/single/spring-cloud-sleuth.html

125. Distributed tracing
for Spring Cloud.

126. Just add the dependency.

127. Borrows heavily from
Dapper, Zipkin and HTrace.

128. An abstraction over common
distributed tracing data models.

129. Instruments common ingress &
egress points for Spring apps.

130. Largely invisible to users.

131. Data can be captured in logs or
sent to remote collectors.

132. PCF Metrics.
https://pivotal.io/platform/services-marketplace/
monitoring-metrics-and-logging/pcf-metrics

133. Out of the box support for
Spring Boot Actuator metrics.

134. Graphical displays of request
traffic through an app.

135. Visually correlated logs.

136. Container metrics, network
metrics, application events.

137. Logs. Trace explorer.

138. Spring Boot Actuator metrics.

139. Customizable.

141. Apps Manager.

142. Manage and observe
your applications.

143. Web based tool.

144. Visual interface for the
Cloud Foundry CLI.

145. Create and manage orgs.

146. Create, manage and delete spaces.

147. Scale apps. Bind services.
Manage environment variables.

148. View logs. Start and stop
apps. Delete apps.

149. Choose & edit service plans.
Rename & delete service instances.

150. Invite new users. Mange
roles. Delete users.

151. You can try all this today.

153. https://run.pivotal.io

154. Take the Fortune Teller
app for a spin!
https://github.com/Pivotal-Field-Engineering/fortune-teller-demo/

155. Want to know where
things are heading?

156. Product Roadmap Call.
roadmap-registration.cfapps.io

157. Good luck!

158. September 24–27, 2018
Washington DC
Gaylord, National Harbor Discount Code
S1P200_NSchutta
Register
Today &
Save!

159. Nathaniel T. Schutta
@ntschutta
ntschutta.io
Thanks!
I’m a Software
Architect,
Now What?
with Nate Shutta
Modeling for
Software
Architects
with Nate Shutta
Presentation
Patterns
with Neal Ford & Nate Schutta