Magento Multi Source Inventory, 19 Jan 2018

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Magento MSI Open Demo. January 19, 2018

Description

Agenda:
- @iminiailo - module InventoryIndexer introduced, indexation mechanism improvements
- @roma-glushko / @iminiailo - Make stock source link part of API (this PR unblocks by priority algorithm and return processing)
- @Yaroslav Rogoza / @vnayda - Status of `Low Stock Notification`

A

Okay, guys, let's start so.

A

On previous demo, I will show you several prototypes and the proof of concept regarding some of the functionality, for example, catalog search and the work with a shopping cart. During this week, we spent quite a lot of time to make this prototypes mmm said to be unsatisfied for our guidelines and the code code requirements we have internally in magenta. That's why we have quite a lot of technical stories during period technical stories and cost during the current week during the current sprint. Actually, so, according to today's agenda, we will start from from the first subject.

A

We would like to present you that module inventory index here has been introduced. You probably know that we've made quite a lot of changes for the inventory indexation, because our indication is pretty typical.

A

We already got an approval from our counter owner from our intern, that we will update source item always with an update on safe mode, and we would not support update by schedule because actually, our reservation placement and the work with the inventory is a synchronous by its nature. So even update, update by update on save, is also a synchronous operation. So we no need, additionally, to support update by schedules that would be just confusing and actually making a refactoring of that indexation code and the older code devoted for the indexation.

A

We decided to introduce a new module and actually the name of that module is venturi indexer and now we place all that code to to that module and actually that's very good, so we aligned with that decision with our basic architectural concept we have in magenta.

A

We raise that question several times regarding similar cases with Anton krill and actually that's really cool when it has the index in there in a separate module, because the indexation as well as it's pretty similar like with the cache is, should not be in the same entity and actually entity should know nothing that it's being cached or in the indexed, because this is just a supplementary work just to speed up speed up the whole process. That's why actually we introduced this in inventory, indexer model and potentially inventory indexer is also switchable module.

A

So potentially we can run the system without inventory index here. So this is pretty good from the modularity point of view. As well as it's pretty good from from that, we don't have a lot of dependencies and our system is like could be built on top of basic layer. It could be extensible and it could be some additional complexity could be introduced along the way that actually was the main decision and let's improve the code quality.

A

So we already have that module inventory individual in our code base and actually the main responsibility and re-index here, and you probably already aware that we have multi dimensional index because we have several dimension by by means of which we need to invalidate our index, so that all of this logic will be right there, it's actually over any place.

A

So this is the first update. The second one would be presented by Roman Google score from ethics, so he will show the introduction of the source link as the part of the API. So probably the name of the story sounds little bit technical, but I. Believe Rahman will describe you in more detail. The business idea behind the technical story, so Ramon feel free to share your screen.

B

And let me share my screen and I'm gonna show you a couple of interfaces that will changed our domain model a little bit so here before I would say that a couple of weeks I was working on this foodie quest and now it's almost complete yeah and you know before this changes, our stock stock source links was or were under the fruit of the module and I was a kind of implementation details, but now they need to be reflected in the domain model because of information.

B

They are stored on their level and we decided to store in the stock source links information regarding the validity of exactly the links that link foreign source stockin source. So yeah. That's why we need we need to introduce a new entity so yeah, that's interface, related to this entity data model. We introduced it in in the inventory, API module and also introduced a couple more interface related to managing this.

B

This entity, which which are remove interface, say interface and get these interfaces as so yeah, and we also reflected all code that related to using the legacy legacy, implementation of links and also we already factored legacy code in newly introduced inventory, indexer module so yeah and the next steps here is to introduce actually the priority and purity field to this entity and remove it from source a source entity. And then we will be able to unlock a couple of other tasks and most of them related to priority source selection, algorithm.

B

So yeah I, guess that's it from my side. You were correct me if I need something to it,.

A

Actually everything great Thank, You Ramon for your update I just want to mention that this story was really critical for us, and implementation of this story helped us to unblock two very important business business story, the first one as Ramon mentioned it was adding the priority because one or along with that, along with that story, we have other guys who have working lives on algorithms like Albany, which will be run at the time of the order processing and at the time of the order, processing we need to decide from which particular sources we need to make to fulfill the order, and actually we agreed with our product owner that in MVP version of the msi will just implement the the basic strategy and the basic strategy is supposed to be priority based your strategy.

A

So we have priorities of sources in the scope of this talk.

A

So, for example, if you have the German stock and we have sources responsible for the Berlin Munich and Hamburg, for example, we can decide that first of all, for example, if customer order the product product I, don't know, maybe it's laptop and we have the same laptop both on Berlin in Munich, we'll make a decision that this product to be delivered from Berlin, because the darling has a higher priority, and initially we had that priority on as a level of sources, but taking into account that the same source could be reusing the scope of different stocks.

A

We need to have that priority and the level of the source to stock link. That's actually why we decided to introduce this API, which Roman implemented, and we will use a priority. So the next task would be introducing the priority attribute to this link, so that will help us to implement the priority based algorithm. Another business story which unlocked you go.

C

A

That is pleasure. Having.

C

What you what you deserve, so it if you please, show me the API to create for swing a game. The the signature of the message, operation.

B

C

All things save so, ok that it can. You please show me stock source, link, interface interface. Yes sure you have here, you have spoke with the source code right and how how.

A

Its priority, as I mentioned, we have the next task introducing priority. So the priority is not ok, we will add the priority so and we will add this like a typical attribute, so we would not add it. As extension attribute, we decided to use this like a normal attribute here, so we belong that like it should attribute or again it won't be here, but priority would matter well.

C

Make sense only.

A

C

For priority said to generate actually.

A

We will use priority for another business story, so we have business case that, for example, for the RMA, a very strong. We also need to make a decision to which source we will return, so we will have will have the actually will make a return to that the most to the stores with the biggest priority as well. So why.

C

Not let the merchant make a decision where, because MVP.

A

Part will have interface. We will introduce the one to that interface. We share the name of the interface from free get get like gets source for the return based on the stock ID provided and based on that we will return the source ID in our default implementation, because it's, the MVP we will return I, will make a decision based on the biggest highest priority. Okay,.

C

But again, even for MMA like in that's something we should take a fun. In my opinion, we should give the decision should be made by merchant not automatically, but even if it may, if made automatically.

C

If you want to support multiple different strategies, priority would be, would only make sense for priority set G both for fulfillment and for returns. Right, because if.

D

C

For example, distance distance mataji, we would be- would ignore priority right.

A

I don't know yet, maybe maybe it would be because, for example, if you have the same distance or it depends, it depends how we will implement the distance strategy.

C

A

Even if we help same distance, we we need to make a decision. Some, yes,.

C

That's what I'm trying to say do you already have a design for strategy? Yes,.

A

Lee we had the design, it was documented. Like quite quite a long ago. I mean it's still, actually, no actually so the main idea. So initially we want to just want to say they regard ins a priority, so the initial idea was to implement it at the extension attribute, but taking into account the performance aspect and also because we will use the priority, at least in the MVP part. Quite quite a lot. We decided to edit as a as a default default attribute.

C

Here and type the word situation when when, for example, priority strategy one in one year, we have multiple strategies and the strategy with special fields in source links, and the reason is that, because it's historically you.

A

Know actually, priority could be admitted just for making a sorting, okay.

C

Okay, let's, let's, let's do let's well I, suggest that do separate meeting to discuss design for strategies not to take a lot of fun here. Okay,.

A

I actually just want to mention that we have free casino principle, with the priority for the product to category link where we have the category ad process queue and the priority, and there, for example, use it for nurturing yeah.

C

I understand that there are multiple users, but what I'm trying to understand I'm trying which is I'm trying to make sure that we have clear vision? How movie.

D

C

Just introduce it because.

D

C

Might use it later, so the separate design meeting already have one in a week, so we.

A

Can add it as a one bullet for that jump.

A

We have a dedicated meeting yeah.

C

I might want to join.

A

Okay, so that was really really important, think and thank you very much for a month for you update, so you feel that that this topic is very interesting and the our lead architect pay attention on it. This actually just.

D

Underlines how important.

A

Your work, which you contribute in this pull request so.

B

You're welcome and happy to say that I'm on my way to to to merge this changes yet to complete or fixes. So um thank you.

A

The next one gonna be Yaroslav, I, don't see your Slav on the meeting but as I know, aerosol sent the video to Valerie and the Valerie will make. A presentation also will highlight that video, which she also recorded for this particular meeting.

E

Hello guys, unfortunately, eres law does not have visibility to visit our demo, but he provides with your record and I will share with you.

D

D

Different sources, so, if we have far along star configuration, we have.

D

E

Sorry guys I forgot to share my steam.

E

D

Hello s so we're gonna smoke.

D

I presented them, Carlos, don't know the source library and we have further web studies from different sources. So we have our stock configuration that is higher for some Model T that then their product that will show this product. This will sell the previous week. It was initial, like implementation of this fictional I'll teach, and this week we already have working filters, so we came through and also we have to the meeting to filter by source code using the drop-down represented all other sources in the system. At the moment also, we have finished the export functionality.

D

We can export the grid values in two formats.

D

So we can see that we have.

D

And if we open it, for example, in Excel, we will see that we have of odd numbers of columns at current levels. Here.

E

Thank you, you know whoops, like we close to finish this story. We have a few tasks related to some technical improvements like model renaming like providing some refactoring collection. So on and a fishnet reveal was this story. Your I stopped share, must feel and mood and disable. My sound.

A

A

Let me share my screen as well.

A

Let's go to the.

A

The roadmap, so on a previous demo, we show you several stories and because we didn't have our product owner mark, we agreed that we will think him and ask whether we can close this story. So currently we are talking about add the short delivery awareness.

A

That sort of delivery awareness to order page, so it was shown previously, and we agreed that we can close it. So I will close this story right after this demo and run full selection algorithm by request on order page. This story also has been presented and we get an approval that we can close it. So I will close both of the story right after this demo and we'll update the amount of studies and make.

C

Sure to close ethics and epics.

A

So stories, okay,.

A

Okay, so is there any other open questions? Maybe some of the meeting participants. We would like to ask us something or.

A

By the way, actually I have a question so actually the question Anton Creole if I have time and you're still on a meeting. Yes.

C

A

Actually, it's pretty typical stuff like that. We can update in there several threats some entity and, for example, like to Edmonds work in parallel in parallel, can update the same entity and while admin one is still working on like an entity, form admin to can already make it persistence and when the admin one makes a decision to to save the form as well. Actually he will just overwrite already existent data, and we don't have like, in a general case of general solution for this case, but actually, in our case this.

A

This could be a real big issue, because currently we are talking about the product update form and we because we are supporting coarse-grain api's and we save all the product dates. And currently, this inventory data is also part of the product data, but it shouldn't be probably in the ideal world but like, for example, if the admin making an update of the product form and the order is placed like simultaneously visit and even if the admin that updates a stock item quantity because he wanted just to make update of the media data for the product.

A

He will override existing data for for source items and actually the main idea and I hope that would be solved on the level of the UI RM, which will provide some kind of the kind of MVCC exertion of the entity and making making the persistent. We will see that we are in a state are but entity already in a state B. So we can just proceed with persistence because we are in our own state. But actually, ideally, we need to make.

A

We need to differentiate, inventory, update and the product data update, because currently we we can get to this to this problematic behavior for some merchants and we already have the github issue and actually this pub issue was opened and today we had a discussion with the maintainer. But so what do you see about this?.

C

As a problem, yes, I mean.

C

A

We need to align here on this or on track that or amiss actually will support this case like entity versioning and another stuff. Would who do you think regarding the separation inventory out of product so editing product? We, so we illusion here the coarse grain API so because the inventory would be like another API call and we can't like now save the inventory, along with the product data. Let's think it makes sense.

C

To separate a inventory from data and I would I would sacrifice this ability to create product identity in a k-hole to have separate inventory. It's not.

A

C

Rights are updated much more often than just.

A

Actually, the main point, but actually in this case we will need to reconsider our look and feel because currently it's on the same page on the inventory. Currently, so probably, we need to introduce a dedicated start with the inventory data and it should not be on the product product edit. That's important topic and I think it's being raised.

C

Sword or force time- let's finalize it, can you please set up a call between product owner me, unpopular, okay,.

A

Yeah actually I wanted to bring Anton Coppola to this conversation as well. Okay, cool so looks like that's all and thank you all for the participation and stay tuned and I will share this recording of this unique and very soon. Thank you very much mine.