You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During my research for our api changes I have notice that Magento uses sku to show specific product. With our concept of immutable codes we can use them for almost all of our entities. For customers we could use an email as unique identifier. This will increase cohesion between different applications and probably it will make life easier. Should we go this way?
It should be noted that this would introduce a bit more database overhead but I think it is worth it. Feels a lot better + safer to use UUIDs (or whatever you use for the code) to be used externally and auto incremented ids internally. 👍
@steffenbrem absolutely. But without making any benchmarks its hard to say anything particular about performance. Index on code should also help. But I guess we will probably go this way. Let just wait for some more feedback.
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in a week if no further activity occurs. Thank you for your contributions.
stalebot
added
the
Stale
Issues and PRs with no recent activity, about to be closed soon.
label
Feb 2, 2018
During my research for our api changes I have notice that Magento uses sku to show specific product. With our concept of immutable codes we can use them for almost all of our entities. For customers we could use an email as unique identifier. This will increase cohesion between different applications and probably it will make life easier. Should we go this way?
Check
catalogProductRepositoryV1
in Magento docs.The text was updated successfully, but these errors were encountered: