I want to build a simple ERP app for my company,i came from PHP MYSQL background, i left PHP and now moving to NODE.JS because it overmatches PHP in many ways, i thought i have to learn NODE.JS,
我想为我的公司构建一个简单的ERP应用程序,我来自PHP MYSQL背景,我离开了PHP,现在转向NODE.JS因为它在很多方面超过了PHP,我想我必须学习NODE.JS,
my company is a meat and poultry importer and has hundreds of product and since it is CATCH WEIGHT INVENTORY SYSTEM, each carton has to be recorded as an individual data, they can be millions of cartons, besides INVENTORY, my app must also has other ERP functionalities such as SALES,PURCHASING,HRD,LOGISTIC and many others.
我的公司是肉类和家禽进口商,有数百种产品,因为它是CATCH WEIGHT INVENTORY SYSTEM,每个纸箱都必须记录为个人数据,它们可以是数百万个纸箱,除了INVENTORY之外,我的应用还必须有其他ERP SALES,PURCHASING,HRD,LOGISTIC等功能。
what i already have in mind, i would use :
我已经想到的,我会用:
- -Node.js then
- -Express / Meteor as backend
- -Angular/React as template engine + D3js (i'm not sure) to visualize various reports
- -various DBMS (i think i cannot rely onto just one DBMS, i have to harness the power both of RDBMS and NoSQL DBMS)
- MySQL for storing user data
- Key/Value pair DBMS (ElasticSearch / Redis) for storing hardly ever change data but used often and needs fast access such as data product
- Graph DBMS (Neo4j) for storing user relation, warehouse structure and product movement
- Document DBMS (MongoDB) for storing tally weight,product detail and many other document based data.
用于存储用户数据的MySQL
用于存储的键/值对DBMS(ElasticSearch / Redis)几乎不会更改数据但经常使用并且需要快速访问,例如数据产品
图DBMS(Neo4j)用于存储用户关系,仓库结构和产品移动
文档DBMS(MongoDB)用于存储计重,产品详细信息和许多其他基于文档的数据。
-Express / Meteor作为后端
-Angular / React作为模板引擎+ D3js(我不确定)可视化各种报告
- 各种DBMS(我认为我不能只依赖于一个DBMS,我必须利用RDBMS和NoSQL DBMS的强大功能)MySQL用于存储用户数据密钥/值对DBMS(ElasticSearch / Redis)用于存储几乎不会更改数据但使用经常需要快速访问,如数据产品Graph DBMS(Neo4j),用于存储用户关系,仓库结构和产品移动Document DBMS(MongoDB),用于存储计重,产品细节和许多其他基于文档的数据。
well chose the right tools and make a good plan is halfway to achieve goal, so i need enlightment from all of you Sir and Mam, give me suggestion what should/shouldn't i choose.
选择合适的工具并制定一个好的计划是实现目标的一半,所以我需要来自你们所有人的启发Sir和Mam,给我一些建议我应该/不应该选择什么。
1 个解决方案
#1
0
Your stack is okay but you need to re-consider the amount of database in use, you don't need the graph database Mysql can handle that for you and as for your key/value pair DBMS go with MongoDb it is a good key/value pair and document store.No need for the extra database.
你的堆栈还可以,但你需要重新考虑使用中的数据库量,你不需要图形数据库,Mysql可以为你处理,对于你的键/值对DBMS与MongoDb一起使用它是一个很好的密钥/值对和文档存储。不需要额外的数据库。
#1
0
Your stack is okay but you need to re-consider the amount of database in use, you don't need the graph database Mysql can handle that for you and as for your key/value pair DBMS go with MongoDb it is a good key/value pair and document store.No need for the extra database.
你的堆栈还可以,但你需要重新考虑使用中的数据库量,你不需要图形数据库,Mysql可以为你处理,对于你的键/值对DBMS与MongoDb一起使用它是一个很好的密钥/值对和文档存储。不需要额外的数据库。