D
D
Dmitry2017-05-06 23:55:48
JavaScript
Dmitry, 2017-05-06 23:55:48

Choice of technologies for a client-server application?

Good evening, I need help choosing a stack of technologies. You need to write a simple application (front + back with the server).
The problem is that I have absolutely no experience in web development, but I have to do this (before that I had only C # experience).
For today the decision to use JS is accepted. After a week of studying information, a clear understanding of how it should work did not work out. The zoo of frameworks has formed a big mess in my head.
Now I'm learning JS and understanding how such a bundle works: Node.js + Express + Typescrip + trifle
I don’t understand if I need to connect something else, such as angular or react, in order to implement, as it seems to me, not the most complicated application, or is it better to try to write everything in native JS (read TS), with local use of small libraries for display tables or something else?
The application itself is for the internal use of a small company, it consists in viewing and unloading tabular data on the client side.
It should consist of:
1. Authorization (internal for the company, no google-accounts and other goodies are needed)
2. A page with a list of the names of the "tables" that we will access. There are many of them - should be grouped under spoilers.
3. Page with the table itself and filters for it. (for filters, an instant response is not needed: ... set up 5-10 filters, clicked the apply button, the data was updated)
3.1 Tables can be of any size, both rows and columns, and with any data types. > a million lines "before filters". Naturally, when working, the data should not be cached on the client.
3.2 Filters must be added dynamically by the client, depending on the available columns. Columns can be disabled. 4. Uploading
data to csv, excel..
4.1 Uploading: a) total b) filtered c) marked Thank you.

Answer the question

In order to leave comments, you need to log in

1 answer(s)
S
Stanislav Romanov, 2017-05-07
@Kaer_Morchen

If realtime is not needed, take the usual PHP + framework for it (for example, laravel or Lumen is simpler).
For the front, I still recommend taking some small and simple framework, figure it out and make a structured, albeit maybe crap, but code. It can be backbone, vue.
Such a stack will give a maximum of ready-made solutions with minimal man-hours to figure it out.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question