Vledic | Franco | faramburo

It was found that it is not lambda specific, this will also break it: ```scala val reserveItemsInstance: InteractionInstance = InteractionInstance.unsafeFrom( new ReserveItems { def apply(orderId: String, items: List[String]): Future[WebshopRecipeReflection.ReserveItemsOutput] =...

Also in Java interactions must be direct class instances, if they are a reference to other class members or to static attributes, the Interactionmanager can't access them

- Request span level (Kamon Tracing) - Recipe Instance level (X-Bakery-Intent: Recipe-Instance-Id:)

Hi @SemanticBeeng, supporting extensions or tooling for the actor system or the cluster is something we think is better to delegate to the user of Baker, since Akka is just...

In my opinion, the main 2 reasons you want a cluster is for scalability and resilience, if you don't require scalability (though you would almost get it by default because...

The Baker 3.0 documentation page (which we are working on right now) will have more about this :)

You are completely correct. Hence the recommendation is to configure journaling to use Cassandra. It is the store we've used for production systems and have worked great

please do @m13m ! I think Assen will agree :) do you have a suggestion on how to do it? or want one? xD

the using sbt-microsite is perfect, the only time I did it I took inspiration from cats and monocle libraries as well