SpringCloud
SpringCloud
-----------------
Spring Cloud Bus links nodes of a distributed system with a lightweight message
broker. This can then be used to broadcast state
changes (e.g. configuration changes) or other management instructions. The only
implementation currently is with an AMQP broker as
the transport, but the same basic feature set (and some more depending on the
transport) is on the roadmap for other transports.
As an application moves through the deployment pipeline from dev to test and into
production you can manage the configuration between
those environments and be certain that applications have everything they need to
run when they migrate.
The default implementation of the server storage backend uses git so it easily
supports labelled versions of configuration environments,
as well as being accessible to a wide range of tooling for managing the content.
It is easy to add alternative implementations and plug
them in with Spring configuration.
https://cloud.spring.io/spring-cloud-config/
Spring Cloud Contract Verifier is a tool that enables Consumer Driven Contract
(CDC) development of JVM-based applications. It is shipped with Contract Definition
Language (DSL) written in Groovy. Stating with version 1.1.0 you can define your
own way of defining contracts - the only thing you have to provide is a converter.
Contract definitions are used to produce following resources:
by default JSON stub definitions to be used by WireMock (HTTP Server Stub) when
doing integration testing on the client code (client tests). Test code must still
be written by hand, test data is produced by Spring Cloud Contract Verifier.
Starting with version 1.1.0 you can provide your own implementation of the HTTP
Server Stub.
Messaging routes if you’re using one. We’re integrating with Spring Integration,
Spring Cloud Stream and Apache Camel. You can however set your own integrations if
you want to.
Spring Cloud Contract Verifier moves TDD to the level of software architecture.