ruby on rails - Separating out user management and Stripe payments into a second app and linking via API. My Neo4j knowledgebase -

i've built database in neo4j , use rails neo4jrb easy way manipulate database. reasons explain below, below call knowledgebase (kb) instead of database.

i starting working friend wants provide access kb users of app. built api in rails can access it.

now friend , talking building membership site subscription payments. figured needed figure out how build stripe subscription payments app. found great tutorial railsapps in terms of functionality need, relies on gem called payola makes stripe integration easy. payola great works activerecord, not neo4j. thinking i'd have figure out how payola neo4j.

but have idea of building separate app using railsapp+payola approach, , hooking app kb's api.

the reason knowledgebase because purpose structure knowledge within particular domain. use graph database neo4j because graph-based data model suits goal, example (object of type a) -[has influence on]-> (object of type b).

so idea of using separate app managing users , subscriptions because avoid mixing app specific data domain knowledge in database.

so guess concern is, might missing? speed concern if membership site has access api every time page loads? there unusual security concerns?

it's fine use database next neo4j. should use database fits needs think :)