I seek currently for the Redux core pattern. I have found some very interesting hint and now I wonder if the Model-View-ViewModel pattern could have inspired the Redux library ?
Thanks
Nope. Redux is primarily inspired by the original Flux Architecture, Elm, and some bits of CQRS / Event Sourcing. See the Prior Art page in the Redux docs for a list of inspirations, as well as the "Thanks" paragraph in the README.
Related
I was referring to the Axon documentation trying to implement a Saga: https://docs.axoniq.io/reference-guide/axon-framework/sagas/implementation
As is the case with everything else I've encountered thus far in Axon's documentation I could see no big picture, no diagrams or code examples or even any reference to example code in Github to help me get started.
I know what Saga means conceptually and what it solves. What I'm unable to understand from the documentation is how to apply that concept using Axon's artifacts. There is not one area that is written holistically and completely.
Does anyone have any good reference, books that helps me apply Axon? I'm currently evaluating Axon (and I'm not willing to buy the "support") and the quality of the documentation has almost forced me to look elsewhere (Eventuate).
I wrote this blog about Saga's with code samples I hope this helps you to get started.
Next to the blog that Yvonne has shared, you could take a look at this book from Vijay Nair:
https://www.amazon.com/Practical-Domain-Driven-Design-Enterprise-Java/dp/1484245423
It explains several approaches towards building DDD applications, with the last one diving into Axon's idea of it.
Added, AxonIQ is working on a training environment:
https://academy.axoniq.io/
So, a website with videos and written material about anything Axon-related.
The two courses that are on there right now, are free. Granted, Saga's/Process Manager aren't present there yet, although they should come soon.
When it comes to sample applications using Axon (that are maintained by AxonIQ developers), I'd refer to these:
https://github.com/AxonIQ/hotel-demo -> complete application touching as much of Axon's components as possible
https://github.com/AxonIQ/code-samples -> repository containing more fine-grained samples
https://github.com/fraktalio -> contains several sample projects, of which I'd recommend the restaurant, order, and courier demos
Apart from sharing the info, I am sad to hear you find the Reference Guide lacking at this stage. Any recommendations on improvements are from your current description, rather vague to be honest. If you have the time and interest to enhance this open source product, know you can always open some issue for the guide too. I am not asking you to write the documentation, but a description of the missed would be much appreciated.
https://github.com/AxonIQ/reference-guide
Which one should I use? For more context I use redux-toolkit. Advices to help understand which tool fits better are appreciated
The Redux Styleguide very clearly recommends thunks over slices for most asynchronous logic. If you have very complex and intertwined logic, sagas might make sense, but most applications don't have that kind of logic.
Also, you should probably try out using RTK-Query which would reduce your need for either middleware for asynchronous tasks quite a bit.
i want to using state management in my angular8 application , before do it i research about state management libraries seems NGRX and NGXS and akita.
But I'm confused as to which one to choose !
NGRS most used.
NGXS are more possibilities and easy to learning.
AKITA less used and less download according to npm download history and github forked and issue but it base on object oriented and is easy to learning.
whats is your choise? Please state your reason !
NGRX: functional approach, well maintain, difficult to adapt due to high boilerplate.
AKITA: new to community, one of good thing about akita is independent of framework can be use with VUE,REDUX.
NGXS: OOP approach, can easily adapt due to less boilerplate.
i am working on angular form it's birth, i started with ngrx, than i switch to ngxs due to easily adaptation.
I am using Weld to observe events. I thought there was a way to specify if the observer was asynchronous or not, but I am not finding that annotation or documentation.
Can observers be asynchronous, if so, what do I need to do to make that happen?
There is an open request for this: CDI-31: Asynchronous events.
Depending on your requirements, you can, as indicated in your comment, set a different transactional observer: If you use AFTER_COMPLETION or AFTER_SUCCESS, it should seem to your application like an asynchronous execution. However until a framework solves , I have just found an example using JMS for asynchronous execution in CDI.
Take a look at post on Piotr Nowicki's blog http://piotrnowicki.com/2013/05/asynchronous-cdi-events/
He described a couple of methods for achieving asynchronous behavior of CDI events.
If you guys want to see this happen, you'll need to head over the the link provided in Kariem's answer and voice your opinion. It seems the expert group is unwilling to consider adding async events because they consider it bloating the spec.
Honestly, Guice manages to offer this feature, and it remains lightweight, so I find the argument against this little counter-intuitive. Nevertheless, if you want to see this feature, head to the link, voice your opinion.
-Jonathan
Me again.. I hear the phrase 'decorating / decorate' a method being thrown about a lot in tutorials I have read / watched. But I just don't understand what it means AND what it actually does?? Can anyone point me in the direction of some information on beginning to use them (Very novice tutorial would be good)
.NET does not have "decorators" but it does have attributes. Developers often use the word "decorate" to indicate the usage of attributes. Here is a good article explaining how they work and how to use them.
Take a look at this article for an introduction and tutorial.
To Decorate in .NET you use attributes which act as metadata that is available to you at runtime which helps describe the items in your code.
If your talking about the Decorator design pattern there is a very clear example on dofactory.com.
Hope this helps