<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Rafael Holanda on Medium]]></title>
        <description><![CDATA[Stories by Rafael Holanda on Medium]]></description>
        <link>https://medium.com/@rafaelholanda90?source=rss-53581ac0d139------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2beJ9_dfqL9XrF-yI6KL8A.jpeg</url>
            <title>Stories by Rafael Holanda on Medium</title>
            <link>https://medium.com/@rafaelholanda90?source=rss-53581ac0d139------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 21:15:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rafaelholanda90/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Continuing looking for an ORM to database layer with Golang]]></title>
            <link>https://medium.com/@rafaelholanda90/continuing-looking-for-an-orm-to-database-layer-with-golang-7fee0316a989?source=rss-53581ac0d139------2</link>
            <guid isPermaLink="false">https://medium.com/p/7fee0316a989</guid>
            <category><![CDATA[database]]></category>
            <category><![CDATA[orm]]></category>
            <category><![CDATA[mysql]]></category>
            <category><![CDATA[gorm]]></category>
            <category><![CDATA[golang]]></category>
            <dc:creator><![CDATA[Rafael Holanda]]></dc:creator>
            <pubDate>Sat, 26 Sep 2020 23:33:26 GMT</pubDate>
            <atom:updated>2020-09-26T23:33:26.812Z</atom:updated>
            <content:encoded><![CDATA[<p>Continuing looking for an ORM to database layer with Golang</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bk4G3H8tt9PbquyE.jpg" /></figure><p>Previously, to find a better way to build a database layer with Golang using an ORM, a library API was built using the <a href="https://fs02.github.io/rel/#/">REL lib</a> on the database layer, as you can see below:</p><p><a href="https://medium.com/@rafaelholanda90/looking-for-an-orm-to-database-layer-with-golang-92e360d3a920">Looking for an ORM to database layer with Golang</a></p><p>To continue this journey and not choose the first option that appears, a new lib will be explored, and now the chosen lib was the most famous GORM:</p><p><a href="https://gorm.io/">GORM</a></p><p>As was described before in the <a href="https://medium.com/@rafaelholanda90/looking-for-an-orm-to-database-layer-with-golang-92e360d3a920">first article</a>, the library API has the four CRUD operations and now I will show you how I built the database layer using GORM as lib.</p><p>To map the routes of the API was chosen the <a href="https://github.com/go-chi/chi">chi</a> framework and the main function of the application will be:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/52c03631faf43284540d73d8daa272e4/href">https://medium.com/media/52c03631faf43284540d73d8daa272e4/href</a></iframe><p>Here I’m creating the repository that will have an instance of the database representation of GORM, and to create this instance it needs to pass the connection of the database and an instance of GORM configurations, here I’m only changing the log mode to be INFO to see all generated SQL:</p><pre>db, err := gorm.Open(mysql.Open(dsn), &amp;gorm.Config{  <br>  Logger: logger.Default.LogMode(logger.Info), <br>})</pre><p>But you can pass only an empty instance of gorm.Config if you want to use the default <a href="https://gorm.io/docs/gorm_config.html">configurations</a> of the GORM.</p><p>This instance of database it’s where I will use all the power that GORM provides to us, and I’m passing to the repository to be used inside of the database layer:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/69a877c1736e94b7d64bc211dd9f1d21/href">https://medium.com/media/69a877c1736e94b7d64bc211dd9f1d21/href</a></iframe><p>To start the database layer with GORM I had to map the entities as bellow:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2ef2996a8627e2b5ff56a3b338c83b85/href">https://medium.com/media/2ef2996a8627e2b5ff56a3b338c83b85/href</a></iframe><p>The GORM has a few options to map the entity, for example, to easily mapping commons columns like <em>ID</em>, <em>CreatedAt, UpdatedAt </em>and <em>DeletedAt</em>, you can use the <a href="https://gorm.io/docs/models.html#gorm-Model">gorm.Model</a>struct as the base of your struct and so not need to write these fields to all your entities as a declarative way. But here I have chosen to not use this option because I can’t manipulate how these fields will be exposed to JSON, so I do the mapping directly as you can see:</p><pre>package gorm</pre><pre>Model struct {  <br>  ID          uint           `gorm:&quot;primarykey&quot;`<br>  CreatedAt   time.Time<br>  UpdatedAt   time.Time        <br>  DeletedAt   gorm.DeletedAt `gorm:&quot;index&quot;`<br>}</pre><p>As the column <em>DeletedAt</em> can be null, so is used the gorm.DeletedAt struct that will manipulate correctly when this field is empty and will do a soft delete. This lib also fills these fields automatically and does not need to you fill in the creation. Here I only follow the same struct of the gorm.Model but the lib allows you other options that you can see on the documentation. Using the tag gorm:&quot;primarykey&quot; this mark what field has to map to the primary key of the table and using the tag gorm:&quot;index&quot; will mark the field as an index of the table on the database.</p><p>To map the relationship between the book table and the shelf table I had to map with the tag gorm:&quot;foreignkey:ShelfID&quot; on the field that contains the struct of the Shelf on the Book entity. And on the Shelf entity I only need to have the slice with the books that the lib will fill when using the Preload function when do the query.</p><p>All the names will be the same at snake case than the name of columns of the tables on the database and the name of the tables by default is pluralized, but here to attends the initial migration, I implement the function TableName() to customize the names of the tables:</p><pre>func (Book) TableName() string { <br>  return &quot;book&quot;<br>} </pre><pre>func (Shelf) TableName() string { <br>  return &quot;shelf&quot;<br>}</pre><p>This lib has a lot of <a href="https://gorm.io/docs/gorm_config.html">configurations</a> that you can change to be the default of your application and not be needed to always customize something.</p><p>Well, since I already mapped the entities than can implement the functions needed to create the book and allow the API to insert new books.</p><p>To create a new book will be needed two functions, one to find the shelf that the book will belong and validate if the capacity supports and the function that will insert the new book on the database and increments the amount of the shelf, as you can see:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/70137a0cac1e74d01e74bf07d877c286/href">https://medium.com/media/70137a0cac1e74d01e74bf07d877c286/href</a></iframe><p>To fetch the shelf with your books I had to use the preload of the associations, and to do that I’m using the Preload function of the GORM repository and next using the First function to fetch the first registry that has the ID equals to the variable value shelfID:</p><pre>err = r.db.Preload(clause.Associations).First(&amp;shelf, shelfID).Error</pre><p>All functions of GORM returns the struct of DB with the filled error when some wrong occurs and the count of rows affected, since I’m not worried about the rows affected, I’m only catching the value of Error to verify if all occurred as expected.</p><p>On the console it’s possible to see the generated SQL by GORM:</p><pre>[0.091ms] [rows:1] SELECT * FROM `book` WHERE `book`.`shelf_id` = 1 AND `book`.`deleted_at` IS NULL</pre><pre>[0.281ms] [rows:1] SELECT * FROM `shelf` WHERE `shelf`.`id` = 1 AND `shelf`.`deleted_at` IS NULL ORDER BY `shelf`.`id` LIMIT 1</pre><p>Now to create a book, the implementation of the InserBook function had to have an implementation to insert the book and update the shelf amount on the same transaction:</p><pre>return r.db.WithContext(ctx).Transaction(func(tx *gorm.DB) error {  <br>  book.ShelfID = book.BookShelf.ID  <br>  if err := tx.WithContext(ctx).Create(&amp;book).Error; err != nil {   <br>    return err  <br>  }   <br>  <br>  if err := tx.WithContext(ctx).Model(&amp;book.BookShelf).UpdateColumn(&quot;amount&quot;, len(book.BookShelf.Books)+1).Error; err != nil {   <br>    return err  <br>  }   <br>  <br>  return nil <br>})</pre><p>Using the function Transaction of db that expects a callback function that will be executed inside all on a single transaction, guarantees a rollback if something wrong occurs. So, I’m using this to insert the book and update the shelf safely.</p><p>But the GORM provides some interesting functionality, the <a href="https://gorm.io/docs/hooks.html">hooks</a>, that you can implements what will occur after the creation of the entity, and here I decided to change the insert of book removing the update of shelf and inserting this new function on the book entity:</p><pre>func (book *Book) AfterCreate(tx *gorm.DB) error { <br>  if book.BookShelf.ID == 0 {<br>    return nil<br>  }  <br>  <br>  if err := tx.Model(&amp;book.BookShelf).UpdateColumn(&quot;amount&quot;, len(book.BookShelf.Books)+1).Error; err != nil {<br>    return err<br>  }<br>  <br>  return nil<br>}</pre><p>And the InsertBook function becomes more cleaner:</p><pre>func (r BooksRepository) InsertBook(ctx context.Context, book books.Book) error {<br>  return r.db.WithContext(ctx).Transaction(func(tx *gorm.DB) error {<br>    book.ShelfID = book.BookShelf.ID<br>    if err :=   tx.WithContext(ctx).Create(&amp;book).Error; err != nil {<br>     return err  <br>    }<br>   <br>    return nil <br>  })<br>}</pre><p>Looking the console you can see the generated SQL:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/44f445f1f860b79a4fe31b77cde1a23d/href">https://medium.com/media/44f445f1f860b79a4fe31b77cde1a23d/href</a></iframe><p>Now I have the needed functions to insert the book following the business rules, let me talk about the tests with GORM.</p><p>As GORM has a feature to auto migrate by the mapped entities I decided to use the <a href="https://www.sqlite.org/index.html">SQLITE database</a> doing the auto migration to test all implementation of the database layer:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/50f1cfe42aa50688036adbd4ed19df33/href">https://medium.com/media/50f1cfe42aa50688036adbd4ed19df33/href</a></iframe><p>With this function it’s possible create the database of tests to each test of the repository as you can see on tests implemented to validate the search of the shelf and the creation of the book:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0081702475fa7ae8765b845de8e28f03/href">https://medium.com/media/0081702475fa7ae8765b845de8e28f03/href</a></iframe><p>With all implemented to insert a new book, it’s time to show you how implements the function to fetch the book by ID and the test to validate the implementation:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/7279a84c525490af0ec6e6a144b1bdab/href">https://medium.com/media/7279a84c525490af0ec6e6a144b1bdab/href</a></iframe><p>To fetch the book by ID with GORM is too simple, just need to use the Preload to fetch the shelf of the book and use the First function passing the variable of the book to store the value and the ID:</p><pre>err = r.db.WithContext(ctx).Preload(&quot;BookShelf&quot;).First(&amp;book, bookID).Error</pre><p>Following the CRUD operations, now you can see how implements the update of the book using GORM on your database layer with the test to validate if is what expects:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a1e99bc39dad45d1b58757ca5d47dafe/href">https://medium.com/media/a1e99bc39dad45d1b58757ca5d47dafe/href</a></iframe><p>Here to allow update only a few fields of the book, I’m using the Updates function passing a map with the fields that I want to update with the new values next to the function Model that says to GORM what entity that will be updated.</p><p>Completing the CRUD operations, the function to delete a book was implemented in a simple way only using the function Delete that will do a soft delete filling the DeletedAt field that was mapped using the typegorm.DeletedAt:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/482088e90862c058d9e6dfa0ce2ed415/href">https://medium.com/media/482088e90862c058d9e6dfa0ce2ed415/href</a></iframe><p>To finish the expected database layer, a function to find all books was implemented and next to a test validating the query:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bf0e722aff5e4b592ab0763de2dc70ec/href">https://medium.com/media/bf0e722aff5e4b592ab0763de2dc70ec/href</a></iframe><p>With the GORM it’s just necessary use the Preload function to fetch all the associations and use the Find function passing the slice of the books to find all books.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/0*Fzl9_HWMKQRmrFgq.gif" /></figure><p>Now the database layer was built one more time with no SQL code complexity, but the GORM does a lot of things in a magic way, for example, the hooks, looking on the database layer you haven’t to know that after the books are created the shelf will be updated.</p><p>All that was implemented you can see on my Github:</p><p><a href="https://github.com/rafaelhl/library-gorm-lib">rafaelhl/library-gorm-lib</a></p><p>Please leave a comment or suggestion and let me know what you think about GORM. If you are familiar with another library, also leave a comment so we can compare them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*_z1bZzrdz7glg8Td" /></figure><p>Until here two libs were explored, <a href="https://fs02.github.io/rel/#/">REL</a> and GORM, but has one more lib yet to be explored, however on the first article I said I would explore the <a href="http://jmoiron.github.io/sqlx/">SQLX</a> lib, and instead this, a new lib was suggested, the <a href="https://entgo.io/">ent.</a> lib a lib created by Facebook, so I decided to explore it since has a different approach and the SQLX still has a lot of SQL, which goes away the idea of this journey.</p><p>Thanks to <a href="https://medium.com/u/a72b03d3464f">Diego Henrique Oliveira</a> and <a href="https://medium.com/u/5d008b6fa606">Alana Domit Bittar</a> for the suggestions and the review.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7fee0316a989" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Looking for an ORM to database layer with Golang]]></title>
            <link>https://codeburst.io/looking-for-an-orm-to-database-layer-with-golang-92e360d3a920?source=rss-53581ac0d139------2</link>
            <guid isPermaLink="false">https://medium.com/p/92e360d3a920</guid>
            <category><![CDATA[chi]]></category>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[database-layer]]></category>
            <category><![CDATA[mysql]]></category>
            <category><![CDATA[orm]]></category>
            <dc:creator><![CDATA[Rafael Holanda]]></dc:creator>
            <pubDate>Sat, 15 Aug 2020 22:14:27 GMT</pubDate>
            <atom:updated>2020-10-15T18:51:11.261Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fKD-pQEQmzIp29TM" /></figure><p>Anyone who’s starting to work with Golang can note some lower productivity compared with another languages when building the layer of the database. This includes a lot of repeated SQL code that makes us waste time worrying about things that do not add value to what we want to deliver.</p><p>While looking for a library that can help us give productivity to the database layer, I looked into the REL library:</p><p><a href="https://fs02.github.io/rel/#/">Golang SQL Database Layer for Layered Architecture | REL</a></p><p>To see how this lib works on the field, I built a little example project of a book library that has CRUD operations. Here you will see how insert, update, delete, do queries, and how to handle transactions on the database in a simple way.</p><p>The book library API has five operations:</p><ul><li><em>POST /books</em> (Insert a new book on the library)</li><li><em>GET /books/{bookID}</em> (Get a book by your ID on the library)</li><li><em>PUT /books/{bookID}</em> (Update a book on the library)</li><li>DELETE /books/{bookID} (Delete a book on the library)</li><li><em>GET /books</em> (Get all books on the library)</li></ul><p>To do the routing of the application I choose <a href="https://github.com/go-chi/chi">chi</a> and as you can see the main function became something like that:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5867de9b16ab609ca2f460041b2bf8cb/href">https://medium.com/media/5867de9b16ab609ca2f460041b2bf8cb/href</a></iframe><p>Here I map the routes with your handlers but I create the repo of REL libs too, as you can see at the part of code below:</p><pre>adapter, err := mysql.Open(dsn) <br>if err != nil {  <br>  panic(err) <br>} <br>defer adapter.Close()  </pre><pre>// initialize rel&#39;s <br>repo := rel.New(adapter)</pre><p>With this, I have an instance of REL repo with the connection to MySQL, and this repo provides all functions that I need to communicate with the database. So I reuse the REL repo in the Repository Layer, as you can see below:</p><pre>type BooksRepository struct { <br>  repo rel.Repository<br>} </pre><pre>func New(repo rel.Repository) BooksRepository { <br>  return BooksRepository{<br>    repo: repo, <br>  }<br>}</pre><p>To start using the repo functions I had to map the entities as below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/edfab340ea532c99200eb852ad14d29b/href">https://medium.com/media/edfab340ea532c99200eb852ad14d29b/href</a></iframe><p>By default, REL will use the name of each field of the struct as the name of the column, and the name of the struct as name of the table on plural.</p><p>To customize the column name I use the tag db:&quot;shelf_id&quot; saying to the REL what name of this column has to be. And to customize the table name, I implement the function Table() with the struct as the receiver that I want to specify the name of table returning the name what I want.</p><p>After this I implement the first operation of the repository to insert a new book and wheres shelf this book belongs, to do that I needed two functions: one to find the shelf where the book will belong to validate your capacity and another function to insert the book and increment the amount of the shelf:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6de3348822221f0c2e348b7411907eb8/href">https://medium.com/media/6de3348822221f0c2e348b7411907eb8/href</a></iframe><p>Looking at each part of this code:</p><pre>r.repo.Find(ctx, &amp;shelf, where.Eq(&quot;id&quot;, shelfID))</pre><p>Here I’m doing a select from table shelf and filtering by your ID. REL is capable of figuring out which tables to query only by using the struct passed in the second parameter, and allows the possibility to use some other parameters to do a filter and another SQL statements, here I’m using the where to fetch the only ID with the value on variable shelfID. You can see a lot of other options on the REL documentation.</p><pre>r.repo.Preload(ctx, &amp;shelf, &quot;books&quot;)</pre><p>Now to fetch all books on the shelf, I call the function Preload that will load all the books inside of shelf struct using the mapping that was done before.</p><p>The REL will execute the query and print the SQL generated:</p><pre>SELECT * FROM `book` WHERE (`id`=? AND `deleted_at` IS NULL) LIMIT 1;<br>SELECT * FROM `book` WHERE `shelf_id` IN (?);</pre><p>To insert a book I need a transaction to insert and update the shelf table:</p><pre>r.repo.Transaction(ctx, func(ctx context.Context) error {<br>   book.ShelfID = book.BookShelf.ID<br>   r.repo.MustInsert(ctx, &amp;book, rel.Cascade(false))<br>   return r.repo.Update(ctx, &amp;book.BookShelf, rel.Inc(&quot;amount&quot;), rel.Reload(false))<br>})</pre><p>And to do that I’m using the Transaction function that expects a callback function that will be executed inside the transaction, being responsible for handle the errors. To perform the rollback I use the MustInsert function, responsible for insert a book. Moreover using the Update function to update the shelf table only incrementing the amount field and saying to not reload the variable after the update. With this, the SQL executed will be:</p><pre>begin transaction<br>INSERT INTO `book` (`title`,`description`,`author`,`edition`,`shelf_id`,`created_at`,`updated_at`) VALUES (?,?,?,?,?,?,?);<br>UPDATE `shelf` SET `amount`=`amount`+? WHERE `id`=?;<br>commit transaction</pre><p>The REL lib provides a way to do tests by mocking the connection with the database and validating if the functions will work as expected, to test these functions was created the following tests:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ac2d71c165c1620fd9a2b1e0e9eddabf/href">https://medium.com/media/ac2d71c165c1620fd9a2b1e0e9eddabf/href</a></iframe><p>After inserting the books was built the operation to find a book by ID:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5832250f5cf2713b45b43122a6792105/href">https://medium.com/media/5832250f5cf2713b45b43122a6792105/href</a></iframe><p>To find a book by ID I did something like I already did when finding a shelf by ID using the Find and Preload functions. And also create a test to validate if all will be working as expected.</p><p>In order to update a book I had to implement the function UpdateBook on the repository and to do that I only had to use the Update function of REL repo, specifying each field needed to update and after create a test after to validate if all works as expected, as below:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2faaa88902ca9b1de990eed13af92f3d/href">https://medium.com/media/2faaa88902ca9b1de990eed13af92f3d/href</a></iframe><p>To complete the four operations of the CRUD, I implement the delete function and how the DeletedAt field was mapped, the REL lib will do a soft delete and the repository implementation is much simple:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/eafe4267a6b8f3f1cec653538a076d6f/href">https://medium.com/media/eafe4267a6b8f3f1cec653538a076d6f/href</a></iframe><p>To finish the CRUD of books on a library, I added a function to find all existent books on the library implementing the function FindAllBooks that use two functions of REL repo, the FindAll function to fetch all books and the Preload function to fetch the shelf of each returned book, and of course, was built a test to validate:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/85e67994a72e01dab3b5f9df39b8c447/href">https://medium.com/media/85e67994a72e01dab3b5f9df39b8c447/href</a></iframe><p>With this, the database layer was built using the REL lib without any SQL complexity and you can find this project on my Github:</p><p><a href="https://github.com/rafaelhl/library-rel-lib">rafaelhl/library-rel-lib</a></p><p>Please leave a comment or suggestion and let me know what you think about REL. If you are familiar with another library, also leave a comment so we can compare them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*uS9EDe5V85jLWFel" /></figure><p>To continue looking for a good ORM it’s good to explore at least three options, so I opt beyond REL the libraries <a href="http://jmoiron.github.io/sqlx/">SQLX</a> and <a href="http://gorm.io/index.html">GORM</a>. So the next library that I will explore it’s the most popular <a href="http://gorm.io/index.html">GORM</a>:</p><p><a href="https://medium.com/@rafaelholanda90/continuing-looking-for-an-orm-to-database-layer-with-golang-7fee0316a989">Continuing looking for an ORM to database layer with Golang</a></p><p>Thanks for reviewers:</p><ul><li><a href="https://medium.com/u/a72b03d3464f">Diego Henrique Oliveira</a></li><li><a href="https://medium.com/u/a1b41529fc03">Felipe Santiago</a></li><li><a href="https://medium.com/u/72e8d8b83b91">Joao Fiumari</a></li><li><a href="https://medium.com/u/3ef378412346">João Victor</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92e360d3a920" width="1" height="1" alt=""><hr><p><a href="https://codeburst.io/looking-for-an-orm-to-database-layer-with-golang-92e360d3a920">Looking for an ORM to database layer with Golang</a> was originally published in <a href="https://codeburst.io/">codeburst</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>