Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [kapua-dev] [Design Note] Kapua Directory Layout
Hi Jens,
    comments inline below.

On Aug 21, 2017, at 9:25 AM, Jens Reimann <jreimann@xxxxxxxxxx> wrote:

Hello Marco,

thanks for migrating this to the google document. I guess for some high level topics the mailing list still is better.

1) I am not really convinced that the current layout is that flawed to justify a full re-structuring, restructuring effectively means loosing the history on GitHub.

My understanding is that as long as we move the files with no rename, git history can be preserved.


2) I couldn't find any explanation of my previous point #2 in the introduction, maybe you I overlooked it and you can point me towards it. Because from what I understood the grouping will be based on the deployment bundles (microservices) and that may change in the future.

Here is the paragraph on this topic in the document:
• The current Kapua architecture has 8 service modules identified. The proposal is to start with those directories. If more service modules are added in the future or existing service modules are further decomposed, new directories will be added. For the Kapua 1.0 release, the output of the projects under this directory is service jar files that are packaged into the distribution of the Kapua apps. For future Kapua releases, the output of the projects under this directory can evolve to a Docker image for the micro-service associated with the service module.

3) Looking at "Service Directory Proposed Layout" and "Example Service Directory Proposed Layout" it looks to me as if the proposed layout doesn't really work. At least in the example there are more exceptions than standard cases.

I saw your comments on the auth service.
In general, each directory under services is a service module. 
A service module is the bounded context of the microservice so it can have more service endpoints if necessary.


I would suggest to do a full breakdown (mapping table), from old to new, so that we can understand what the proposal actually is. Because right now I don't see how modules (like broker-core, dev-tools, sso, transport, …) would be match the proposed ruleset. I guess actually doing this in a spreadsheet might clear up a few questions.

The bullet list in the document is an attempt for the new map; broker-core is under apps, dev-tools under util, transport under libraries. 
I misses sso which should be under libraries if used by multiple services. 

I reformat it into a spreadsheet as suggested.

Thanks
-Marco



Cheers

Jens

On Fri, Aug 18, 2017 at 6:44 PM, Carrer, Marco <marco.carrer@xxxxxxxxxxxx> wrote:
Jens,
    thanks for the comments.

I moved the wiki page to a pubic google document available for comments here:

I also expanded in the introduction addressing your questions.

Comments are welcome.

Ciao
-Marco


Hi,

I am not sure the Wiki is a good place for working on a design like that. There is no real way do amend or comment on GitHub wiki pages.
So I would like to understand two things here:

1) What is the benefit of re-organizing this?
2) What will happen if we decide in the future that the split up services in a different way?

Cheers

Jens

-- 
Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
phone: +49 89 2050 71286


Marco Carrer | CTO | EUROTECH | direct +39 0433 485 427 | mobile +39 346 4753123






_______________________________________________
kapua-dev mailing list
kapua-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kapua-dev




--
Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
phone: +49 89 2050 71286
_____________________________________________________________________________

Red Hat GmbH, www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill
_______________________________________________
kapua-dev mailing list
kapua-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kapua-dev

Back to the top