50. — Adam Wright
The prevailing mythology is you should
"containerize" everything and give it to a
container orchestrator to run, but why?
They had one problem, "Run an app". Now
they have two, "Run a container that runs
an app" and "maintain a container".
https://news.ycombinator.com/item?id=16332184
97. Of course you should also
leverage Spring Boot Actuator.
https://docs.spring.io/spring-boot/docs/current/
reference/html/production-ready-metrics.html
117. 1. One codebase in version control,
multiple deploys.
2. Explicitly define your dependencies.
3. Configuration must be separate from
the code.
4. Backing services are just attached
resources.
5. Build, release, run.
118. 6. Stateless - share nothing.
7. Export services via port binding.
8. Scale via process.
9. Start up fast, shut down gracefully.
10.Dev/Prod parity.
11.Logs as event streams.
12.Admin tasks run as one off
processes.
137. Profiles let you describe sets of
beans differently from env to env.
https://docs.spring.io/spring-boot/docs/current/
reference/html/boot-features-profiles.html
141. Bring CF service connection data
directly into your Spring Beans.
http://cloud.spring.io/spring-cloud-connectors/
spring-cloud-cloud-foundry-connector.html