Q. Using vanilla javascript without any frameworks - what is a pattern for large scale component based architecture?
I understand the idea of components being split out into individual sections, and having their own structure, methods and api. However I don't know how to tie it all together. Where does the business logic reside? How do you structure the project, where do you include all the methods etc.
My experience is monolithic whereby everything is coupled too tightly. Any clarification on this would be much appreciated, feels like I'm running around in circles.
Note: When I'm talking about component based architecture, I'm referring to this idea
React. js, a JavaScript library, introduced a concept called Component-Based-Architecture, a method for encapsulating individual pieces of a larger user interface (aka components) into self-sustaining, independent micro-systems.
The core ecosystem of JavaScript consists of 3 main components which are ECMAScript, JavaScript Engine, and the JavaScript Runtime. It all starts with understanding what is ECMAScript and how is it different from JavaScript and followed by an understanding of the JavaScript Engine and the JavaScript Runtime.
1. A Web application framework that encapsulates the processing logic into modular components with the implementation details of request handling abstracted, independent from the incoming request protocols at the transport level. Learn more in: Java Web Application Frameworks.
The component-based framework we are using is called React. Developed by Facebook for its home page and released to the world's open source community in 2013, React is a framework that allows developers to make components for web pages that can be shared across teams.
You can read more about Object-Pattern and Module-Pattern
Here is a link to a lot of common patterns:
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With