almost all of these risks stem from the fact that so few people are trained on the request/response call flow. I once had a a program manager from KONG (now at Postman) say the 'front controller' pattern was specific to JAVA simply because he had no clue what handled the request/response handoff from the web server to the application (https://flic.kr/p/2ovxHUw).
And people do nopt understand the difference between call flow of single threaded api application patterns (REACTOR) vs multithreaded(PROACTOR) and how they vary.
The vast majority of people only understand API's from a FRONTEND/UI/UX perspective and have a limited understanding of HTTP protocol.
almost all of these risks stem from the fact that so few people are trained on the request/response call flow. I once had a a program manager from KONG (now at Postman) say the 'front controller' pattern was specific to JAVA simply because he had no clue what handled the request/response handoff from the web server to the application (https://flic.kr/p/2ovxHUw).
And people do nopt understand the difference between call flow of single threaded api application patterns (REACTOR) vs multithreaded(PROACTOR) and how they vary.
The vast majority of people only understand API's from a FRONTEND/UI/UX perspective and have a limited understanding of HTTP protocol.