Our account/user mockup we have a system API that has the basic
user
post
get
{id}
get
put
delete
While the experience API (currently only account/user related)
user
post
get
{id}
get
delete
/forgot password
put
/reset password
put
/update email
put
There will also be a an notification system api that will be called after the user actions are done.
For the process API I have a question on general design. Would it look like the following?
user
post
get
{id}
get
put
delete
notification
post
or
user
post
get
{id}
get
delete
/forgot password
put
/reset password
put
/update email
put
notification
/some endpoint
post
/some endpoint
post
or would it be something completely different?
The other dev and I working on this are very new to mule and still are unsure of the correct API design. Any tip or suggestions would be appreciated
Hi,
Please correct me if I understood it wrong.
You have two system API one for account/user and another for Notification email.
And both will be integrated with Process.
You Experience Layer also have a resource for update email with PUT method.
So it means you are manually sending email updates and not implicitly,
In that case you can go with the below process layer approach, with respect o your Experience API:
user
post
get
{id}
get
delete
/forgot password
put
/reset password
put
/update email
put
I don't find there is any use of the notification resource in 2nd approach with POST Method because any how the logic will be in the Process Layer.
Regards,
Abhishek Bathwal
