Distributed React
Download as PPTX, PDF0 likes113 views
The document discusses the organization of front-end code using React in a complex environment with numerous distributed teams and microservices. It emphasizes the importance of separation of concerns and effective collaboration through React's architecture, allowing multiple developers to work on self-contained components. The presentation concludes with practical advice on maintaining common tools and build systems.
![Thank you!
Refreshments anyone?
#IBDevDays16
[:coffee, :juice, :water]
|> Stream.cycle
|> Stream.each(&IO.inspect/1)
|> Enum.filter(&(&1))](https://image.slidesharecdn.com/distributedreactdevdays2016-170524063119/85/Distributed-React-13-320.jpg)
Distributed React
- 1. React Time Or How I Learned to Stop Worrying and Love the Bomb React is a magnificent "new" platform that allows for a nice organization of front-end code. This is a story about organizing people and products using React.
- 2. The Problem portal.infobip.com 10+ modules 20+ teams 100+ microservices
- 3. Distributed teams, distributed code base, distributed deploy locations, distributed everything! How does one organize code when there are so many factors in the game?
- 4. Solution Embrace distributed! - Captain Obvious
- 6. Within web layer We cannot solve our problems with the same thinking we used when we created them. - Albert Einstein Use React / Flux
- 8. React Plays nice with parallel work on the same module. One person can work on one (set of) self contained component(s). Stores and actions play nice with separation and are easy to merge, usually :-)
- 9. Rules of engagement Root component has the context All child components accept properties only Child components talk to parent through callbacks Actions talk to the outside world
- 10. Between teams If you're going through hell, keep going. - Winston Churchill Common components Common tools Common build system
- 12. Deploy
- 13. Thank you! Refreshments anyone? #IBDevDays16 [:coffee, :juice, :water] |> Stream.cycle |> Stream.each(&IO.inspect/1) |> Enum.filter(&(&1))