<p>One could also create libraries and call them using a dependency manager like a package.json if node is used or ivy if the code is written in java.</p>

CC BY-SA 3.0
2017-10-17T18:11:41.630Z
But what does this mean to repo layout?
Ta Mu
CC BY-SA 3.0
2017-10-17T15:17:05.423Z
2017-10-17T15:17:05.423Z
030
<p>With Atlassian BitBucket, you can have:</p>

<ul>
<li>Projects, which incorporate..</li>
<li>Source code repositories.</li>
</ul>

<p>Now, you could have a microservices with more than just one codebase and need therefore more than just repository. What is the best practice to reflect this if you have many different projects?</p>

<p>My idea now is to encode microservice prefixes to repository names, but is this really the way to go?</p>

<p>Like:</p>

<ul>
<li>Project A

<ul>
<li>service1.repo1</li>
<li>service1.repo2</li>
<li>service2.repo1</li>
</ul></li>
<li>Project B

<ul>
<li>serviceN.repoX</li>
</ul></li>
</ul>

CC BY-SA 3.0
2017-12-17T13:37:18.360Z
Can you give concrete examples?
AnoE
CC BY-SA 3.0
2017-12-17T19:04:02.067Z
They are given above
Ta Mu
<bitbucket><methodology>
Proper mapping for service architectures, Docker and BitBucket mapping - how do you do it?
Ta Mu
# Proper mapping for service architectures, Docker and BitBucket mapping - how do you do it?

(Asked by: username_0 on 2017-10-17)

With Atlassian BitBucket, you can have:

* Projects, which incorporate..
* Source code repositories.

Now, you could have a microservices with more than just one codebase and need therefore more than just repository. What is the best practice to reflect this if you have many different projects?

My idea now is to encode microservice prefixes to repository names, but is this really the way to go?

Like:

* Project A
  + service1.repo1
  + service1.repo2
  + service2.repo1
* Project B
  + serviceN.repoX

**Tags:** bitbucket, methodology

> **Comments:**
> **username_1**: Can you give concrete examples?  
> **username_0**: They are given above  

---

## 1 answers

### Answer by username_2 on 2017-10-17. Score: 1

One could also create libraries and call them using a dependency manager like a package.json if node is used or ivy if the code is written in java.

> **Comments:**
> **username_0**: But what does this mean to repo layout?  

---

