I find your question strange because, unless you have a specific architectural problem , which you don't, AFAIK, you shouldn't try to force patterns in your code. Write code that is testable then refactor if needed. Don't try to force a specific pattern just because "patterns".
Now if you are looking for patterns for the sake of patterns Microsoft has extensive documentation of enterprise patterns : https://msdn.microsoft.com/en-us/library/ff648419.aspx as well as Martin Fowler : http://martinfowler.com/eaaCatalog/index.html Something that would be useful for everybody next time is you actually coming with a piece of code that works then asking for ways to refactor that piece of code. Le vendredi 19 août 2016 16:08:04 UTC+2, Asit Dhal a écrit : > > Hi All, > > I need to build an application that accesses a small database(sqlite or > may be mysql in production). > > My database operations are very small, like > 1. Insert > 2. Read > 3. Search > > Insert is one time, and most of the time new records will be added in a > batch. > > Can someone suggest me some application design pattern(a tutorial or > github repo) for small database access ? > > > Warm Regards, > Asit Dhal > http://bit.ly/193ASIT > -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
