---
title: "Comment by Fabio Sarmento on \"Advanced Patterns & Integration with Frameworks\" | Hashnode"
description: "this is a great overview of why integrating Web Components with frameworks is tricky. tbh, I’ve run into those data flow model issues myself. Once, I had a proj"
url: "https://hashnode.com/posts/advanced-patterns-and-integration-with-frameworks/67fbd6711a499b9078b8ff7b/comment/69b6a671d6abc7497bc46b20"
---

[Discussion](https://hashnode.com/posts/advanced-patterns-and-integration-with-frameworks/67fbd6711a499b9078b8ff7b)

Comment [Advanced Patterns & Integration with Frameworks](https://hashnode.com/posts/advanced-patterns-and-integration-with-frameworks/67fbd6711a499b9078b8ff7b)

[Fabio Sarmento](https://hashnode.com/@sarmento)

[Mar 15](https://hashnode.com/posts/advanced-patterns-and-integration-with-frameworks/67fbd6711a499b9078b8ff7b/comment/69b6a671d6abc7497bc46b20)

this is a great overview of why integrating Web Components with frameworks is tricky. tbh, I’ve run into those data flow model issues myself. Once, I had a project where the communication between React and a Web Component became a nightmare, but using the Ref Pattern definitely helped tidy things up. have you tried other patterns for handling lifecycle events?