1.Basic specifications

Check the basic design specifications on the "OVERVIEW" tab of the report on the design details page.


Performance, Cost, Complexity

1. Select the "OVERVIEW" tab of the report.

2. The two numbers below the tab show maximum performance and maximum cost.

rps (Request Per Second): The maximum number of requests processed per second for each application. The larger the number, the higher the required performance. The numerical value fluctuates depending on the conditions such as many users, concentrated access, and many display parts per page.

USD/M: Estimated monthly cost of using the cloud. The currency unit changes according to the display language and is calculated by multiplying the price based on US dollars by a specific exchange rate. You can check the types of cloud resources and exchange rates that can be calculated with ForkMe! By clicking the "?" Icon.

Service start cost: Shows performance and cost when the requested volume is minimal. Clouds generally fluctuate in price depending on the volume requested.

3. The higher the number on each tab, the more information there is and the more complex the design.

Numbers ​​on the "OVERVIEW" tab: The number of files included in the design. The file contains the Cloud Design specification and the provisioning code for each cloud vendor.

Numbers on the "ACTORS" tab: The type of actor (system user) included in the design.

Numbers on the "RESOURCES" tab: The type of resource (cloud resource) included in the design.

Numbers on the "CONTEXTS" tab: The type of context (system usage) included in the design.

Usage

1. Select the "OVERVIEW" tab of the report.

2. The usage of the cloud is displayed in the middle. The first line is a descriptive text written by the designer, and the second and subsequent lines are a summary text automatically generated by ForkMe! from the design code.


Quality

1. Select the "OVERVIEW" tab of the report.

2. The audit results of the design are displayed at the bottom. If there is a red mark to indicate a warning, the quality of the design is not high. And the yellow mark is a standard recommendation. Please note that it may not be compliant depending on the design, so please be aware of this as a reminder.

3. The Actors displayed below the audit results are useful for quality evaluation. Click "Member information" of the person who is marked as "Certified" to check the design history. It is thought that the greater the amount of activity, the more design know-how is accumulated. The "Certified" mark is given when the designer is a ForkMe! User.


License

1. Select the "OVERVIEW" tab of the report.

2. The Public / Private and license types are displayed below the design title. If you reprint the design in publications or media other than ForkMe!, please follow the terms of use of this license. ForkMe! encourages designers to adopt a Creative Commons "CC0" license to support the free distribution of great designs.

2. Usages

ForkMe! calls the use of the cloud "CONTEXTS". Similar to software engineering use cases and user stories, it is a design unit that summarizes user-system interactions by purpose. You can see the details on the "CONTEXTS" tab of the report.


Request volume

1. Select the "CONTEXTS" tab of the report.

2. In each context of the list, a "Max throughput" is displayed, which indicates the required performance for each application. This is the maximum number of requests that the system accepts per second (self-ignitions for timed processing).

3. Click the "CONTEXTS" to see the detailed request volume. ForkMe! Calls the usage start point for each application a "trigger" and calculates the amount of communication from the trigger to the cloud as the required volume. There are two types of triggers: "Web access", which indicates a user's site visit, and "Timed action", which indicates the activation of a regular batch.

When "Type" is "Web Access"

PV/M:: Monthly page views calculated by multiplying the number of users by the daily active user rate (DAU) x 30 days.
DAU: A monthly average that indicates what percentage of all users visit each day.
Busy hours/day: The average number of hours in a day when access is concentrated.
Pages/visit: The number of pages the user views per visit.
Requests/page: The average number of requests included in one page.
Posts/visit: Shows what percentage of users post as well as browse.
Size/page: The size of browsing (data transmission to users) per page.
Size/post: The size of each post (data received from the user).
Throughput: The number of requests per second from the user.
Max performance duration: The monthly percentage of time that the maximum throughput lasts.
Requests: The number of monthly requests from users.
When "Type" is "Timed action"

Monthly request: The number of monthly requests by timed action. Shows the total amount of requests required for cost valuation.
Throughput: The number of requests by timed action per second. Indicates the concentration of requests required for performance evaluation.
Size/request: Indicates the size of data that occurs on each request and is received by subsequent systems.
Size/response: Shows the size of the data returned to the trigger by the subsequent system as a response to the request.

Processing volume

1. Select the "CONTEXTS" tab of the report.

2. In each context of the list, "Data Transfer Out" is displayed, which indicates the processing volume for each application. This is the total amount of data that the system sends to users and linked external systems in a month.

3. Click the "CONTEXTS" tab to see the detailed processing volume. ForkMe! collectively refers to users and external systems that cooperate with them as "ACTORS", and the processing volume is the amount of communication that occurs with the actors.

Data Transfer In: The size of the data received from the actor.
Data Transfer Out: The size of data transmission to the actor
Storage: the size to store the data received from the actor in the system.

Data flow

1. Select the "CONTEXTS" tab of the report.

2. You can see a summary of all contexts in the "System overview" in overview. "Max throughput" shows the maximum required performance in all contexts, and "Data Transfer Out" shows the total value of the response volumes in all contexts.

3. Click the "System overview" line for more information.

Throughput: The maximum throughput value in this design. Throughput is the number of requests issued by the trigger per second and is an indicator of required performance.
Data Transfer In: The total data size received from the actors.
Date Transfer Out: The total size of data sent to the actors.
Storage: The total size of data received from the actor and stored in the system.
Information: The type of information that the system handles, as defined by the designer. Each type has one of the attributes of personal information / confidential information / public information only.

4. On the right side of the screen, you will see a diagram showing the relationships between actors and resources.
Hover over the arrow to see the contents of the communication path, and hover over the icon to see an overview of actors and resources.

Red line: Risky (Personal or confidential information is exchanged through general public route)
Orange line: Regardless of safety (Public or unconfidential information is exchanged through general public route)
Dark gray line: Secure (Destination is restricted by IP restrictions etc.)
Light gray line: Additional (Traffics to additional resources)
Dashed line: Outbound traffic to external actors

Note: 'Network wide' resources, such as subnets, do not appear in the drawing. In addition, additional resources like parameter groups attached to the DB server are displayed as (Complementary resources) with small icons.

5. Click each connection or nodes to select the relevant actor or resource in the report on the left lists.

6. When you click each context, you can check related resources and actors in the diagram.

7. In the diagram on the right of the screen, resources and actors that are not related to the context are transparent. However, the usage name, performance (rps), estimated price, and various information displayed at the top of each resource are the sum of all context information, not context-specific information.

3.Users

ForkMe! calls cloud users "actors". Actors are classified into three types: an unspecified number of "market" types, specified "individual" types such as operators, and "external system" types such as linked APIs. Details can be found on the "Actors" tab of the report.


Market

1. Select the "Actors" tab on the report.

2. An item with the globe icon is "market" type actor. Represents an unspecified number of users.

3. Click the item to see the details.

Calculation basis: The calculation basis of the user, expressed as market size x share. Details of the market size are displayed in the blue frame below.
Market title: The name of the market.
Market size: The number of people in the market.
Market description: A description of the market.
Author: The name of the person or organization that defined the market.
Date: The day when the market was defined.
"Jump to code" button: In the code editor on the right, the code that defines this market is selected.

4. Clicking "Open related contexts" above the details will take you to the Contexts tab where the context associated with this user will be selected. Click "Jump to code" and the code editor on the right will select the code that defines this user.


Individual

1. Select the "ACTORS" tab on the report.

2. An item with an address book icon is "Individual" type actor. Represents a specific user, such as an operations person.

3. Click the item to see the details. If the "Jump to code" button is displayed in "Groups such as IP Address / Domain", click it to select the description location of the code editor. If the same group name is used by multiple users, they will be selected by rotation each time they are clicked.

4. Clicking "Open related contexts" above the details will take you to the "CONTEXTS" tab where the context associated with this user will be selected. Click "Jump to code" and the code editor on the right will select the code that defines this user.


External system

1. Select the "ACTORS" tab for on the report.

2. An items with a robot icon is "external system" type actors. Represents a specific external system, such as an API to work with.

3. Click the item to see the details. If the "Jump to code" button is displayed in "Groups such as IP Address / Domain", click it to select the description location of the code editor. If the same group name is used by multiple users, they will be selected by rotation each time they are clicked.。

4. Clicking "Open related contexts" above the details will take you to the "CONTEXTS" tab where the context associated with this user will be selected. Click "Jump to code" and the code editor on the right will select the code that defines this user.

4. System resources

ForkMe! calls cloud servers and various services "RESOURCES". The types of resources vary from cloud vendor to cloud vendor and are diverse. Details can be found on the "RESOURCES" tab of the report.


Resource

1. Select the "RESOURCES" tab for on the report.

2. A summary of each resource is listed.

1st line: The resource name set by the designer.
2nd line: Resource ID. It is used when referencing resources in the design.
3rd line: Resource type code defined by each cloud vendor.
Max throughput: Maximum required performance for resources.
Roughly cost: Roughly cost. Click the "?" Mark to check the prerequisites for calculation.

3. Click the item to see the details.

Type: A resource type code defined by each cloud vendor.
Throughput: Required performance.
Data Transfer In: The amount of data received.
Data Transfer Out: The amount of data to be sent.
Requests: The number of requests to receive.
Storage: This is the amount of data that is stored in the resource out of the amount of received data.
Cost details: It is detail of cost.

4. Clicking "Open related contexts" above the details will take you to the "CONTEXTS" tab where the context associated with this user will be selected. Click "Jump to code" and the code editor on the right will select the code that defines this user.

Appendix


ForkMe! and Reindeer


ForkMe! is provided by Reindeer Technology PTE. LTD.
Reindeer wants to reach out to all people by supporting the use of the cloud.
A society in which anyone can create services on their own will bring freedom of expression and diversity of values. We also believe that it promotes the redistribution of wealth to all and brings equal wealth and well-being to people around the world.


ForkMe!

Reindeer Technology PTE. LTD.



Trademarks

*Amazon Web Services and other AWS trademarks are trademarks of Amazon.com, Inc. or its affiliates in the United States and other countries.
*Google and Google Cloud Platform (GCP) is a registered trademark or trademarks of Google LLC.
*Micosoft and Microsoft Azure are registered trademarks or trademarks of Microsoft Corporation in the United States and other countries.
*Terraform is a registered trademark of HashiCorp, Inc.
*All other product names mentioned herein may be trademarks or registered trademarks of their respective companies.