Create a gist now

Instantly share code, notes, and snippets.

35thAirhacksQ&A.md
@vasouv
vasouv commented Jan 19, 2017

Hi Adam,

my question is about entity relationships in microservices. In a monolith, the entities have fields that refer to other entities via annotations and tables in the RDBMS. In microservices, let's say service A fetches the Users and service B fetches the Orders from separate databases. How do I handle the relationships in a simple CRUD scenario?

@chakib-mohamed

Hi Adam,

What do you think about the new reactive style of programming using reactive streams(RxJava, spring reactor, akka streams)? do you think that it has a place in entreprise applications and will be widely adopted? and can we reach currently the same goals using plain java ee with CompletableFutures and Executors?

Thanks

@jessefarinacci

Hello Adam, thank you for your assistance, your show is useful and fun!

I see in many of your examples on airhacks.tv that your JAX-RS services return a javax.ws.rs.core.Response directly instead of some @javax.xml.bind.annotation.XmlRootElement tagged @javax.persistence.Entity and thereby allow the Java EE container to perform the serialization for Content Negotiated response value (i.e. @javax.ws.rs.Produces({json, xml})) . I'm just curious if you have given up on XML entirely, and what is your experience in the field regarding JSON-only responses being required, and not having to work with XML. Even if it were true that it's generally only useful to provide JSON response, can you please describe any advantages of working with the Response directly and any disadvantages to allowing the Container to do the content negotiation and serialization?

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment