Re: Confusing entity names

+1 Taher > On 14-Apr-2018, at 12:40 PM, Taher Alkhateeb > wrote: > > Hi Everyone, > > Thinking some more about the concerns from multiple people in this thread > like Michael, Rajesh, Gil and others I have a different suggestion. > > Why not make a sweeping review

Re: HTTP based API using REST architectural style

Hello Paul, Paul Foxworthy writes: > This might be of interest too: > > https://martinfowler.com/articles/richardsonMaturityModel.html Thanks for the link. -- Mathieu Lirzin GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37

Re: Confusing entity names

Hi Everyone, Thinking some more about the concerns from multiple people in this thread like Michael, Rajesh, Gil and others I have a different suggestion. Why not make a sweeping review of the full domain model, and then decide on one comprehensive change, with even a migration script that we

Re: Confusing entity names

Suraj, I still do not see much value in this change, compared to the effort needed for development and testing as well as the migration the users have to do. Please consider to not do this change. Thanks, Michael Am 13.04.18 um 10:09 schrieb Suraj Khurana: Thanks everyone for your

Re: Check for only QOH while doing reservations

+1 Suraj I agree with Rishi, We should start another mail thread to discuss race condition. IMO, At the time of reservation, we should check for ATP instead of QOH(As Suraj suggest). Vaibhav Jain Sr. Enterprise Software Engineer HotWax Systems m: 782-834-1900 e: vaibhav.j...@hotwaxsystems.com