How to work with meteor and laravel in an appl? -

i tried build real-time web app.

the major app functionality based on meteor.js.(node.js mongodb)

but want let user management, billing system(stripe), static pages based on laravel(php + mysql).

they share same user system, authentication. part of whole app.

but have no idea how combine both, database schema.

there seem little written architectures this. both meteor , laravel still relatively new. i'm thinking of same combination following architecture. aware of fact i'm trying combine pizza steak (which might prove tasty).

what kind of app having architecture?

first strengths , weaknesses (real short). meteor fast , provides excellent communication layer between client , server. lacks matured data layer. nosql db's (like: mongo) lack example proper support migrations , not documented mysql. although think there might bright future nosql, it's not choice reliable applications 'yet'. though did see mysql layers meteor, not closely laravel mysql layers.

both applications have interface layer , both nicely documented. both run on unix systems , scale pretty in terms of code. both laravel , meteor event based.

with knowledge should clear apps chats, auctions , other live stuff should handled meteor. on other hand, structurizing complex / relational data should done laravel. if app small , has 1 goal. stick either laravel or meteor depending on demands , don't try combine them. if work on bigger project having static api mysql database chat functionality (for example facebook) go more distributed approach.

distributed cloud architecture here's reading material distributed architectures.

distributed clouds

in our use case meteor act (what call) secretary reading nosql storage , instructing other applications/workers it's efficient asynchronous way of working. laravel more in processing layer allowing consistent processing. laravel reads , mysql database , 'caches' api output nosql storage meteor uses. laravel app can accept queue messages , respond http calls send meteor application

soo: clients <-> meteor <-> mongodb <-> laravel <-> mysql

many projects start php laravel application, demand realtime functionality. example native ios/android app displays static content , should able have real time chat. that's architecture pretty nice. 2 applications different work closely using nosql storage or direct api calls.

although can both on same server recommend having cloud infrastructure 1 small meteor server, 1 laravel server. 1 mysql database server , 1 nosql server. each able scale independently depending on type of tasks. in case example during weekends meteor server can scaled down because there less clients connected while laravel server scales process intense stuff.

this setup pretty redundant. when complex laravel app fails, clients won't notice. on other hand when there high amount of clients, laravel continues tasks without disturbance