This section defines key terms related to a BLOCK architecture and its building process. The vocabulary emphasizes technical accuracy and clarity, using concise and commonly understood terms.

• Microservice: An architectural style where a large application is decomposed into autonomous, independently deployable, and business-aligned services. Each microservice performs a specific function with modularity and loose coupling.

• Fat Service: A type of microservice that encompasses a broader range of functionalities compared to standard microservices. This may be suitable for smaller applications or where tight integration is essential.

• Nanoservice: A highly granular microservice focused on a single, specialized function. It may encapsulate sub-functionalities for further granularity.

• Subfunction: A specific operation within a nanoservice that provides access to a particular database or storage.

• Data Source: A database or storage system containing user-specific information. It only responds to authorized requests from microservices or nanoservices.

• Authorization Service: A resource responsible for verifying access permissions before allowing communication between microservices or nanoservices and data sources.

• jGraph: A JSON-formatted graph depicting resource interactions within a specific application block.

• hGraph: A visually-oriented graph created using tools like Miro, representing resource interactions within a specific application block.

• Resource: An entity within the system, such as microservices, nanoservices, roles, policies, infrastructure components (EC2 instances, CloudFormation stacks, S3 buckets), etc.

• Payload: An object or data package originating externally, triggering or performing actions on resources within the system. It contains instructions for resource creation, configuration, testing, notification, or maintenance.

• Manifest: An object containing configuration details or specifications essential for a specific resource's functionality. It acts as a blueprint or instruction set for resource installation.

• Alias: An alternative name assigned to each resource, following specific naming conventions depending on the resource type.

• Alias Theme: A topic used for consistent alias naming within specific resource categories or application blocks.

• Domestic Communication: Interaction between components belonging to the same application.

• Foreign Communication: Interaction between components belonging to different applications.

• Phase: A distinct stage in the application creation process with specific tasks and predetermined actions to achieve a particular goal.

• Preparation Phase: Stage where users identify and define all necessary resources (microservices, nanoservices, data sources, authorization services, graphs, repositories) for a specific application block.

• Configuration Phase: Stage where users create human-readable graphs, JSON graphs, repositories, and message templates for all resources in the block.

• Installation Phase: Stage where all resources are created and installed.

• Communication Phase: Stage where communication between resources is tested without creating new resources.

• Operation Phase: Stage where the application is fully functional and operational.

Mission accomplished! Now, let's go ahead and simplify your Kubernetes journey. Contact k8or.