Elegance is Not My Middle Name!

Free AI web copilot to create summaries, insights and extended knowledge, download it at here

4376

Abstract

private readonly paymentService: PaymentService, private readonly moderationService: ModerationService ) {}

<span class="hljs-variable language_">this</span>.<span class="hljs-property">reputationService</span>.<span class="hljs-title function_">increaseReputation</span>(args.<span class="hljs-property">userId</span>);
<span class="hljs-variable language_">this</span>.<span class="hljs-property">notificationService</span>.<span class="hljs-title function_">notifyFollowersAboutPost</span>(post);
<span class="hljs-variable language_">this</span>.<span class="hljs-property">userService</span>.<span class="hljs-title function_">updateUserActivity</span>(<span class="hljs-string">'post.created'</span>, post);
<span class="hljs-variable language_">this</span>.<span class="hljs-property">trackingService</span>.<span class="hljs-title function_">registerTrackable</span>(<span class="hljs-string">'post'</span>, post);
<span class="hljs-variable language_">this</span>.<span class="hljs-property">moderationService</span>.<span class="hljs-title function_">checkPostContentForViolations</span>(post.<span class="hljs-property">content</span>);    

<span class="hljs-keyword">if</span> (args.<span class="hljs-property">isPremium</span>) {
  <span class="hljs-variable language_">this</span>.<span class="hljs-property">paymentService</span>.<span class="hljs-title function_">chargeUserForPremiumPost</span>(args.<span class="hljs-property">userId</span>);
}

<span class="hljs-keyword">return</span> post;

} }</pre></div>This example is obviously made up, so please don’t pay too much attention to the details. I just want you to notice how many services <code>PostService</code> is dependent on and imagine that these services may also be dependent on PostService. For example, the notification service may require additional data from the post service to dispatch notifications, or the <code>ModerationService</code> may need to modify the post again via <code>PostService</code> after moderation. This is where circular dependencies occur.So now that we have a grasp of the problem, let’s explore the solution that I want to propose.<h1 id="c471">The solution</h1>The solution I want to propose for this problem is to use the well-known concept of Event-Driven Architecture. Instead of calling all subsequent actions from the <code>createPost</code> method, we will simply create the post there and emit an event. Then, any module interested in performing some action related to the event may do so without crossing its logical borders.NestJS already comes with handy tools that we can use to benefit from events. If you don't yet have the package installed, you can simply add <code>@nestjs/event-emitter</code> to your application.<div id="9629"><pre>yarn add @nestjs/event-emitter</pre></div>And when the package is installed, add the <code>EventEmitterModule</code> to the root module of your application.<div id="e0ec"><pre>import { Module } from '@nestjs/common'; import { EventEmitterModule } from '@nestjs/event-emitter';

@Module({ imports: [ EventEmitterModule.forRoot(), // ... ], }) export class AppModule {}</pre></div>When we have it ready, we may simply ge

Options

t rid of all <code>PostService</code> dependencies and replace them with only one — <code>EventEmitter2</code>. After this, we may also remove subsequent method invocations from the <code>createPost</code> method and instead emit an event with its key and payload. The payload may be defined as a separate interface or class if you wish, but here, for presentation purposes, I will just emit the created post as a payload.<div id="86c2"><pre>class PostsService { constructor(private eventEmitter: EventEmitter2) {}

public createPost(args: CreatePostArgs): Post { const post = this.db.posts.create({ ... }); this.eventEmitter.emit('post.created', post);

<span class="hljs-keyword">return</span> post;

} }</pre></div>The last thing we have to do is to add a listener to the modules that may be interested in this event. For example, in the notification module, we may have a listener as below. In the other modules, the code will be pretty much the same, just other services will be involved in event handling.<div id="c0ad"><pre>class NotificationsListener { constructor( private readonly notificationsService: NotificationsService ) {}

@OnEvent('post.created') handlePostCreated(post: Post) { this.reputationService.notifyFollowersAboutPost(post); } }</pre></div>This way, the <code>NotificationService</code> and <code>PostService</code> are only loosely coupled now. The <code>PostService</code> is no longer dependent on <code>NotificationService</code>. We get rid of circular dependency here, yet we keep the functionality still working — Yay!<h1 id="ea7f">Summary</h1>To sum up, in this article we explored the proposition of introducing events into your application to solve the issue of circular dependencies. This approach helps modules to stay within their borders yet react to actions performed in another module as well. Even though this way may not be applicable to all solutions it definitely may fix the one presented today.I want to say thank you to all who read this article. I would love to hear your thoughts about this proposal and your ways of tackling circular dependencies in your applications, so feel free to share.Don’t forget to check out my other articles for more tips and insights. Happy hacking!<h1 id="7cf6">Stackademic 🎓</h1>Thank you for reading until the end. Before you go:<ul><li>Please consider clapping and following the writer! 👏</li><li>Follow us <a href="https://twitter.com/stackademichq">X</a> | <a href="https://www.linkedin.com/company/stackademic">LinkedIn</a> | <a href="https://www.youtube.com/c/stackademic">YouTube</a> | <a href="https://discord.gg/in-plain-english-709094664682340443">Discord</a></li><li>Visit our other platforms: <a href="https://plainenglish.io">In Plain English</a> | <a href="https://cofeed.app/">CoFeed</a> | <a href="https://venturemagazine.net/">Venture</a> | <a href="https://blog.cubed.run">Cubed</a></li><li>More content at <a href="https://stackademic.com">Stackademic.com</a></li></ul></article></body>

Elegance is Not My Middle Name!

Here’s why

Elegance is My Middle Name

A statement that speaks for itself.

This Elegant Universe

Haiku/Tanka prompt “elegant ”.