Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Horizontal Scaling Source: ISO/IEC/IEEE 42010:2022 Source reference: https://www.iso.org/standard/74393.html Additional information: Horizontal scaling is a decision in IT architecture that involves adding more servers or nodes to a system to increase its capacity and performance. This approach is often used in distributed systems, where workloads can be spread across multiple servers to improve efficiency and reduce the risk of downtime. Horizontal scaling can be achieved through various techniques, such as load balancing, clustering, and sharding, and it can help organizations to scale their IT infrastructure in a cost-effective and flexible manner. However, horizontal scaling also requires careful planning and management to ensure that the system remains reliable and secure as it grows. Example: Horizontal Scaling: Decision: Adopting a microservices architecture to enable horizontal scaling of system components. Rationale: A microservices architecture allows for independent scaling of individual services based on demand, providing flexibility and the ability to allocate resources where they are most needed. LOST view: Digital Solution Architecture Decisions Catalogue view Identifier: http://data.europa.eu/dr8/egovera/HorizontalScalingGoal EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal ABB name: egovera:HorizontalScalingGoal EIRA concept: eira:ArchitectureBuildingBlock Last modification: 2023-06-15 dct:identifier: ADR-20230515180947594 dct:title: Architecture Decision Record about Horizontal 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.