In this talk, I will discuss the evolution of frontend architecture – from monolith software which consist of backend and front end together (e.g. PHP generating JS/HTML), to separation of concerns (use of APIs, micro services etc). In addition, I will discuss about how different type of architectures and patterns can match to the growth of teams and different organisation cultures. This effects the efficiency of teams, and the quality of the code.
2. Evolution and history (monolith software to separation) – why?
3. Patterns and architecture according to team sizes, growth and organisational culture + examples.
Management choose architecture and patterns are normally based on product type. However, team sizes should be another main concern when it comes to such decisions.