Flexible Data Flow Architecture in Angular
Web applications are there to move data around in a useful and user-friendly way. Being quite opinionated, Angular defines its own data flow rules and provides specific ways to pass it around. You are probably already thinking about input and output binding and services, but it’s just the tip of the iceberg! I’ve counted more than 15 interaction options in total! Let’s zoom out and have a look at the general principles rather than going into implementation of specific features. In this talk we are going to structure ways of information sharing across your app and discuss the underlying design patterns. Being able to chose how you organise your data flows allows you to adjust the implementation to your use case. We will explore some examples where you can vary the degree of flexibility depending on the way you structure your components and services. However, with great flexibility comes great responsibility. So we will also touch upon the strengths and weaknesses of each data sharing approach.
Talk takeaways
Know your (data sharing) options
Choose your option wisely, namely according to the use case and the reasonable degree of flexibility it provides
About Maria
Maria is a Frontend Technology Lead at Aleri with current focus on Angular. She writes for ng-conf and speaks now and there at tech meetups and conferences. In her tweets and articles Maria likes to share her learnings from everyday coding. Fun fact: she illustrates her stories herself because she likes drawing.
Learn more about Maria at https://browserperson.medium.com/, https://twitter.com/BrowserPerson or https://www.linkedin.com/in/maria-korneeva/