Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Vertical Scaling
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Vertical scaling, also known as scaling up or scaling vertically, is a method of increasing the capacity and capabilities of a single server or machine by adding more resources to it. This is typically achieved by upgrading the hardware components, such as increasing the processing power, memory, storage capacity, or network bandwidth of the server.
Example: Title: Vertical Scaling Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/VerticalScalingGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:VerticalScalingGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-06
dct:identifier: ADR-20230606091024769
dct:title: Architecture Decision Record about Vertical Scaling
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
|
|
dct:modified | 2024-01-28 |
dct:identifier | ADR-20230606091024769 |
dct:title | Architecture Decision Record about Vertical Scaling |
skos:example | Title: Vertical Scaling Architecture Decision Record (ADR) |
eira:adr_context | The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons. |
eira:adr_decision | The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how. |
eira:adr_status | [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)] |
eira:adr_consecuences | The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture. |
eira:concept | eira:ArchitectureBuildingBlock |
eira:definitionSource | ISO/IEC/IEEE 42010:2022 |
eira:definitionSourceReference | https://www.iso.org/standard/74393.html |
skos:note | Vertical scaling, also known as scaling up or scaling vertically, is a method of increasing the capacity and capabilities of a single server or machine by adding more resources to it. This is typically achieved by upgrading the hardware components, such as increasing the processing power, memory, storage capacity, or network bandwidth of the server. |
eira:PURI | http://data.europa.eu/dr8/VerticalScalingGoal |
dct:type | eira:VerticalScalingGoal |
skos:definition | Architecture Decision Record from where you should specialise the ADR SBBs regarding the Vertical Scaling |
eira:view | Digital Solution Architecture Decisions Catalogue view |
eira:eifLayer | N/A |
skos:broader | http://data.europa.eu/dr8/DigitalSolutionArchitectureDecisionGoal |