forked from microservices-patterns/ftgo-application
-
Notifications
You must be signed in to change notification settings - Fork 0
/
TODO.txt
67 lines (42 loc) · 1.68 KB
/
TODO.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
eventuate client
sync repo ignores interceptor
error handling ignores options interceptor
tram:
// TODO accidentally returned new Success() and message handler was fine
* mysql image
* logging of sending reply
* in-memory: sending message to channel with no subscribers = error?
* default channel mapping bean
* varags publish domain event
* channel mapping needs to be pushed to lowest-level - messageproducer, messageconsumer
* trameventspublisherconfiguration.class, // todo => tramdomaineventpublisherconfiguration?
exceptions during event delivery don't cause rollback of transaction that records duplicate?
sagas
* mysql image
* logging of sending reply
* logging of sagas actions
--------------------------------
ftgo - big
what functionality:
* Cancel ORder
* Revise order
CQRS:
* Order events,
* Other events
API Gateway
* composition
----
* separate schemas for the services
** tram needs to use an explicit schema
* actual create order request - stupid stuff right now: passing in prices.
** order request should have menuitemid and pricing - need to ask a service to price the order.
*** self (duplicate), ros (preparation - not pricing), rs (ok - except we discussed the need to offload), new orderpricingservice
** do we need to start at the beginning of ordering?? shopping cart?
** saga method throws exception, reported by kafkamessageprocessor, eventuatekafkaconsumer appears to have processed the record. what is the expected behavior??? who stops processing?
** define constants for channels, ?? kitchenservice
@transactional
ftgo - misc
* serialization of money
* jpa mapping of enum - e.g. orderstate as name rather than integer
misc
* need static checking of serializability