Component | C4 model
c4model.com · 986 words · saved by 1 readers
The C4 model for visualising software architecture (official website)
The word “component” is a hugely overloaded term in the software development industry but, in the C4 model, a component is a grouping of related functionality encapsulated behind a well-defined interface. If you’re using a language like Java or C#, the simplest way to think of a component is that it’s a collection of implementation classes behind an interface. With the C4 model, components are not separately deployable units. Instead, it’s the container that’s the deployable unit. In other words, all components inside a container execute in the same process space. Aspects such as how…
saved by
related reading
- Containerc4model.com
- Abstractionsc4model.com
- Microservicesc4model.com
- Software systemc4model.com
- Clean Coder Blogblog.cleancoder.com
- Non-functional requirementen.wikipedia.org
- How to write complex softwaregrantslatton.com
- Home | C4 modelc4model.com
- Design Patternsrefactoring.guru
- 4. Encapsulation - CS2030S Programming Methodology IInus-cs2030s.github.io
- Clean Architecture: Component Cohesion Principles | by Rebeca Mora | Mediummedium.com
- Components | The Component Gallerycomponent.gallery