Skip to main content
Tweeted twitter.com/StackSoftEng/status/1334829880425508871
added 25 characters in body
Source Link

I'm designing an editor as a desktop application that opens, saves and saves as documents from files, something very common in fact.
I already have Bounded Contexts for my business rules.

Naively, I want to put the paths of the files used to re-hydrate entities as their identities and implement the repositories with file access and management.
But I have the feeling that it's not the right way to manage the file aspect in my application.

So, do you think it may be interesting to design a Bounded Context dedicated to file management?
Do you have examples of such applications mixing DDD and file management?

Most examples show databases access through repositories and I was not able to find anything about that so far.

I'm designing an editor that opens, saves and saves as documents from files, something very common in fact.
I already have Bounded Contexts for my business rules.

Naively, I want to put the paths of the files used to re-hydrate entities as their identities and implement the repositories with file access and management.
But I have the feeling that it's not the right way to manage the file aspect in my application.

So, do you think it may be interesting to design a Bounded Context dedicated to file management?
Do you have examples of such applications mixing DDD and file management?

Most examples show databases access through repositories and I was not able to find anything about that so far.

I'm designing an editor as a desktop application that opens, saves and saves as documents from files, something very common in fact.
I already have Bounded Contexts for my business rules.

Naively, I want to put the paths of the files used to re-hydrate entities as their identities and implement the repositories with file access and management.
But I have the feeling that it's not the right way to manage the file aspect in my application.

So, do you think it may be interesting to design a Bounded Context dedicated to file management?
Do you have examples of such applications mixing DDD and file management?

Most examples show databases access through repositories and I was not able to find anything about that so far.

Source Link

In DDD, is it worth it to define a Bounded Context for file access?

I'm designing an editor that opens, saves and saves as documents from files, something very common in fact.
I already have Bounded Contexts for my business rules.

Naively, I want to put the paths of the files used to re-hydrate entities as their identities and implement the repositories with file access and management.
But I have the feeling that it's not the right way to manage the file aspect in my application.

So, do you think it may be interesting to design a Bounded Context dedicated to file management?
Do you have examples of such applications mixing DDD and file management?

Most examples show databases access through repositories and I was not able to find anything about that so far.