Our last projects—Twitter Consumers, Twitter Gathering, and Twitter Dispatcher—were excellent. We learned several exciting features, and they were implemented using the new features present in Spring 5.0. All of them are implemented in Reactive Streams and use Kotlin as the programming language. They are the hottest features in Spring 5.0; it was an impressive progression.
However, there are notably missing parts on these projects; we have microservice needs in mind. There are no infrastructure services such as service discovery, distributed configurations, API Gateway, distributed tracing, and monitoring. These kinds of services are mandatory in distributed systems such as microservice architectures.
There are several reasons for that. Firstly, we can think of the configuration management. Let's imagine the following scenario –...
