kitman's avatar

Should I separate my system?

Hi everyone,

I trying the create 3 system/projects, which are the API posts system which handing all the posts(eg :video post, post ), API Landing page system which handles all the landing page stuff and an API auth system which connects all other two systems not sure is it a good idea? the reason behind this is because the company that I work for changes their website quite often, in the past they have changed from their own cms to using WordPress a year ago, however, they wanted to keep all the posts from the old CMS, and now wanted to do a new website again with Drupal, another problem is these posts are used by another system (products) as well and need to sync the post to the other systems, my point of view is separating the three system have the following benefits

  1. ppl can use our api if wanted, does not matter what CMS they use, they can just read the data.

  2. more than one application can access the data.

3.In some time there will be new ways of promoting the business(eg: VR ) so landing pages or posts will maybe not used. we just needed to disconnect from the auth system.

  1. does not matter how the front-end changes it will not effect backend programmers.

  2. For the speed I decide to put the 3 system at the same server, so don't think it will be a big issue, but not sure.

0 likes
2 replies
Web Confection's avatar

Not sure what "API Landing page system" is but separating the authentication solution and creating an API seems seems sensible. You will need token based authentication/authorisation using something like Laravel Passport.

biishmar's avatar

@kitman

Single advice is that, dont make too much of API call to different system, that would take hell of a time..

Please or to participate in this conversation.