A component is a software object, intended to interact with other components,
encapsulating certain functionality or a set of functionalities. It has an obviously
defined interface and conforms to a recommended behavior common to all components within an architecture.
Reusability
: being able to be used in different situations in different applicationsReplaceable
: Switching components with other similar components freelyNot context specific
: Components being able to work in different environments and contexts.Extensible
: extending a component to have a new behavior.Encapsulated
: a component covers the interface while not exposing the internal state, variables or process.Independent
: little to no dependency on other componentsEase of deployment
: Easily change and replacing components to newer versionsReduced cost
: The use of third-party components allows you to spread the cost of development and maintenance.Ease of development
: components being independent allows development without major problems to other parts of the system.Reusable
: Using components through multiple applications and systems which brings overall costs down.Modification of technical complexity
:A component modifies the complexity through the use of a component container and its services.Reliability
: Reusing components makes the system more consistent which in turn makes it more reliableSystem maintenance and evolution
: easy to update/change components without changing other parts of the systemIndependent
: Components are such that different groups could work on other parts of the same application without affecting each other boosting overall productivity. parent ----> data ----> child
parent <---- data <---- child(using a callback-function)
- How do components interact while on different pages that need to interact with
each other. Does passing data from one component to the other get tricky when dealing with login and stuff?