1

Hi need an advice on which technologies adopt for a project with the follow requirements:

B2B multi-user browser app. Talking about a multi-functional app: we need it for internal corporate use (a complicated admin panel) and for B2B customer that wants a view on analytics data (graphs, pies, search, trends, etc.)

We are 3 developers, so far we used some OO PHP with jQuery for AJAX and HTML5/CSS for rendering. No framework adopted, but we’re evaluating some.

Should we completely separate backend logic from front-end? I mean RESTful API and let’s say a JS framework for the front-end, or it would be quite hard?

We’re open to “new” technologies, could you please provide come cutting edge approach in 2016? Our time-window is more or less 6-9 months.

Jumpa
  • 4,319
  • 11
  • 52
  • 100

2 Answers2

1

Since it's a multi-funcional app with integration of dashboards and multiple panels, I would 100% suggest usage of a framework and the separation between backend and frontend. This way your architecture will be more powerful and reliable, as well as easy to maintain in the future (since it's a large app, bad architecture can cost you a lot of time and money in the future). Separating this into 2 major components can help you guys split work. One major backend, one major frontend and one guy more focused on the communication (API, requests...) can be one solution.

For the backend, since you're used to work with PHP and you need something to control all that complex data you're going to work with, I would suggest Laravel (growing in 2016!). It's great to build API's and make a very good connect from Model to request since you have service layers. For the frontend, just keep it simple with well separated views, CSS by components and well defined HTML. Be sure you use SASS for example, since you're building graphs and other elements that needs a well structured data. Bootstrap can help you guys out dealing with the basic layout.

Bootstrap - http://getbootstrap.com/

Laravel Basics - https://laravel.com/docs/5.2/quickstart

Laravel Service Provider - https://laravel.com/docs/5.3/providers

bmfteixeira
  • 124
  • 1
  • 12
1

It's very good idea to split front end from back end by api available throw HTTP. It's will allow connect to you server any type of a client. May be in future you wold like to connect mobile app to you server. Also you can think about micro-service architecture. It's cutting edge approach now. p.s.Of couse it's flame topic, but after some research i decide to use Symfony on back end.

Artemy Prototyping
  • 170
  • 1
  • 9