Inventory & Assembly proposal #16
Conversation
doomspork
force-pushed
the
scallan-inventory-assembly
branch
from
a3bf893 to
f85d6ea
Compare
doomspork
force-pushed
the
scallan-inventory-assembly
branch
2 times, most recently
from
2e514ec to
01522c6
Compare
There was a problem hiding this comment.
I was thinking about how the split here is at BuildCreated and not OrderCreated and at first I was against it long term. But thinking about it, long term we would want to split out Fulfillment.Product to be able to keep track of each quantity independently for returns anyway. So this split makes more sense long term than what I was thinking.
|
|
||
| package bottle.inventory.events.v1; | ||
|
|
||
| message ComponentAvailabilityRequested { |
There was a problem hiding this comment.
Having a quantity request and change in queue seems weird to me, but I guess this makes sense with our current infrastructure. I know that aws elb support grpc if we want to start working with that for this project.
There was a problem hiding this comment.
This has felt meh to me as well. My thinking was they don't need to be synchronous so it didn't seem necessary to introduce a mechanism to achieve that when it isn't required.
(We discussed in Slack, we'll use this for now and circle back to this later)
doomspork
force-pushed
the
scallan-inventory-assembly
branch
from
b3abe34 to
e62e6c8
Compare
doomspork
force-pushed
the
scallan-inventory-assembly
branch
from
b3993c3 to
9111ba7
Compare
|
Thanks for the help @btkostner 🎉 |
This isn't complete, I'll expand on how these will be used later today 👍