spring-cloud | Develop distributed application services | Microservice library

I used systemd, it allows me to set any environment variable on service start.

1. place the executable jar and the application.properties in a folder, like /opt/ or /home//
2. sudo nano /etc/systemd/system/.service
3. Content:

You need to put @Configuration on top of FeignConfig which should make it work I believe.

You need to add this to the app config:

You are using an outdated API.

The annotation-based configuration model has been long deprecated in favor of functional programming model, so EnableBinding, StreamListener etc are on their way out.

For you case you can simply use Supplier with StreamBridge. See this section for more details. And then you can do programmatic start/stop binding using the available lifecycle features of spring-cloud-stream.

Now, that doesn't mean your other problem will be resolved, but without a full stack trace and sufficient detail (e.g., version of frameworks you are using) it is difficult to say.

Indeed this is not supported for functional programming model at the moment as it really violates a concept of microservices for which spring-cloud-stream was designed for, where one of the main principles is you do one thing and do it well without affecting others. And in your case (especially with sources) you have multiple microservices grouped together in a single JVM process, thus one service affecting another.

That said, feel free to raise an issue so we can consider adding this feature

Can you try excluding ribbon dependency as shown below

dockerfile was poorly constructed, also added main-class config for application in build.gradl.kt

It seems axon-tracing-spring-boot-starter is using OpenTracing. OpenTracing is a tracing library that was abandoned and it has never reached a GA/stable release. So even if there would be an easy way, I would not use OpenTracing in production, I would try to move away from it.

From version 3.0, Spring Cloud Sleuth has abstracted the tracer away and it supports multiple tracer implementations. By default it supports Brave which is a mature tracing library but Sleuth has support for OpenTelemetry as well (Sleuth-OTel). The OpenTelemetry support is incubating and it is not recommended to use in prod since OpenTelemetry Tracing is not entirely stable/GA yet for Java.

With this, your options are:

1. Add support to Axon for Brave
   This is what I would recommend, I would start with opening an issue for them
2. OpenTelemetry theoretically compatible with OpenTracing (check the OpenTelemetry docs)
   You might be able to use Sleuth-OTel and OpenTracing The problem with this is: OpenTracing is abandoned and never went GA, OpenTelemetry Java Tracing is not stable yet, Sleuth-OTel is not stable yet
3. You can implement OpenTracing support for Sleuth
   I think this is a bad idea, it is a lot of work and OpenTracing is abandoned and never went GA

You can use together Spring Boot and Spring Cloud packages. Spring Boot is just a preconfigured Spring Framework with some extra functionalities. It also uses library versions compatibile with each other. Spring Cloud is also the part of the Spring ecosystem, contains libraries that mostly used in cloud applications. In the background, these packages will pull all necessary Spring (and other) libraries into your project, as transitive dependencies. So you can use the generated pom/gradle, and add other dependencies. In this case Spring boot will be your core and cloud add extras.