1. There should be more than just moving things… a microservice should be autonomous, and have it’s own database. It’s not even clear You want to use REST api to communicate between services, some may use Event bus, or pubsub.

2. It’s true put_flash has no use in case of JSON api.

It’s one of the case where I would choose an umbrella application.

Thank you so much. There are simply too many buzzwords and people just need to wade through all of them as they settle down and make serious stuff beyond simple tutorials and throwaway single-user applications.

Basically some background for you as you helped…

I was just confused about microservices and JSON API endpoints until I realize microservices are just the “end goal” while what I am doing building JSON API endpoints are actually part of achieving that. I doubt I am that adept to explore other less well documented patterns such as event bus and pubsub though I have heard good things about them

2. Thank you. I was so disconcerted that JSON APIs cant even use put_flash and I was thinking of a convoluted way such as a handoff mechanism between a JSON API and conventional HTML routes. But i figured that it is overly… complex. So Im using plain vanilla javascript to process JSON responses and display the errors.

I look forward to being of assistance to you should you should ever have questions more in the business domain and etc.

Everything is a fair game. Last I had to devise such an API on my own, I just did this:

{
  "errors": [
    {"username": "must be more than 3 characters"},
    {"password": "must include a special symbol"}
  ]
}

Not sure I understand your conundrum though. Do you seek general advice or particular Phoenix implementation techniques? If it’s the former, don’t bother. Do it the way you feel is right.