How to coordinate registration of a class with Kryo between two separate spring boot apps?
up vote
0
down vote
favorite
I have multiple spring boot apps, fronted by rest, and I want to speed up serialization between them. Each spring boot rest app has a class that should be the same, but they might be in different packages between the apps. The class might be located at org.example.app1.model.Foo in one app, and it might be at org.example.app2.data.model.Foo in the other app.
This class is not a simple pojo with simple fields, but some fields are other data model objects in our app. So, we are specifically talking about an object graph that gets passed around between spring boot apps in our architecture. I don't know if this is a very important detail for my question, but I want to make sure that this detail is known.
When I register the class for serialization/deserialization with Kryo, how can I ensure that I can send and receive this class via Kryo and make sure that these classes are understood across the various different spring boot services? I would prefer not to create a common module and share the data between them. After all, if they are microservices, they should have their own (separate) data classes.
spring-boot spring-restcontroller spring-rest kryo
asked Nov 19 at 0:40
Steve Storck
140110
add a comment |
up vote
0
down vote
favorite
I have multiple spring boot apps, fronted by rest, and I want to speed up serialization between them. Each spring boot rest app has a class that should be the same, but they might be in different packages between the apps. The class might be located at org.example.app1.model.Foo in one app, and it might be at org.example.app2.data.model.Foo in the other app.
This class is not a simple pojo with simple fields, but some fields are other data model objects in our app. So, we are specifically talking about an object graph that gets passed around between spring boot apps in our architecture. I don't know if this is a very important detail for my question, but I want to make sure that this detail is known.
When I register the class for serialization/deserialization with Kryo, how can I ensure that I can send and receive this class via Kryo and make sure that these classes are understood across the various different spring boot services? I would prefer not to create a common module and share the data between them. After all, if they are microservices, they should have their own (separate) data classes.
spring-boot spring-restcontroller spring-rest kryo
asked Nov 19 at 0:40
Steve Storck
140110
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have multiple spring boot apps, fronted by rest, and I want to speed up serialization between them. Each spring boot rest app has a class that should be the same, but they might be in different packages between the apps. The class might be located at org.example.app1.model.Foo in one app, and it might be at org.example.app2.data.model.Foo in the other app.
This class is not a simple pojo with simple fields, but some fields are other data model objects in our app. So, we are specifically talking about an object graph that gets passed around between spring boot apps in our architecture. I don't know if this is a very important detail for my question, but I want to make sure that this detail is known.
When I register the class for serialization/deserialization with Kryo, how can I ensure that I can send and receive this class via Kryo and make sure that these classes are understood across the various different spring boot services? I would prefer not to create a common module and share the data between them. After all, if they are microservices, they should have their own (separate) data classes.
spring-boot spring-restcontroller spring-rest kryo
asked Nov 19 at 0:40
Steve Storck
140110
I have multiple spring boot apps, fronted by rest, and I want to speed up serialization between them. Each spring boot rest app has a class that should be the same, but they might be in different packages between the apps. The class might be located at org.example.app1.model.Foo in one app, and it might be at org.example.app2.data.model.Foo in the other app.
This class is not a simple pojo with simple fields, but some fields are other data model objects in our app. So, we are specifically talking about an object graph that gets passed around between spring boot apps in our architecture. I don't know if this is a very important detail for my question, but I want to make sure that this detail is known.
When I register the class for serialization/deserialization with Kryo, how can I ensure that I can send and receive this class via Kryo and make sure that these classes are understood across the various different spring boot services? I would prefer not to create a common module and share the data between them. After all, if they are microservices, they should have their own (separate) data classes.
spring-boot spring-restcontroller spring-rest kryo
spring-boot spring-restcontroller spring-rest kryo
asked Nov 19 at 0:40
Steve Storck
140110
asked Nov 19 at 0:40
Steve Storck
140110
asked Nov 19 at 0:40
Steve Storck
140110
asked Nov 19 at 0:40
Steve Storck
140110
asked Nov 19 at 0:40
Steve Storck
140110
140110
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53366933%2fhow-to-coordinate-registration-of-a-class-with-kryo-between-two-separate-spring%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
