[PonyORM-list] PonyORM and a micro-service architecture

Alexey Malashkevich alexeymalashkevich at gmail.com
Mon Jun 5 12:17:18 UTC 2017

Hi Andrew,

Please see the answer at


On Wed, May 31, 2017 at 1:45 PM, Andrew Graham-Yooll <
andrew at solarisoffgrid.com> wrote:

> Hello all,
> We have a monolithic application built with a Flask/Pony framework. It
> works great right now.
> However, in the near future we are going to start shifting to a
> micro-service architecture. In this process, we are going to most likely
> have a separate Db for each service. For a number of reasons that I wont go
> into, this is beneficial. But i get hung up, and I know many others do too,
> when thinking about the foreign key relationships developed between tables
> at the moment.
> People have solved this by denormalizing their db's ending up with
> duplicated tables in another service's DB.
> Im curious what the users of pony think of this solution and if its
> feasible.
> And what have others using PonyORM, or any other ORM for that matter, come
> up with when using a micro service architecture?
> Thanks
> Andrew
> <http://www.solarisoffgrid.com/#what-we-do>
> <http://www.solarisoffgrid.com/#what-we-do>
> _______________________________________________
> ponyorm-list mailing list
> ponyorm-list at ponyorm.com
> /ponyorm-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ponyorm-list/attachments/20170605/19d07e16/attachment.html>

More information about the ponyorm-list mailing list