Dataset Preview
The full dataset viewer is not available (click to read why). Only showing a preview of the rows.
The dataset generation failed
Error code: DatasetGenerationError
Exception: CastError
Message: Couldn't cast
name: string
pretty_name: string
category: string
samples: int64
language: string
license: string
format: list<item: string>
child 0, item: string
to
{'id': Value('string'), 'category': Value('string'), 'domain': Value('string'), 'objective': Value('string'), 'requirements': List(Value('string')), 'recommended_architecture': Value('string'), 'components': List(Value('string')), 'tradeoffs': Value('string'), 'decision_rationale': Value('string'), 'difficulty': Value('int64')}
because column names don't match
Traceback: Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/datasets/builder.py", line 1858, in _prepare_split_single
num_examples, num_bytes = writer.finalize()
^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/datasets/arrow_writer.py", line 781, in finalize
self.write_rows_on_file()
File "/usr/local/lib/python3.12/site-packages/datasets/arrow_writer.py", line 663, in write_rows_on_file
self._write_table(table)
File "/usr/local/lib/python3.12/site-packages/datasets/arrow_writer.py", line 773, in _write_table
pa_table = table_cast(pa_table, self._schema)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/datasets/table.py", line 2369, in table_cast
return cast_table_to_schema(table, schema)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/datasets/table.py", line 2297, in cast_table_to_schema
raise CastError(
datasets.table.CastError: Couldn't cast
name: string
pretty_name: string
category: string
samples: int64
language: string
license: string
format: list<item: string>
child 0, item: string
to
{'id': Value('string'), 'category': Value('string'), 'domain': Value('string'), 'objective': Value('string'), 'requirements': List(Value('string')), 'recommended_architecture': Value('string'), 'components': List(Value('string')), 'tradeoffs': Value('string'), 'decision_rationale': Value('string'), 'difficulty': Value('int64')}
because column names don't match
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 1361, in compute_config_parquet_and_info_response
parquet_operations, partial, estimated_dataset_info = stream_convert_to_parquet(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/src/services/worker/src/worker/job_runners/config/parquet_and_info.py", line 940, in stream_convert_to_parquet
builder._prepare_split(split_generator=splits_generators[split], file_format="parquet")
File "/usr/local/lib/python3.12/site-packages/datasets/builder.py", line 1683, in _prepare_split
for job_id, done, content in self._prepare_split_single(
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/datasets/builder.py", line 1869, in _prepare_split_single
raise DatasetGenerationError("An error occurred while generating the dataset") from e
datasets.exceptions.DatasetGenerationError: An error occurred while generating the datasetNeed help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.
id string | category string | domain string | objective string | requirements list | recommended_architecture string | components list | tradeoffs string | decision_rationale string | difficulty int64 |
|---|---|---|---|---|---|---|---|---|---|
AIARC_00001 | architecture | recommendations | Design a monolith solution for a recommendations platform with low budget. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A monolith approach with clear boundaries around the file and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Monolith improves the low budget story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00002 | architecture | audit | Design a microservices solution for a audit platform with high throughput. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A microservices approach with clear boundaries around the record and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Microservices improves the high throughput story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00003 | architecture | logging | Design a modular monolith solution for a logging platform with strict compliance. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A modular monolith approach with clear boundaries around the metric and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Modular Monolith improves the strict compliance story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00004 | architecture | sync | Design a event-driven solution for a sync platform with rapid iteration. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A event-driven approach with clear boundaries around the notification and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Event-Driven improves the rapid iteration story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00005 | architecture | streaming | Design a CQRS solution for a streaming platform with multi-tenant. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A CQRS approach with clear boundaries around the task and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Cqrs improves the multi-tenant story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00006 | architecture | exports | Design a hexagonal solution for a exports platform with offline support. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A hexagonal approach with clear boundaries around the route and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Hexagonal improves the offline support story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00007 | architecture | imports | Design a clean architecture solution for a imports platform with global scale. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A clean architecture approach with clear boundaries around the service and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Clean Architecture improves the global scale story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00008 | architecture | payments | Design a serverless solution for a payments platform with low latency. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A serverless approach with clear boundaries around the adapter and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Serverless improves the low latency story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00009 | architecture | messaging | Design a monolith solution for a messaging platform with low budget. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A monolith approach with clear boundaries around the handler and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Monolith improves the low budget story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00010 | architecture | admin | Design a microservices solution for a admin platform with high throughput. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A microservices approach with clear boundaries around the controller and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Microservices improves the high throughput story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00011 | architecture | dashboard | Design a modular monolith solution for a dashboard platform with strict compliance. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A modular monolith approach with clear boundaries around the repository and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Modular Monolith improves the strict compliance story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00012 | architecture | billing | Design a event-driven solution for a billing platform with rapid iteration. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A event-driven approach with clear boundaries around the client and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Event-Driven improves the rapid iteration story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00013 | architecture | auth | Design a CQRS solution for a auth platform with multi-tenant. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A CQRS approach with clear boundaries around the pipeline and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Cqrs improves the multi-tenant story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00014 | architecture | search | Design a hexagonal solution for a search platform with offline support. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A hexagonal approach with clear boundaries around the module and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Hexagonal improves the offline support story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00015 | architecture | analytics | Design a clean architecture solution for a analytics platform with global scale. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A clean architecture approach with clear boundaries around the invoice and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Clean Architecture improves the global scale story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00016 | architecture | notifications | Design a serverless solution for a notifications platform with low latency. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A serverless approach with clear boundaries around the session and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Serverless improves the low latency story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00017 | architecture | reports | Design a monolith solution for a reports platform with low budget. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A monolith approach with clear boundaries around the token and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Monolith improves the low budget story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00018 | architecture | cache | Design a microservices solution for a cache platform with high throughput. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A microservices approach with clear boundaries around the queue and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Microservices improves the high throughput story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00019 | architecture | scheduler | Design a modular monolith solution for a scheduler platform with strict compliance. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A modular monolith approach with clear boundaries around the worker and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Modular Monolith improves the strict compliance story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00020 | architecture | uploads | Design a event-driven solution for a uploads platform with rapid iteration. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A event-driven approach with clear boundaries around the parser and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Event-Driven improves the rapid iteration story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00021 | architecture | webhooks | Design a CQRS solution for a webhooks platform with multi-tenant. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A CQRS approach with clear boundaries around the report and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Cqrs improves the multi-tenant story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00022 | architecture | profiles | Design a hexagonal solution for a profiles platform with offline support. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A hexagonal approach with clear boundaries around the profile and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Hexagonal improves the offline support story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00023 | architecture | checkout | Design a clean architecture solution for a checkout platform with global scale. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A clean architecture approach with clear boundaries around the cart and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Clean Architecture improves the global scale story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00024 | architecture | inventory | Design a serverless solution for a inventory platform with low latency. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A serverless approach with clear boundaries around the order and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Serverless improves the low latency story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00025 | architecture | recommendations | Design a monolith solution for a recommendations platform with low budget. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A monolith approach with clear boundaries around the cache_key and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Monolith improves the low budget story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00026 | architecture | audit | Design a microservices solution for a audit platform with high throughput. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A microservices approach with clear boundaries around the job and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Microservices improves the high throughput story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00027 | architecture | logging | Design a modular monolith solution for a logging platform with strict compliance. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A modular monolith approach with clear boundaries around the event and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Modular Monolith improves the strict compliance story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00028 | architecture | sync | Design a event-driven solution for a sync platform with rapid iteration. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A event-driven approach with clear boundaries around the payload and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Event-Driven improves the rapid iteration story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00029 | architecture | streaming | Design a CQRS solution for a streaming platform with multi-tenant. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A CQRS approach with clear boundaries around the file and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Cqrs improves the multi-tenant story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00030 | architecture | exports | Design a hexagonal solution for a exports platform with offline support. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A hexagonal approach with clear boundaries around the record and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Hexagonal improves the offline support story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00031 | architecture | imports | Design a clean architecture solution for a imports platform with global scale. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A clean architecture approach with clear boundaries around the metric and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Clean Architecture improves the global scale story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00032 | architecture | payments | Design a serverless solution for a payments platform with low latency. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A serverless approach with clear boundaries around the notification and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Serverless improves the low latency story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00033 | architecture | messaging | Design a monolith solution for a messaging platform with low budget. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A monolith approach with clear boundaries around the task and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Monolith improves the low budget story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00034 | architecture | admin | Design a microservices solution for a admin platform with high throughput. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A microservices approach with clear boundaries around the route and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Microservices improves the high throughput story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00035 | architecture | dashboard | Design a modular monolith solution for a dashboard platform with strict compliance. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A modular monolith approach with clear boundaries around the service and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Modular Monolith improves the strict compliance story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00036 | architecture | billing | Design a event-driven solution for a billing platform with rapid iteration. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A event-driven approach with clear boundaries around the adapter and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Event-Driven improves the rapid iteration story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00037 | architecture | auth | Design a CQRS solution for a auth platform with multi-tenant. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A CQRS approach with clear boundaries around the handler and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Cqrs improves the multi-tenant story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00038 | architecture | search | Design a hexagonal solution for a search platform with offline support. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A hexagonal approach with clear boundaries around the controller and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Hexagonal improves the offline support story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00039 | architecture | analytics | Design a clean architecture solution for a analytics platform with global scale. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A clean architecture approach with clear boundaries around the repository and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Clean Architecture improves the global scale story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00040 | architecture | notifications | Design a serverless solution for a notifications platform with low latency. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A serverless approach with clear boundaries around the client and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Serverless improves the low latency story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00041 | architecture | reports | Design a monolith solution for a reports platform with low budget. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A monolith approach with clear boundaries around the pipeline and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Monolith improves the low budget story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00042 | architecture | cache | Design a microservices solution for a cache platform with high throughput. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A microservices approach with clear boundaries around the module and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Microservices improves the high throughput story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00043 | architecture | scheduler | Design a modular monolith solution for a scheduler platform with strict compliance. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A modular monolith approach with clear boundaries around the invoice and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Modular Monolith improves the strict compliance story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00044 | architecture | uploads | Design a event-driven solution for a uploads platform with rapid iteration. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A event-driven approach with clear boundaries around the session and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Event-Driven improves the rapid iteration story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00045 | architecture | webhooks | Design a CQRS solution for a webhooks platform with multi-tenant. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A CQRS approach with clear boundaries around the token and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Cqrs improves the multi-tenant story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00046 | architecture | profiles | Design a hexagonal solution for a profiles platform with offline support. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A hexagonal approach with clear boundaries around the queue and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Hexagonal improves the offline support story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00047 | architecture | checkout | Design a clean architecture solution for a checkout platform with global scale. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A clean architecture approach with clear boundaries around the worker and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Clean Architecture improves the global scale story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00048 | architecture | inventory | Design a serverless solution for a inventory platform with low latency. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A serverless approach with clear boundaries around the parser and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Serverless improves the low latency story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00049 | architecture | recommendations | Design a monolith solution for a recommendations platform with low budget. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A monolith approach with clear boundaries around the report and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Monolith improves the low budget story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00050 | architecture | audit | Design a microservices solution for a audit platform with high throughput. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A microservices approach with clear boundaries around the profile and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Microservices improves the high throughput story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00051 | architecture | logging | Design a modular monolith solution for a logging platform with strict compliance. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A modular monolith approach with clear boundaries around the cart and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Modular Monolith improves the strict compliance story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00052 | architecture | sync | Design a event-driven solution for a sync platform with rapid iteration. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A event-driven approach with clear boundaries around the order and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Event-Driven improves the rapid iteration story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00053 | architecture | streaming | Design a CQRS solution for a streaming platform with multi-tenant. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A CQRS approach with clear boundaries around the cache_key and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Cqrs improves the multi-tenant story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00054 | architecture | exports | Design a hexagonal solution for a exports platform with offline support. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A hexagonal approach with clear boundaries around the job and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Hexagonal improves the offline support story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00055 | architecture | imports | Design a clean architecture solution for a imports platform with global scale. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A clean architecture approach with clear boundaries around the event and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Clean Architecture improves the global scale story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00056 | architecture | payments | Design a serverless solution for a payments platform with low latency. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A serverless approach with clear boundaries around the payload and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Serverless improves the low latency story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00057 | architecture | messaging | Design a monolith solution for a messaging platform with low budget. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A monolith approach with clear boundaries around the file and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Monolith improves the low budget story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00058 | architecture | admin | Design a microservices solution for a admin platform with high throughput. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A microservices approach with clear boundaries around the record and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Microservices improves the high throughput story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00059 | architecture | dashboard | Design a modular monolith solution for a dashboard platform with strict compliance. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A modular monolith approach with clear boundaries around the metric and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Modular Monolith improves the strict compliance story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00060 | architecture | billing | Design a event-driven solution for a billing platform with rapid iteration. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A event-driven approach with clear boundaries around the notification and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Event-Driven improves the rapid iteration story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00061 | architecture | auth | Design a CQRS solution for a auth platform with multi-tenant. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A CQRS approach with clear boundaries around the task and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Cqrs improves the multi-tenant story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00062 | architecture | search | Design a hexagonal solution for a search platform with offline support. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A hexagonal approach with clear boundaries around the route and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Hexagonal improves the offline support story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00063 | architecture | analytics | Design a clean architecture solution for a analytics platform with global scale. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A clean architecture approach with clear boundaries around the service and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Clean Architecture improves the global scale story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00064 | architecture | notifications | Design a serverless solution for a notifications platform with low latency. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A serverless approach with clear boundaries around the adapter and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Serverless improves the low latency story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00065 | architecture | reports | Design a monolith solution for a reports platform with low budget. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A monolith approach with clear boundaries around the handler and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Monolith improves the low budget story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00066 | architecture | cache | Design a microservices solution for a cache platform with high throughput. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A microservices approach with clear boundaries around the controller and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Microservices improves the high throughput story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00067 | architecture | scheduler | Design a modular monolith solution for a scheduler platform with strict compliance. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A modular monolith approach with clear boundaries around the repository and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Modular Monolith improves the strict compliance story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00068 | architecture | uploads | Design a event-driven solution for a uploads platform with rapid iteration. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A event-driven approach with clear boundaries around the client and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Event-Driven improves the rapid iteration story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00069 | architecture | webhooks | Design a CQRS solution for a webhooks platform with multi-tenant. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A CQRS approach with clear boundaries around the pipeline and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Cqrs improves the multi-tenant story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00070 | architecture | profiles | Design a hexagonal solution for a profiles platform with offline support. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A hexagonal approach with clear boundaries around the module and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Hexagonal improves the offline support story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00071 | architecture | checkout | Design a clean architecture solution for a checkout platform with global scale. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A clean architecture approach with clear boundaries around the invoice and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Clean Architecture improves the global scale story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00072 | architecture | inventory | Design a serverless solution for a inventory platform with low latency. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A serverless approach with clear boundaries around the session and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Serverless improves the low latency story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00073 | architecture | recommendations | Design a monolith solution for a recommendations platform with low budget. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A monolith approach with clear boundaries around the token and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Monolith improves the low budget story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00074 | architecture | audit | Design a microservices solution for a audit platform with high throughput. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A microservices approach with clear boundaries around the queue and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Microservices improves the high throughput story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00075 | architecture | logging | Design a modular monolith solution for a logging platform with strict compliance. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A modular monolith approach with clear boundaries around the worker and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Modular Monolith improves the strict compliance story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00076 | architecture | sync | Design a event-driven solution for a sync platform with rapid iteration. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A event-driven approach with clear boundaries around the parser and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Event-Driven improves the rapid iteration story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00077 | architecture | streaming | Design a CQRS solution for a streaming platform with multi-tenant. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A CQRS approach with clear boundaries around the report and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Cqrs improves the multi-tenant story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00078 | architecture | exports | Design a hexagonal solution for a exports platform with offline support. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A hexagonal approach with clear boundaries around the profile and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Hexagonal improves the offline support story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00079 | architecture | imports | Design a clean architecture solution for a imports platform with global scale. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A clean architecture approach with clear boundaries around the cart and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Clean Architecture improves the global scale story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00080 | architecture | payments | Design a serverless solution for a payments platform with low latency. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A serverless approach with clear boundaries around the order and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Serverless improves the low latency story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00081 | architecture | messaging | Design a monolith solution for a messaging platform with low budget. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A monolith approach with clear boundaries around the cache_key and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Monolith improves the low budget story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00082 | architecture | admin | Design a microservices solution for a admin platform with high throughput. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A microservices approach with clear boundaries around the job and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Microservices improves the high throughput story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00083 | architecture | dashboard | Design a modular monolith solution for a dashboard platform with strict compliance. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A modular monolith approach with clear boundaries around the event and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Modular Monolith improves the strict compliance story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00084 | architecture | billing | Design a event-driven solution for a billing platform with rapid iteration. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A event-driven approach with clear boundaries around the payload and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Event-Driven improves the rapid iteration story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00085 | architecture | auth | Design a CQRS solution for a auth platform with multi-tenant. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A CQRS approach with clear boundaries around the file and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Cqrs improves the multi-tenant story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00086 | architecture | search | Design a hexagonal solution for a search platform with offline support. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A hexagonal approach with clear boundaries around the record and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Hexagonal improves the offline support story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00087 | architecture | analytics | Design a clean architecture solution for a analytics platform with global scale. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A clean architecture approach with clear boundaries around the metric and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Clean Architecture improves the global scale story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00088 | architecture | notifications | Design a serverless solution for a notifications platform with low latency. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A serverless approach with clear boundaries around the notification and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Serverless improves the low latency story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00089 | architecture | reports | Design a monolith solution for a reports platform with low budget. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A monolith approach with clear boundaries around the task and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Monolith improves the low budget story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00090 | architecture | cache | Design a microservices solution for a cache platform with high throughput. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A microservices approach with clear boundaries around the route and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Microservices improves the high throughput story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00091 | architecture | scheduler | Design a modular monolith solution for a scheduler platform with strict compliance. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A modular monolith approach with clear boundaries around the service and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Modular Monolith improves the strict compliance story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00092 | architecture | uploads | Design a event-driven solution for a uploads platform with rapid iteration. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A event-driven approach with clear boundaries around the adapter and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Event-Driven improves the rapid iteration story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00093 | architecture | webhooks | Design a CQRS solution for a webhooks platform with multi-tenant. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A CQRS approach with clear boundaries around the handler and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Cqrs improves the multi-tenant story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00094 | architecture | profiles | Design a hexagonal solution for a profiles platform with offline support. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A hexagonal approach with clear boundaries around the controller and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Hexagonal improves the offline support story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00095 | architecture | checkout | Design a clean architecture solution for a checkout platform with global scale. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A clean architecture approach with clear boundaries around the repository and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Clean Architecture improves the global scale story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00096 | architecture | inventory | Design a serverless solution for a inventory platform with low latency. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A serverless approach with clear boundaries around the client and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Serverless improves the low latency story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00097 | architecture | recommendations | Design a monolith solution for a recommendations platform with low budget. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A monolith approach with clear boundaries around the pipeline and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Monolith improves the low budget story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
AIARC_00098 | architecture | audit | Design a microservices solution for a audit platform with high throughput. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A microservices approach with clear boundaries around the module and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Microservices improves the high throughput story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 4 |
AIARC_00099 | architecture | logging | Design a modular monolith solution for a logging platform with strict compliance. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A modular monolith approach with clear boundaries around the invoice and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Modular Monolith improves the strict compliance story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 5 |
AIARC_00100 | architecture | sync | Design a event-driven solution for a sync platform with rapid iteration. | [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
] | A event-driven approach with clear boundaries around the session and core business rules. | [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
] | Event-Driven improves the rapid iteration story, but the team must keep ownership boundaries explicit. | Choose the simplest architecture that satisfies the operational and product constraints. | 3 |
End of preview.
AIForge-05-Architecture
Architecture Dataset for AI and Programming Tasks
Overview
AIForge-05-Architecture is a curated English dataset designed for AI systems working on architecture tasks in software engineering and programming.
Contents
data.jsonldata.jsonmetadata.json
Use Cases
- AI agent training
- Supervised fine-tuning
- Evaluation and benchmarking
- Software engineering research
Example Record
{
"id": "AIARC_00001",
"category": "architecture",
"domain": "recommendations",
"objective": "Design a monolith solution for a recommendations platform with low budget.",
"requirements": [
"Scale predictably",
"Keep observability high",
"Avoid unnecessary coupling",
"Support future growth"
],
"recommended_architecture": "A monolith approach with clear boundaries around the file and core business rules.",
"components": [
"API layer",
"Domain service",
"Persistence layer",
"Async worker",
"Monitoring and alerting"
],
"tradeoffs": "Monolith improves the low budget story, but the team must keep ownership boundaries explicit.",
"decision_rationale": "Choose the simplest architecture that satisfies the operational and product constraints.",
"difficulty": 3
}
License
Released under CC BY 4.0.
Source
JumpLander
- Downloads last month
- 87