Service Design Specification

clonesahibinden-listingimage-service documentation Version: 1.0.1

Scope

This document provides a structured architectural overview of the listingImage 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:

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.

ListingImage Service Settings

Manages uploading, linking, ordering, and storing all images attached to classified listings. Enforces image file format, size, count, and metadata standards; supports multi-resolution handling and per-listing image count limits.

Service Overview

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

The following routes are available by default:

The service uses a PostgreSQL database for data storage, with the database name set to clonesahibinden-listingimage-service.

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

Authentication & Security

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 clonesahibinden-listingimage-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
listingImage Stores metadata about each image attached to a classified listing, with enforced image count, format, size, and dimension constraints. Four separate URL fields for different resolutions. Tied to listing; managed by listing owner/admin/mod. accessProtected

listingImage Data Object

Object Overview

Description: Stores metadata about each image attached to a classified listing, with enforced image count, format, size, and dimension constraints. Four separate URL fields for different resolutions. Tied to listing; managed by listing owner/admin/mod.

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

Composite Indexes

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: doUpdate

The existing record will be updated with the new data.No error will be thrown.

Properties Schema

Property Type Required Description
fileSize Integer Yes Size of the image file in bytes.
fullUrl String Yes URL to a full-res processed but possibly optimized image (e.g. with max side 1600px, for gallery display).
height Float Yes Height of the original image, in pixels.
listingId ID Yes The related listing that this image belongs to.
mediumUrl String Yes URL to the medium-sized processed image version (e.g. 400x300px or similar).
mimeType String Yes MIME type of the image (e.g., image/jpeg, image/png, image/webp, image/gif).
sortOrder Integer Yes Order value for display in UI; the lowest value image is the cover/main image.
thumbnailUrl String Yes URL to the thumbnail image (small size, e.g. 120x90px).
uploadedAt Date Yes UTC timestamp when image was uploaded to platform.
url String Yes URL to the original uploaded image file (full resolution/original).
width Float Yes Width of the original image, in pixels.

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.

Constant Properties

fileSize fullUrl height listingId mediumUrl mimeType thumbnailUrl uploadedAt url width

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

fileSize fullUrl height listingId mediumUrl mimeType sortOrder thumbnailUrl url width

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.

Elastic Search Indexing

listingId sortOrder uploadedAt url

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

listingId sortOrder

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

listingId

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

listingId

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.

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

Filter Properties

listingId

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.

Business Logic

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

Edge Controllers

m2mCreateListingImage

Configuration:

REST Settings:

m2mBulkCreateListingImage

Configuration:

REST Settings:

m2mUpdateListingImageById

Configuration:

REST Settings:

m2mDeleteListingImageById

Configuration:

REST Settings:

m2mUpdateListingImageByQuery

Configuration:

REST Settings:

m2mDeleteListingImageByQuery

Configuration:

REST Settings:

m2mUpdateListingImageByIdList

Configuration:

REST Settings:

Service Library

Functions

validateImageUpload.js

// Validates image upload constraints (for create/update)
// context = API context; expects fileSize, mimeType, width, height, imageCount (if create), max images per listing = 10
const ALLOWED_MIME = ['image/jpeg','image/png','image/webp','image/gif'];
const MIN_WIDTH = 400, MIN_HEIGHT = 300, MAX_FILE_SIZE = 10 * 1024 * 1024, MAX_IMAGES = 10;
module.exports = function validateImageUpload(context) {
  // Check required file properties present
  const { fileSize, mimeType, width, height, imageCount } = context;
  if (mimeType && !ALLOWED_MIME.includes(mimeType))
    throw new Error('Unsupported image type. Allowed: JPEG, PNG, WEBP, GIF.');
  if (fileSize && fileSize > MAX_FILE_SIZE)
    throw new Error('Image file exceeds 10MB limit.');
  if (width && width < MIN_WIDTH)
    throw new Error('Image width must be at least 400px.');
  if (height && height < MIN_HEIGHT)
    throw new Error('Image height must be at least 300px.');
  // Check image count only on create
  if (typeof imageCount === 'number' && imageCount >= MAX_IMAGES)
    throw new Error('Cannot add more than 10 images per listing.');
  return true;
}

Hook Functions

No hook functions defined.

Edge Functions

m2mCreateListingImage.js

module.exports = async (request) => {
        const { createListingImage } = require("dbLayer");
        const context = { session: request.session, requestId: request.requestId };
        const data = request.body?.data || request.data || request;
        const result = await createListingImage(data, context);
        return { status: 200, content: result };
      }

m2mBulkCreateListingImage.js

module.exports = async (request) => {
        const { createBulkListingImage } = require("dbLayer");
        const context = { session: request.session, requestId: request.requestId };
        const dataList = request.body?.dataList || request.dataList || (Array.isArray(request.body) ? request.body : [request.body]);
        if (!Array.isArray(dataList) || dataList.length === 0) {
          return { status: 400, message: "dataList must be a non-empty array" };
        }
        const result = await createBulkListingImage(dataList, context);
        return { status: 200, content: result };
      }

m2mUpdateListingImageById.js

module.exports = async (request) => {
        const { updateListingImageById } = require("dbLayer");
        const context = { session: request.session, requestId: request.requestId };
        const id = request.body?.id || request.params?.id || request.id;
        const dataClause = request.body?.dataClause || request.dataClause || request.body;
        if (dataClause && dataClause.id) delete dataClause.id;
        if (!id) {
          return { status: 400, message: "ID is required" };
        }
        const result = await updateListingImageById(id, dataClause, context);
        return { status: 200, content: result };
      }

m2mDeleteListingImageById.js

module.exports = async (request) => {
        const { deleteListingImageById } = require("dbLayer");
        const context = { session: request.session, requestId: request.requestId };
        const id = request.body?.id || request.params?.id || request.id;
        if (!id) {
          return { status: 400, message: "ID is required" };
        }
        const result = await deleteListingImageById(id, context);
        return { status: 200, content: result };
      }

m2mUpdateListingImageByQuery.js 

module.exports = async (request) => {
        const { updateListingImageByQuery } = require("dbLayer");
        const context = { session: request.session, requestId: request.requestId };
        const dataClause = request.body?.dataClause || request.dataClause || request.body;
        const query = request.body?.query || request.query || {};
        if (!query || typeof query !== "object" || Object.keys(query).length === 0) {
          return { status: 400, message: "Query is required and must be a non-empty object" };
        }
        const result = await updateListingImageByQuery(dataClause, query, context);
        return { status: 200, content: result };
      }

m2mDeleteListingImageByQuery.js 

module.exports = async (request) => {
        const { deleteListingImageByQuery } = require("dbLayer");
        const context = { session: request.session, requestId: request.requestId };
        const query = request.body?.query || request.query || {};
        if (!query || typeof query !== "object" || Object.keys(query).length === 0) {
          return { status: 400, message: "Query is required and must be a non-empty object" };
        }
        const result = await deleteListingImageByQuery(query, context);
        return { status: 200, content: result };
      }

m2mUpdateListingImageByIdList.js 

module.exports = async (request) => {
        const { updateListingImageByIdList } = require("dbLayer");
        const context = { session: request.session, requestId: request.requestId };
        const idList = request.body?.idList || request.idList || [];
        const dataClause = request.body?.dataClause || request.dataClause || request.body;
        if (dataClause && dataClause.idList) delete dataClause.idList;
        if (!Array.isArray(idList) || idList.length === 0) {
          return { status: 400, message: "idList must be a non-empty array" };
        }
        const result = await updateListingImageByIdList(idList, dataClause, context);
        return { status: 200, content: result };
      }

Templates

No templates defined.

Assets

No assets defined.

Public Assets

No public assets defined.

Event Emission

Integration Patterns

Deployment Considerations

Environment Configuration

Implementation Guidelines

Development Workflow

  1. Data Model Implementation: Generate database schema from data object definitions
  2. CRUD Route Generation: Implement auto-generated routes with custom logic
  3. Custom Logic Integration: Implement hook functions and edge functions
  4. Authentication Integration: Configure with project-level authentication
  5. Testing: Unit and integration testing for all components

Code Generation Expectations

Custom Code Integration Points

Testing Strategy

Unit Testing

Integration Testing

Performance Testing

Appendices

Data Type Reference

Type Description Storage
ID Unique identifier UUID (SQL) / ObjectID (NoSQL)
String Short text (≤255 chars) VARCHAR
Text Long-form text TEXT
Integer 32-bit whole numbers INT
Boolean True/false values BOOLEAN
Double 64-bit floating point DOUBLE
Float 32-bit floating point FLOAT
Short 16-bit integers SMALLINT
Object JSON object JSONB (PostgreSQL) / Object (MongoDB)
Date ISO 8601 timestamp TIMESTAMP
Enum Fixed numeric values SMALLINT with lookup

Enum Value Mappings

Request Locations

HTTP Methods

Edge Function Signature

async function edgeFunction(request) {
  // Custom request processing
  // Return response object or throw error
  return {
    data: {},
    status: 200,
    message: "Success"
  };
}

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