🧱Brokenatom's Architecture

Overview

Brokenatom's architecture is designed to handle multiple CRUD (Create, Read, Update, Delete) operations, which are fundamental to web application functionality. These operations interact with the application's data, allowing users to create, retrieve, update, and delete data entries. Here, we detail the specific CRUD operations and their variations, along with the roles of data models, permissions, and the UI editor in Brokenatom's architecture.

CRUD Operations

CRUD operations form the backbone of data management within Brokenatom. They enable various actions on the data stored within the application:

1. Create: Add a new data entry.

2. Get (Retrieve): Fetch an existing data entry.

3. Update: Modify an existing data entry.

4. Delete: Remove an existing data entry.

These operations can be performed individually or in combination with additional parameters to cater to specific needs:

Get Operations

• Get One: Retrieve a single data entry.

• Get Selected One: Retrieve a specific data entry based on defined parameters.

• Get Many: Retrieve all data entries.

Create Operations

• Create One: Add a single new data entry.

Update Operations

• Update One: Modify a single data entry.

• Update Selected One: Modify a specific data entry based on defined parameters.

Delete Operations

• Delete One: Remove a single data entry.

• Delete Selected One: Remove a specific data entry based on defined parameters.

• Delete Many: Remove multiple data entries.

These operations are typically applied to a relational database, but the underlying logic remains consistent regardless of the data stored.

Data Models

Data models are the structural foundation of the application. They define the schema for data storage, including the types of data, relationships between different data entities, and the rules governing the data. Data models ensure that data is organized logically and can be accessed and manipulated efficiently.

Permissions

Permissions determine access control within the application. They define who can perform specific actions and access certain parts of the application. Permissions are essential for security and ensure that users only have access to the functionalities and data that they are authorized to use. This can include role-based access control (RBAC), where different roles (e.g., admin, user, guest) have varying levels of access and capabilities.

UI Editor

The UI editor is the interface for designing and customizing the look and feel of the application. It allows users to visually edit the application's design, layout, and user interface components. The UI editor makes it possible to create a user-friendly and aesthetically pleasing application without needing to write extensive code. It provides tools and options to modify elements such as colours, fonts, spacing, and overall design structure.