---
title: "Comment by Denis Koltsov on \"Application or applications?\" | Hashnode"
description: "What can also justify multi-service approach is how your data flows and being processed, like if you have some data pipelines and such. Or also if you have some"
url: "https://hashnode.com/posts/application-or-applications/66413781614ca52dda3c7ddb/comment/66446e6f40c954095aa1ae2f"
---

[Discussion](https://hashnode.com/posts/application-or-applications/66413781614ca52dda3c7ddb)

Comment [Application or applications?](https://hashnode.com/posts/application-or-applications/66413781614ca52dda3c7ddb)

[Denis Koltsov](https://hashnode.com/@deniskoltsov)

[May 15, 2024](https://hashnode.com/posts/application-or-applications/66413781614ca52dda3c7ddb/comment/66446e6f40c954095aa1ae2f)

What can also justify multi-service approach is how your data flows and being processed, like if you have some data pipelines and such.

Or also if you have some potentially expensive processes that can kill the entire monolith — better put them into a separate service to achieve better redundancy.

[Dmytro Safonov](https://hashnode.com/@SafonovDmytro)

[May 15, 2024](https://hashnode.com/posts/application-or-applications/66413781614ca52dda3c7ddb/comment/66446e6f40c954095aa1ae2f#reply-664472ecad2e1957d13c4001)

It may depend if you have something working already or not. Because you can build data flow before you started development. In some cases there are limitations of engine or framework that dictates you data pipelines. But also really valid point that should be taken in consideration. Thanks.
