What architecture to choose?

C

Cyril2016-12-01 17:34:59

CRM

Cyril, 2016-12-01 17:34:59

The question arose of creating CRM as a SaaS web application, which includes workflow, a calendar, an email client, client management (client base) and everything else that usually happens in CRM. Plus - the organization of the workplace (personal account).
It is meant to be used internally only (and within the franchise buyer's company). The number of personnel (of one company) that will simultaneously use CRM is more than 200 people. In addition to the company's staff, customers, of which there are more than 1000 (or even more), will also contact some CRM modules.
In addition, there was a desire to connect such CRM with PBX so that you can keep an archive of telephone conversations with customers. And also integrate it with telecom operators Beeline, Megafon, MTS.
In the future, there is an intention to provide CRM on a franchise (SaaS) in the form of a sub-domain model ( company_name.mycrm.ru , where company_name is the company that bought the franchise).
Considering the above wishes, several questions arise:

What technologies to choose? (language, backend/frontend framework)
Should I immediately choose a corporate DBMS, such as SQL Server / Oracle?
If you have to choose PHP as the language, then how effective is it to write CRM in it? And what frameworks and related technologies to choose for it?

Thanks in advance.

Reply

Answer the question

In order to leave comments, you need to log in

3 answer(s)

X

xeops, 2016-12-08
@xeops

We are making one cloud-based CRM for travel agencies here...
The first version came out for about $60K, but they didn't want to buy it.
At that moment, when customers were ready to pay money for use, about $100K was invested in the system.
Now there are hundreds of customers, the system is several years old, and it is still being developed and developed. And there is no end to this, because strong competitors have appeared.

S

Stepan Yudin, 2016-12-01
@stepan_sib

Write from scratch - do not even think) A few years will go away, and it will most likely go down the drain.
I strongly advise you to take a closer look at OroCRM/OroPlatform
Based on the Symfony framework. Very good code, very well extensible.

S

sim3x, 2016-12-01
@sim3x

1. django + rest + angular2/react
ClojureScript + React
2. PostgreSQL. From oracle even Yandex dumps (dumped?)
3. Not at all. If you need a code that will not be completely thrown out after the arrival of a normal service station, then specialists in any PL will cost the same amount