LazyGuard
Optimizing Performance vs. Domain Separation: How to Choose between Two Alternatives
So the flow will be like this :
BFF --> A : have the classification. Note that A needs also to call service C to get some information
BFF --> B, endpoint 1 : generating the tracing-id
BFF --> B endpoint 2: printing
I fear it's a lot
35 replies
Optimizing Performance vs. Domain Separation: How to Choose between Two Alternatives
The point is that, what if a user looses the first printed label, he or she may want to re-print. If generating the tracing number and printing it is aggregted in a single endpoint, how we will manage a second print ?
35 replies
Optimizing Performance vs. Domain Separation: How to Choose between Two Alternatives
but for option 2. It depends.
It can be :
User -> BFF -> A, BFF -> B, BFF -> Printing (the printing is done implicitly when BFF calls B, B generates and prints. A single call )
Or
User -> BFF -> A, BFF -> B, BFF (generating the tracing number) -> B, BFF (printing)
35 replies
Optimizing Performance vs. Domain Separation: How to Choose between Two Alternatives
For the point 2. Unfortanetly, it's a organization decision. Architectures decided to do microservices :/ So I am trying to find tricks to improve performance and reduce failures that will block the whole users' worflow
35 replies
Optimizing Performance vs. Domain Separation: How to Choose between Two Alternatives
For the point 1., no it's not possible. Users have dozens of documents to treat every day. A user cannot move to the next document unless the label with the tracing number is printed.
35 replies
Optimizing Performance vs. Domain Separation: How to Choose between Two Alternatives
Right now, this is how it’s being done, but assuming we move it, we’ll then have a tracing-number resource with a POST endpoint to generate one, and a separate endpoint to print it. Does that sound correct?
35 replies
Which Architecture to Choose?
@reacher I see, that's waht I am saying. Here the main aim is to desynchronize POST requests and procesing needed for each request. The desynchronization can be perfectly done using an in-process tool, no need for kafka whatsoever. The lead dev is not convinced :/
52 replies