# Service Design Specification
**linkedin-networking-service** documentation
**Version:** `1.0.0`

## Scope

This document provides a structured architectural overview of the `networking` microservice, detailing its configuration, data model, authorization logic, business rules, and API design. It has been automatically generated based on the service definition within Mindbricks, ensuring that the information reflects the source of truth used during code generation and deployment.

The document is intended to serve multiple audiences:

* **Service architects** can use it to validate design decisions and ensure alignment with broader architectural goals.
* **Developers and maintainers** will find it useful for understanding the structure and behavior of the service, facilitating easier debugging, feature extension, and integration with other systems.
* **Stakeholders and reviewers** can use it to gain a clear understanding of the service's capabilities and domain logic.

> **Note for Frontend Developers**: While this document is valuable for understanding business logic and data interactions, please refer to the [Service API Documentation](#) for endpoint-level specifications and integration details.

> **Note for Backend Developers**: Since the code for this service is automatically generated by Mindbricks, you typically won't need to implement or modify it manually. However, this document is especially valuable when you're building other services—whether within Mindbricks or externally—that need to interact with or depend on this service. It provides a clear reference to the service's data contracts, business rules, and API structure, helping ensure compatibility and correct integration.



## `Networking` Service Settings

Handles professional networking logic for user-to-user connections: manages connection requests, accepted relationships, listing/removal, permissions, and state transitions. Publishes connection lifecycle events for notification...

### Service Overview

This service is configured to listen for HTTP requests on port `3001`, 
serving both the main API interface and default administrative endpoints.

The following routes are available by default:

* **API Test Interface (API Face):** `/`
* **Swagger Documentation:** `/swagger`
* **Postman Collection Download:** `/getPostmanCollection`
* **Health Checks:** `/health` and `/admin/health`
* **Current Session Info:** `/currentuser`
* **Favicon:** `/favicon.ico`

The service uses a **PostgreSQL** database for data storage, with the database name set to `linkedin-networking-service`.

This service is accessible via the following environment-specific URLs:

* **Preview:** `https://linkedin.prw.mindbricks.com/networking-api`
* **Staging:** `https://linkedin-stage.mindbricks.co/networking-api`
* **Production:** `https://linkedin.mindbricks.co/networking-api`

                                 

### Authentication & Security
- **Login Required**: Yes

This service requires user authentication for access. It supports both JWT and RSA-based authentication mechanisms, ensuring secure user sessions and data integrity.
If a crud route also is configured to require login, 
it will check a valid JWT token in the request query/header/bearer/cookie. If the token is valid, it will extract the user information from the token and make the fetched session data available in the request context.

  
### Service Data Objects
The service uses a **PostgreSQL** database for data storage, with the database name set to `linkedin-networking-service`.

Data deletion is managed using a **soft delete** strategy. Instead of removing records from the database, they are flagged as inactive by setting the `isActive` field to `false`.



| Object Name | Description | Public Access |
|-------------|-------------|---------------|
| `connection` | Represents a single established user-to-user professional relationship (mutual connection). One record per unordered user pair, deleted on disconnect.. | accessPrivate | 
| `connectionRequest` | Tracks a user's request to connect with another user, supporting request/accept/reject/cancel, with audit timestamps. | accessPrivate | 




## connection Data Object

### Object Overview
**Description:** Represents a single established user-to-user professional relationship (mutual connection). One record per unordered user pair, deleted on disconnect..

This object represents a core data structure within the service and acts as the blueprint for database interaction, API generation, and business logic enforcement. 
It is defined using the `ObjectSettings` pattern, which governs its behavior, access control, caching strategy, and integration points with other systems such as Stripe and Redis.

### Core Configuration
- **Soft Delete:** Enabled — Determines whether records are marked inactive (`isActive = false`) instead of being physically deleted.
- **Public Access:** accessPrivate — If enabled, anonymous users may access this object’s data depending on API-level rules.




### Composite Indexes

- **uniqueUsersPair**: [userId1, userId2] 
This composite index is defined to optimize query performance for complex queries involving multiple fields.

The index also defines a conflict resolution strategy for duplicate key violations.

When a new record would violate this composite index, the following action will be taken:

**On Duplicate**: `throwError`

An error will be thrown, preventing the insertion of conflicting data.






### Properties Schema


| Property | Type | Required | Description |
|----------|------|----------|-------------|
| `connectedSince` | Date | Yes | - |
| `userId1` | ID | Yes | - |
| `userId2` | ID | Yes | - |
* Required properties are mandatory for creating objects and must be provided in the request body if no default value is set.



### Default Values
Default values are automatically assigned to properties when a new object is created, if no value is provided in the request body.
Since default values are applied on db level, they should be literal values, not expressions.If you want to use expressions, you can use transposed parameters in any business API to set default values dynamically.

- **connectedSince**: new Date()
- **userId1**: '00000000-0000-0000-0000-000000000000'
- **userId2**: '00000000-0000-0000-0000-000000000000'


### Constant Properties

`connectedSince` `userId1` `userId2`

Constant properties are defined to be immutable after creation, meaning they cannot be updated or changed once set. They are typically used for properties that should remain constant throughout the object's lifecycle.
A property is set to be constant if the `Allow Update` option is set to `false`.


 



 

 

### Elastic Search Indexing

`connectedSince` `userId1` `userId2`

Properties that are indexed in Elastic Search will be searchable via the Elastic Search API. 
While all properties are stored in the elastic search index of the data object, only those marked for Elastic Search indexing will be available for search queries.


### Database Indexing

`userId1` `userId2`

Properties that are indexed in the database will be optimized for query performance, allowing for faster data retrieval.
Make a property indexed in the database if you want to use it frequently in query filters or sorting.




### Cache Select Properties

`userId1` `userId2`

Cache select properties are used to collect data from Redis entity cache with a different key than the data object id.
This allows you to cache data that is not directly related to the data object id, but a frequently used filter.



### Relation Properties

`userId1` `userId2`

Mindbricks supports relations between data objects, allowing you to define how objects are linked together.
You can define relations in the data object properties, which will be used to create foreign key constraints in the database.
For complex joins operations, Mindbricks supportsa BFF pattern, where you can view dynamic and static views based on Elastic Search Indexes.
Use db level relations for simple one-to-one or one-to-many relationships, and use BFF views for complex joins that require multiple data objects to be joined together.

- **userId1**: ID
Relation to `user`.id

The target object is a parent object, meaning that the relation is a one-to-many relationship from target to this object.

On Delete: Set Null
Required: Yes

- **userId2**: ID
Relation to `user`.id

The target object is a parent object, meaning that the relation is a one-to-many relationship from target to this object.

On Delete: Set Null
Required: Yes




### Formula Properties

`connectedSince`

Formula properties are used to define calculated fields that derive their values from other properties or external data.
These properties are automatically calculated based on the defined formula and can be used for dynamic data retrieval.

- **connectedSince**: Date  
  - Formula: `new Date()`
  
  - Calculate After Instance: No
  






## connectionRequest Data Object

### Object Overview
**Description:** Tracks a user's request to connect with another user, supporting request/accept/reject/cancel, with audit timestamps.

This object represents a core data structure within the service and acts as the blueprint for database interaction, API generation, and business logic enforcement. 
It is defined using the `ObjectSettings` pattern, which governs its behavior, access control, caching strategy, and integration points with other systems such as Stripe and Redis.

### Core Configuration
- **Soft Delete:** Enabled — Determines whether records are marked inactive (`isActive = false`) instead of being physically deleted.
- **Public Access:** accessPrivate — If enabled, anonymous users may access this object’s data depending on API-level rules.




### Composite Indexes

- **uniqueConnectionRequestPair**: [senderUserId, receiverUserId] 
This composite index is defined to optimize query performance for complex queries involving multiple fields.

The index also defines a conflict resolution strategy for duplicate key violations.

When a new record would violate this composite index, the following action will be taken:

**On Duplicate**: `throwError`

An error will be thrown, preventing the insertion of conflicting data.






### Properties Schema


| Property | Type | Required | Description |
|----------|------|----------|-------------|
| `receiverUserId` | ID | Yes | - |
| `senderUserId` | ID | Yes | - |
| `sentAt` | Date | Yes | - |
| `status` | Enum | Yes | - |
| `respondedAt` | Date | No | - |
| `message` | String | No | - |
* Required properties are mandatory for creating objects and must be provided in the request body if no default value is set.



### Default Values
Default values are automatically assigned to properties when a new object is created, if no value is provided in the request body.
Since default values are applied on db level, they should be literal values, not expressions.If you want to use expressions, you can use transposed parameters in any business API to set default values dynamically.

- **receiverUserId**: '00000000-0000-0000-0000-000000000000'
- **senderUserId**: '00000000-0000-0000-0000-000000000000'
- **sentAt**: new Date()
- **status**: pending


### Constant Properties

`receiverUserId` `senderUserId` `sentAt` `message`

Constant properties are defined to be immutable after creation, meaning they cannot be updated or changed once set. They are typically used for properties that should remain constant throughout the object's lifecycle.
A property is set to be constant if the `Allow Update` option is set to `false`.


### Auto Update Properties

`status` `respondedAt`

An update crud API created with the option `Auto Params` enabled will automatically update these properties with the provided values in the request body. 
If you want to update any property in your own business logic not by user input, you can set the `Allow Auto Update` option to false.
These properties will be added to the update API's body parameters and can be updated by the user if any value is provided in the request body.

 


### Enum Properties
Enum properties are defined with a set of allowed values, ensuring that only valid options can be assigned to them. 
The enum options value will be stored as strings in the database, 
but when a data object is created an addtional property with the same name plus an idx suffix will be created, which will hold the index of the selected enum option.
You can use the index property to sort by the enum value or when your enum options represent a sequence of values.

- **status**: [pending, accepted, rejected]


 

 

### Elastic Search Indexing

`receiverUserId` `senderUserId` `sentAt` `status` `respondedAt` `message`

Properties that are indexed in Elastic Search will be searchable via the Elastic Search API. 
While all properties are stored in the elastic search index of the data object, only those marked for Elastic Search indexing will be available for search queries.


### Database Indexing

`receiverUserId` `senderUserId` `sentAt` `status`

Properties that are indexed in the database will be optimized for query performance, allowing for faster data retrieval.
Make a property indexed in the database if you want to use it frequently in query filters or sorting.




### Cache Select Properties

`receiverUserId` `senderUserId` `status`

Cache select properties are used to collect data from Redis entity cache with a different key than the data object id.
This allows you to cache data that is not directly related to the data object id, but a frequently used filter.



### Relation Properties

`receiverUserId` `senderUserId`

Mindbricks supports relations between data objects, allowing you to define how objects are linked together.
You can define relations in the data object properties, which will be used to create foreign key constraints in the database.
For complex joins operations, Mindbricks supportsa BFF pattern, where you can view dynamic and static views based on Elastic Search Indexes.
Use db level relations for simple one-to-one or one-to-many relationships, and use BFF views for complex joins that require multiple data objects to be joined together.

- **receiverUserId**: ID
Relation to `user`.id

The target object is a parent object, meaning that the relation is a one-to-many relationship from target to this object.

On Delete: Set Null
Required: Yes

- **senderUserId**: ID
Relation to `user`.id

The target object is a parent object, meaning that the relation is a one-to-many relationship from target to this object.

On Delete: Set Null
Required: Yes


### Session Data Properties

`senderUserId`

Session data properties are used to store data that is specific to the user session, allowing for personalized experiences and temporary data storage.
If a property is configured as session data, it will be automatically mapped to the related field in the user session during CRUD operations.
Note that session data properties can not be mutated by the user, but only by the system.

- **senderUserId**: ID property will be mapped to the session parameter `userId`.




### Formula Properties

`sentAt`

Formula properties are used to define calculated fields that derive their values from other properties or external data.
These properties are automatically calculated based on the defined formula and can be used for dynamic data retrieval.

- **sentAt**: Date  
  - Formula: `new Date()`
  
  - Calculate After Instance: No
  


### Filter Properties

`status`

Filter properties are used to define parameters that can be used in query filters, allowing for dynamic data retrieval based on user input or predefined criteria.
These properties are automatically mapped as API parameters in the listing API's that have "Auto Params" enabled.

- **status**: Enum  has a filter named `status`







## Business Logic



networking has got 9 Business APIs to manage its internal and crud logic. 
For the details of each business API refer to its chapter.

* [Create Connection](/businessLogic/createconnection)

* [Delete Connectionrequest](/businessLogic/deleteconnectionrequest)

* [Update Connectionrequest](/businessLogic/updateconnectionrequest)

* [List Connections](/businessLogic/listconnections)

* [List Connectionrequests](/businessLogic/listconnectionrequests)

* [Create Connectionrequest](/businessLogic/createconnectionrequest)

* [Delete Connection](/businessLogic/deleteconnection)

* [Get Connectionrequest](/businessLogic/getconnectionrequest)

* [Get Connection](/businessLogic/getconnection)















## Edge Controllers


### helloWorld

**Configuration:**
- **Function Name**: `helloWorld`
- **Login Required**: No

**REST Settings:**
- **Path**: `/helloworld`
- **Method**: 

---

### sendMail

**Configuration:**
- **Function Name**: `sendMail`
- **Login Required**: Yes

**REST Settings:**
- **Path**: `/sendmail`
- **Method**: 

---





## Service Library


### Functions

#### ensureNoDuplicateOrBlocked.js
```js
// Throws if: sender or receiver are the same, already connected, active request exists between these users
module.exports = async function ensureNoDuplicateOrBlocked(senderId, receiverId) {
  if (senderId === receiverId) throw new Error('Cannot connect to yourself.');
  // Check for existing connection
  const existing = await this.sequelize.models.connection.findOne({ where: { isActive: true, [this.sequelize.Op.or]: [ { userId1: senderId, userId2: receiverId }, { userId1: receiverId, userId2: senderId } ] } });
  if (existing) throw new Error('Users are already connected.');
  // Check for pending requests either direction
  const req = await this.sequelize.models.connectionRequest.findOne({ where: { isActive: true, status: 0, [this.sequelize.Op.or]: [ { senderUserId: senderId, receiverUserId: receiverId }, { senderUserId: receiverId, receiverUserId: senderId } ] } });
  if (req) throw new Error('Active connection request already exists.');
  return true;
}
```

#### ensureUpdateAllowed.js
```js
// Throws if sessionUserId is not receiver or status is not 'pending'.
module.exports = function ensureUpdateAllowed(sessionUserId, requestObject) {
  if (!requestObject) throw new Error('Request not found.');
  if (requestObject.status !== 0) throw new Error('Request already responded to.');
  if (requestObject.receiverUserId !== sessionUserId) throw new Error('Only the receiver can accept/reject this request.');
  return true;
};
```

#### ensureDeleteAllowed.js
```js
// Only sender or receiver may delete request.
module.exports = function ensureDeleteAllowed(sessionUserId, requestObject) {
  if (!requestObject) throw new Error('Request not found.');
  if (requestObject.senderUserId !== sessionUserId && requestObject.receiverUserId !== sessionUserId) {
    throw new Error('Unauthorized to delete this request.');
  }
  return true;
};
```

#### ensureDisconnectAllowed.js
```js
// User must be part of the connection (sessionUserId == userId1 or userId2)
module.exports = function ensureDisconnectAllowed(sessionUserId, otherUserId) {
  if (!sessionUserId || !otherUserId) throw new Error('Both users required.');
  if (sessionUserId === otherUserId) throw new Error('Cannot disconnect from yourself.');
  return true;
};
```




### Edge Functions

#### helloWorld.js
```js
module.exports = async (request) => { return { status: 200, message: "Hello from the networking edge function!", date: new Date().toISOString() }; }
```

#### sendMail.js
```js
module.exports = async (request) => { throw new Error('Not Implemented: Use notification microservice for emails.'); }
```










---

*This document was generated from the service architecture definition and should be kept in sync with implementation changes.*