App using api to store stuff is a bit pointless … suggest rolling the database into the app, and using the api as a complex “FitToOwnPets” service or something that makes more sense as a separate api.
Then the app can consume that in the “new pet” flow to make sure you can be insured.
At that point we can stick something into a queue so that a micro service environment (container apps) can pick it up and process it.
Without something like this, the app -> api flow could easily be considered an anti pattern taking attention away from its main purpose being to demonstrate aad flows.
App using api to store stuff is a bit pointless … suggest rolling the database into the app, and using the api as a complex “FitToOwnPets” service or something that makes more sense as a separate api.
Then the app can consume that in the “new pet” flow to make sure you can be insured.
At that point we can stick something into a queue so that a micro service environment (container apps) can pick it up and process it.
Without something like this, the app -> api flow could easily be considered an anti pattern taking attention away from its main purpose being to demonstrate aad flows.