Building Nanoservices with Java 8 and JavaEE 7
Microservices were yesterday. Now talk about nanoservices:
Stay tuned: Picoservices are around the corner! :-)
Thanks to foocafe.org for the invitation and perfect organization!
See you at Java EE Workshops at Munich Airport or on demand and in a location very near you: airhacks.io!
Ups, you have already make the joke of pico services ;-)
Posted by Jordi on September 03, 2014 at 08:32 AM CEST #
Great talk, Adam!
I agree with everything you said.
Posted by Mircea on September 03, 2014 at 10:56 AM CEST #
I have a question: what's the best way to deal with EJBs which need use a specific database for the caller/login?
I have an application where each group of logins has its own database. Now I'm using a custom produces to inject the DataSource in another POJO (it is created in each request/view scope). This Produces verifies the current login in the session and then return the specific data source.
But in Stateless EJB, how can I do this? Should I get the reference to data source in every method? Should I use Stateful?
Posted by Wesley on September 03, 2014 at 07:25 PM CEST #
According to stress testing, I think the real point here is to check data consistency after concurrently invoking bussiness logic methods. There could be some lock exceptions, but they are ok if state of system is consistent.
Posted by Peter on September 13, 2014 at 02:48 AM CEST #