quick org architecture question :thinking:
quick org architecture question 
we have an agent console FE that talks to our agent console BE (works great)
now our team wants us to hit other internal teams' APIs directly instead of proxying through our main BE
example: call conversation service API to get whatsapp numbers (we need to filter this in FE cuz API return some redundent data as well), display in UI, then call our main BE when user wants to send a message to this number.
we have a session cookies that work across all internal services but i still gotta get each team to whitelist our domain/localhost for CORS, auto generate schema from their swagger docs etc..
feels like our FE is gonna become a service orchestrator instead of just rendering UI also we have mobile app coming on the way
is this normal in bigger orgs or should i push back for keeping everything through our main backend?
we have an agent console FE that talks to our agent console BE (works great)
now our team wants us to hit other internal teams' APIs directly instead of proxying through our main BE
example: call conversation service API to get whatsapp numbers (we need to filter this in FE cuz API return some redundent data as well), display in UI, then call our main BE when user wants to send a message to this number.
we have a session cookies that work across all internal services but i still gotta get each team to whitelist our domain/localhost for CORS, auto generate schema from their swagger docs etc..
feels like our FE is gonna become a service orchestrator instead of just rendering UI also we have mobile app coming on the way
is this normal in bigger orgs or should i push back for keeping everything through our main backend?
