I have an application that is divided into two main parts:
- A web crawler written in Python
- A REST API written in Golang
They share a MySQL database, which is mainly populated/updated by the web crawler, and then read from by the REST API.
I wanted to use an ORM on each side to make interacting with the database easier, but now I am not sure if this is a good approach.
It doesn't seem like a good idea to maintain two sets of ORM model files, where I would have to change each set whenever I want to change some attributes of the database. Additionally, I am worried that with two ORMs battling for structure of the database, that conflicts might arise, or the models might become out of sync with what the actual db structure is.
Is this a scenario where using an ORM will cause more trouble than its worth? Or maybe I should use a single ORM (for either Python or Golang) and write raw queries for the other side.