Right approach to building SAAS in Laravel 4
Ok, so about a year ago I wrote a web app that helps organize appointments
for my dads company. He now "couldn't do business without it". I have
decided that I want to build a SAAS subscription model out of it and open
it up to the public.
It's currently built on codeigniter and php which I do not think is a good
fit for a SAAS version. I am planning on rebuiling it from scratch in
laravel 4 and using stripe as a payment gateway.
My concern is how best to handle the database / application structure for
more than one client. Currently, it just serves the one business and is
very un-abstract and is specific to my dads companies needs. I need it to
be able to handle different data depending on what the business who uses
it does.
I have looked into multi-tenancy but i'm not sure this is right for this.
I am thinking that a 'gmail' style approach would be better. One app /
domain that after login the user will see their customised dashboard and
only their data.
Before I get stuck in with the coding I need to work out how best to
handle multiple 'accounts' on the one database. I do not want to create a
table for each user, nor a database for each user.
I guess my question is can anybody point me in the right direction for how
best to handle a monthly payment subscription in Laravel? It's not so much
the code that I'm stuggling with, rather what exactly I would need to
build to handle charging the customer each month and denying them access
if billing failed etc.
Thanks
No comments:
Post a Comment