Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Database Sharding Source: ISO/IEC/IEEE 42010:2022 Source reference: https://www.iso.org/standard/74393.html Additional information: Database sharding ADR is a decision to choose the technique used in distributed databases to improve scalability and performance. It involves partitioning a large database into smaller, more manageable pieces called shards, which are distributed across multiple servers. Each shard contains a subset of the data, and queries are routed to the appropriate shard based on a predefined sharding key. This allows for faster query processing and reduces the risk of data loss or downtime in the event of a server failure. However, implementing database sharding requires careful planning and coordination to ensure data consistency and availability. Example: Database Sharding: Decision: Implementing database sharding to distribute data across multiple database instances. Rationale: Sharding allows for horizontal scaling of the database by splitting data into smaller partitions and distributing them across multiple database servers, improving performance and accommodating increased data volume. LOST view: Digital Solution Architecture Decisions Catalogue view Identifier: http://data.europa.eu/dr8/egovera/DatabaseShardingGoal EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal ABB name: egovera:DatabaseShardingGoal EIRA concept: eira:ArchitectureBuildingBlock Last modification: 2023-06-15 dct:identifier: ADR-20230515180947693 dct:title: Architecture Decision Record about Database Sharding 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.