architecture-katas

KO | EN

gitlite — search

#hacktoberfest #typescript #llm #golang #machine-learning #docker #awesome #vue #awesome-list #pytorch #security #openai #mcp #ios

architecture-katas

(★ 13)

Architecture Katas

architecture-katas 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Architecture Katas - Farmacy Food

## Presentation
[View Presentation](https://drive.google.com/drive/folders/1iaBb1ZlPgxhvYSS1HB35YBBvyU9GvBhq?usp=sharing)

## Overview
![Overview](https://raw.githubusercontent.com/icedhacker/architecture-katas/main/image/FarmacyFoods_Overview.png)

Farmacy Food is a tech-enabled healthy food startup that creates tasty meals around people's dietary needs and active lifestyles to support their overall well-being.

Their mission is to make health and wellness radically affordable and accessible.

Let me explain the basic concept of Farmacy Food:
1. Farmacy Food is a “Ghost Kitchen” which will prepare the meals.
2. We use Smart Fridges and Sub-let spaces in other businesses as our Points of Sale. So, the meals are delivered to these POS from the Kitchen.
3. Customers will check availability of meals using Mobile/Web App in the nearby Points of Sale.
4. Customers go to the nearest available POS and purchase or pick-up the meals.
5. The system has to maintain the inventory levels in the Smart Fridge and other POS.

Some Long Term goals are: 
1. Allowing multiple vendors or kitchens to provide meals using our system.
2. Provide personalized recommendation based on user profile & purchase history.

## Step 1
### Identifying the Users/Clients
1. Customers
2. Vendors
3. Kitchens
4. Smart Fridges
5. Kiosk / POS Systems
6. Admin

### Identifying Use Cases and deriving components
![Use-Case Analysis](https://raw.githubusercontent.com/icedhacker/architecture-katas/main/image/FarmacyFoods_UseCase_Analysis.png)

## Step 2
### Overall High-level Architecture

![High Level Architecture Diagram](https://raw.githubusercontent.com/icedhacker/architecture-katas/main/image/OverallArchitectureDiagram.png)

Architecture Approach for **Farmacy Food Service** - Decision Records
1. [Monolithic Design](adrs/monolithic-approach.md)
2. [Serverless Design](adrs/serverless-approach.md)

Moving ahead with the **Serverless design** for the Farmacy Food Service.

## Step 3
### Architecture of POS integration

Decision Record: [POS Integration Design](adrs/pos-integration.md)

![POS Integration Architecture Diagram](https://raw.githubusercontent.com/icedhacker/architecture-katas/main/image/POSIntegrationArchitecture.png)

## Step 4
### Component & Sequence Diagrams

![Component Diagram](https://raw.githubusercontent.com/icedhacker/architecture-katas/main/image/component-arch-diagram.png)

#### Vendor Registration

![Vendor Sequence Diagram](https://raw.githubusercontent.com/icedhacker/architecture-katas/main/sequence-diagrams/vendor.png)

#### Kitchen Registration

![Kitchen Sequence Diagram](https://raw.githubusercontent.com/icedhacker/architecture-katas/main/sequence-diagrams/kitchen.png)

#### Adding Menu Items

![Menu Sequence Diagram](https://raw.githubusercontent.com/icedhacker/architecture-katas/main/sequence-diagrams/menu.png)

#### Kitchen Order Placement

![Kitchen Order Placement Diagram](https://raw.githubusercontent.com/icedhacker/architecture-katas/main/sequence-diagrams/kitchen-order.png)

#### Expiry Tracker

![Expiry Tracker Diagram](https://raw.githubusercontent.com/icedhacker/architecture-katas/main/sequence-diagrams/expiry-tracker.png)

#### Online Order Reservations

Architecture Decisions:

[Inventory Updates Communicaiton](adrs/inventory-reservations.md)

[Payment Service Communication](adrs/payments-communication.md)

![Order Resevation Diagram](https://raw.githubusercontent.com/icedhacker/architecture-katas/main/sequence-diagrams/reserve-meal.png)

#### Purchasing Meal offline

Architecture Decisions:

[POS Integration](adrs/pos-integration.md)

![Purchase Meal Diagram](https://raw.githubusercontent.com/icedhacker/architecture-katas/main/sequence-diagrams/purchase-items-and-send-survey.png)

#### Create Surveys

![Create Surveys Diagram](https://raw.githubusercontent.com/icedhacker/architecture-katas/main/sequence-diagrams/surveys.png)

#### Create Coupons

![Create Coupons Diagram](https://raw.githubusercontent.com/icedhacker/architecture-katas/main/sequence-diagrams/coupons-create.png)

## Step 5
### Components Architecture Characteristics

| Component | Description | Architecture Characteristics |
|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|
| Inventory | As this is one of the system's core components, it need to be highly available, provide necessary responses to other system services in short time. | 1- Scalability 2- Performance 3- Availability 4- Reliability |
| Expiry Tracker | This job needs to run daily but should be quick enough to analyze all items that are expired. | 1- Performance |
| Feedback | This component is highly needed to render the menu, and thus needs to be highly available and performant. | 1- Performance 2- Availability 3- Customizable |
| User Profile | User Profile will provide users' data and authentication services | 1- Availability 2- Performance 3- Reliability 4- Scalability
| Coupons | Coupons service will be used mainly to create promotional coupons and validate them. | 1- Availability 2- Reliability 3- Customizable
| Menu Catalog | Menu Catalog will hold the menu for all enabled items and it will manage adding/removing/disabiling menu items as well as listing menu items for customers. | 1- Availability 2- Performance 3- Customizable 4- Scalability 5- Reliability

architecture-katas

architecture-katas 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

architecture-katas

architecture-katas 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README