Clean architecture best practices / patterns.

[Mohamedh Fazal]

Hello Gophers,

I'm  practicing creating clean application architectures in Go and I have many questions. 

I have a little practice project up on Github at https://github.com/faxal/cleanarch after reading this http://blog.8thlight.com/uncle-bob/2012/08/13/the-clean-architecture.html

I feel I have not completely grasped the idea.

I want to know if I'm doing it right from an architectural point of view (ignore the crawler part, I was just testing RPC stuff). 

I have abstracted away the storage so I can easily switch 

between different implementations. I have two implementations, one that stores and retrieves from an SQLite table and the other stores and retrieves from a hash table.

So to summarize questions:

1. Is this the right direction and is it mostly idiomatic Go (I'm also learning Go)?
2. Is there any harm in referring to structures multiple levels deep? For example can I refer to data structures in Entities layer, from the presentation layer?
3. Would be grateful if one could point me to a good resource(s) / book(s) etc.

[Francesc Campoy Flores]

Manuel Kiessling wrote a very nice article on this.

http://manuel.kiessling.net/2012/09/28/applying-the-clean-architecture-to-go-applications/

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

--

Francesc Campoy

http://campoy.cat

[Mohamedh Fazal]

Thanks for linking to this. I did come across that while I was searching. For some reason I got sidetracked and did not get to read it. Hopefully it will clear some doubts.