Hi everyone! First, thank you so much for this resource that helps me not to forget im

Another comment regarding "1.1 Structure your solutions by business components" about nodebestpractices HOT 1 OPEN

mindactuate commented on May 18, 2024

Another comment regarding "1.1 Structure your solutions by business components"

from nodebestpractices.

Comments (1)

mindactuate commented on May 18, 2024

Hi together, just a short update. I currently try to use the following concept:

my-system
|─ services (components, modules)
|   |-- config-service
|   |    |-- entry-points
|   |    |    |-- validators # here I validate for example the request body (using zod) and convert to JS objects
|   |    |    |-- config-code-server.ts # provides a simple object with methods from "the inner world" of the service
|   |    |    |-- config-http-routes.ts # my http routes that are registered with my fastify HTTP server
|   |    |-- data-access
|   |    |    |-- validators # some of the columns in my Postgres are json type, I use validators (zod) to convert to JS objects
|   |    |    |-- config-db.ts # my DB calls using Prisma
|   |    |-- business-logic (domain)
|   |    |    |-- get-config-use-case.ts # here I do something with the config from DB and return it to the entry point
|   |-- another-service
|   |    |-- entry-points
|   |    |    |-- validators
|   |    |    |-- another-code-server.ts
|   |    |    |-- another-http-routes.ts
|   |    |-- data-access
|   |    |    |-- another-db.ts
|   |    |-- business-logic (domain)
|   |    |    |-- clients
|   |    |    |    |-- validators
|   |    |    |    |-- config-client.ts # imports config-code-server and provides functions to the "inner world" of another service
|   |    |    |    |-- google-maps-client.ts
|   |    |    |-- another-use-case.ts
|   |

Here an example for my config-code-server.ts:

import {
  getActiveConfig,
  getAllConfigs
} from '../business-logic/get-config-use-case';

export {
  getActiveConfig,
  getAllConfigs
};

And here my config-client.ts:

import { Config } from '@prisma/client';
import * as configCodeServer from '../../../config-service/entry-points/config-code-server';

export async function getActiveConfig(): Promise<Config> {
  const config = await configCodeServer.getActiveConfig();
  return config;
}

export async function getAllConfigs(): Promise<Config[]> {
  const configs = await configCodeServer.getAllConfigs();
  return configs;
}

I can also write my code server a little more abstract like this:

import { Config } from '@prisma/client';
import {
  getActiveConfig,
  getAllConfigs
} from '../business-logic/get-config-use-case';

export async function getActiveConfig(): Promise<Config> {
  const config = await getActiveConfig();
  return config;
}

export async function getAllConfigs(): Promise<Config[]> {
  const configs = await getAllConfigs();
  return configs;
}

config-code-server.ts and config-client.ts look quite similar leading to redundancy (don't repeat yourself?!). But all in all it would be the same or perhaps even worse with microservices.

I can use the client within another-service like this

import * as ConfigClient from '../config-client'

async function anotherFunc(){
  //...
  const config = await ConfigClient.getActiveConfig();
  //...
}

How do you find this approach? I saw other approaches with messages being published to an (in memory or external) event bus. You can find information to this here: kamilgrzybek.com/blog/posts/modular-monolith-integration-styles I tried to implement the "direct call" approach.

Here is also a great video on that topic. Modular Monolith - How to build one & lessons learned, from Milan Jovanovic

from nodebestpractices.

Another comment regarding "1.1 Structure your solutions by business components" about nodebestpractices HOT 1 OPEN

Comments (1)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent