In this blog post, we will describe how you could configure HashiCorp Vault in a Cloud Foundry environment. In Cloud Foundry developers provision service instances and then bind those service instances to an application. The service broker is responsible to provide those service instances by interacting with the Cloud Controller. The service brokers advertise a catalog of service offerings and service plans in the marketplace (e.g. a single node Vault plan or a clustered multinode Vault plan). They also act on requests from the marketplace for provisioning, binding, unbinding, and de-provisioning service instances.
Creating a batch-driven solution is pretty easy with Spring Batch. There is an excellent getting started guide on spring.io website, which explains the basics and provides example code how to start a batch job on application startup. However, batch jobs are typically executed as a result of an event. In this blog post, we are going to look how to trigger a Spring Batch job with a JMS message.
As we saw in the first part of this series, it is essential necessary to monitor the health of our microservices, and to improve the tool we developed which helps us get metrics and forward them to an Elasticsearch instance. In this chapter we will pursue the question of how can we improve the processing of the result of the metrics endpoint?