# Using babylon as renderer-only **URL:** \ **Category:** Questions\ **Created:** [January 28, 2020, 7:14am UTC](https://forum.babylonjs.com/t/using-babylon-as-renderer-only/8274 "2020-01-28T07:14:16Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![belfortk](https://avatars.discourse-cdn.com/v4/letter/b/ed8c4c/32.png) [@belfortk](https://forum.babylonjs.com/u/belfortk)\ **Post date:** [January 29, 2020, 1:15am UTC](https://forum.babylonjs.com/t/using-babylon-as-renderer-only/8274/4 "2020-01-29T01:15:20Z")
You might want to look into using Observables? I know BabylonJS uses them a bunch to manage reacting to events. [https://doc.babylonjs.com/how\_to/observables](https://doc.babylonjs.com/how_to/observables) I was inspired by this [article](https://medium.com/@clevyr/entity-component-system-for-react-js-e3ab6e9be776), maybe you’d find a good jumping off point. pinging @Deltakosh? Edit: Oh hey someone else on the forum kinda agreed with me! > [@Best Practice for separating out components](https://forum.babylonjs.com/t/best-practice-for-separating-out-components/8275/3): > > This is an issue I’ve been trying to figure out myself for quite a while. I agree that belfortk’s suggestion of asset containers works for encapsulating assets but I don’t know if it works as well for the logic. Babylon is pretty flexible when it comes to how you handle your logic, so I’ve tried three options (no big projects so I’m not sure how any of them scale, also keep in mind that I use TypeScript which means I can’t just add methods to defined Babylon classes): Extending mesh class. W… --- _[View the full topic](https://forum.babylonjs.com/t/using-babylon-as-renderer-only/8274)._