Ask questions and see you on 15th December at 8pm CET: youtube.com/c/bienadam
Also check out the latest episode:
Please keep the questions as short and as concise as only possible. Feel free to ask multiple, shorter questions. I will also answer some questions in my "shorts" youtube.com/@bienadam/shorts between the shows.
Upcoming airhacks.tv events will also be announced at meetup.com/airhacks
New: The airhacks.tv discord server: discord.gg/airhacks
Time machine: 41st airhacks.tv from 7th August 2017:
"React over Angular? ...and WebStandards, JSR-375 and REST, Reactive Programming vs. CompletableFuture, Blocking @asynchronous calls, Interceptors with EntityManager, AMQP and data masses, To Framework Or Not To Framework, Unit Testing Primefaces, Multi-Threaded JAX-RS 2.0 Clients, Java EE "vs." .NET, Dynamic entities, Data encryption, Working offline with JPA, Sample Projects, Industry trends, Conferences and Co., Server Side Rendering with Java EE 7, Naming CRUD in BCE, Java 9 Logging interface, Generic REST client, React.js / Polymer examples, Session replication challenges"
👉 https://adambien.blog/roller/abien/entry/react_over_angular_reactive_programming
How do you manage transactions when you spawn threads(virtual/use of completable futures etc) in your code base? AFAIK transactions are per-thread and spawning a thread for whatever reason will detach from the transaction boundary.
Considering a Java application, potentially with MicroProfile, that needs to support multi-tenancy where each tenant (client) has a dedicated database, what approach would you recommend?
Specifically, should we pursue a 'one application instance per tenant database' model or a 'single shared application instance' that dynamically routes requests to the correct tenant database based on a tenant identifier in the incoming request? Do you know if panache/hibernate supports that?