meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
microservices_architecture:frontend_integration_strategies_comparison [2019/08/27 11:39] – created Antonio Robirosamicroservices_architecture:frontend_integration_strategies_comparison [2019/12/18 19:44] (current) – external edit 127.0.0.1
Line 12: Line 12:
     * [[https://www.slideshare.net/ArifWider/a-highperformance-solution-to-microservice-ui-composition-xconf-hamburg|UI Fragment Composition (slides 13 and 14):]] Each microservice delivers html parts and a thin assembly layer puts them together. Each team is not only resposible for the backend microservices but also for delivering the html fragments     * [[https://www.slideshare.net/ArifWider/a-highperformance-solution-to-microservice-ui-composition-xconf-hamburg|UI Fragment Composition (slides 13 and 14):]] Each microservice delivers html parts and a thin assembly layer puts them together. Each team is not only resposible for the backend microservices but also for delivering the html fragments
  
-{{:images:article_files:mcroservices_frontend_integration_strategies_comparison.jpg|Gateway API, API Composition, UI-Fragment Integration and Backends for Frontends Strategies}}Explanation of the frontend integration strategies+{{:microservices_architecture:mcroservices_frontend_integration_strategies_comparison.jpg|Gateway API, API Composition, UI-Fragment Integration and Backends for Frontends Strategies}}Explanation of the frontend integration strategies
  
 +{{ :microservices_architecture:mcroservices_frontend_integration_strategies_comparison.dia|Original DIA file}}
 ===== Comparison ====== ===== Comparison ======
  
-|**Aspect**|**API Composition**|**Gateway API**|**Backends for Frontends**|**UI-Fragment Composition**| +^ Aspect                                                                                                                     ^ API Composition  ^ Gateway API        ^ Backends for Frontends  ^ UI-Fragment Composition  ^ 
-|Is an assembly or aggregation layer required?|No|Yes|Yes|Yes| +| Is an assembly or aggregation layer required?                                                                              | No               | Yes                | Yes                     | Yes                      | 
-|Where is done the cross-bounded-contexts coordination between microservices?|UI|Aggregation Layer|Aggregation Layer|Backend Microservices| +| Where is done the cross-bounded-contexts coordination between microservices?                                               | UI               | Aggregation Layer  | Aggregation Layer       | Backend Microservices    | 
-|Can the aggregation layer take on logic?|No|Yes|Yes|No| +| Can the aggregation layer take on logic?                                                                                   | No               | Yes                | Yes                     | No                       | 
-|Ability to tailor responses for desktops, mobile and wearable devices? For example, to return a product with a few fields|Little|High|High|Little| +| Ability to tailor responses for desktops, mobile and wearable devices? For example, to return a product with a few fields  | Little           | High               | High                    | Little                   | 
-|Has the ability to serve native apps or thick clients which don't understand html?|Yes|Yes|Yes|No| +| Has the ability to serve native apps or thick clients which don't understand html?                                         | Yes              | Yes                | Yes                     | No                       | 
-|Does the communication with the backend require lots of calls?|Yes|No|No|No| +| Does the communication with the backend require lots of calls?                                                             | Yes              | No                 | No                      | No                       | 
-|Is the UI team always the creator of the backend microservices?|No|No|No|Yes| +| Is the UI team always the creator of the backend microservices?                                                            | No               | No                 | No                      | Yes                      | 
-|Do small changes require requests to multiple teams if each team is responsible for one microservice?|Yes|Yes|Yes|No| +| Do small changes require requests to multiple teams if each team is responsible for one microservice?                      | Yes              | Yes                | Yes                     | No                       | 
-|Is easy to ensure the consistency of the user experience?|Yes|Yes|Yes|No| +| Is easy to ensure the consistency of the user experience?                                                                  | Yes              | Yes                | Yes                     | No                       | 
-|Are bounded-context-crossing features like autosuggestions from the last orders of the customer easy to implement?|No|Yes|Yes|No|+| Are bounded-context-crossing features like autosuggestions from the last orders of the customer easy to implement?         | No               | Yes                | Yes                     | No                       |
  
 Source: [[https://www.nginx.com/wp-content/uploads/2015/01/Building_Microservices_Nginx.pdf|"Building Microservices", Sam Newman, page 51-61]] Source: [[https://www.nginx.com/wp-content/uploads/2015/01/Building_Microservices_Nginx.pdf|"Building Microservices", Sam Newman, page 51-61]]