# Architectural papers

**URL:** <https://forums.mobyproject.org/t/architectural-papers/293>\
**Category:** Architecture\
**Tags:** integration\
**Created:** [April 6, 2018, 12:49pm UTC](https://forums.mobyproject.org/t/architectural-papers/293 "2018-04-06T12:49:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pcittadini](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.mobyproject.org/pcittadini/32/143_2.png) [@pcittadini](https://forums.mobyproject.org/u/pcittadini)\
**Post date:** [April 6, 2018, 12:49pm UTC](https://forums.mobyproject.org/t/architectural-papers/293/1 "2018-04-06T12:49:37Z")

</div>

Hi all,  
I was just wondering if there is a place where I can find some architectural specs for people that want to start contributing and diving into the projects.  
I am really interested on how components are talking each other (at least from a logic pov), material/documentation of any sort might help getting more contributors onboard.

Thanks

---

<div class="post-metadata">

**Author:** ![foxxxyben](https://yyz1.discourse-cdn.com/flex031/user_avatar/forums.mobyproject.org/foxxxyben/32/145_2.png) [@foxxxyben](https://forums.mobyproject.org/u/foxxxyben)\
**Post date:** [April 12, 2018, 6:01pm UTC](https://forums.mobyproject.org/t/architectural-papers/293/2 "2018-04-12T18:01:49Z")

</div>

I second this request. I had to do a LOT of digging in order to make sense of how everything relates to the API: Protobufs might be great for cross-language interfaces, but being automatically generated, and with such a variety of generation options, it makes readability of the resulting Go code a bit hard to follow. Working with the API from an outsider’s perspective can be quite discouraging.