V
V
Vadim2015-11-22 13:54:45
Database
Vadim, 2015-11-22 13:54:45

How to start developing a database application?

Good day!
Undertook the development of the first more or less serious application. It will be connected mainly with adding \ changing \ displaying data from the database. The database itself is in MySQL.
Can you tell me how to start designing an application? What models exist and where can I read about it in an understandable language?
I already heard something about Hibernate in Java, as well as a variant for C # - NHibernate. But they also write that ORM-systems are "bad and overloaded" ... But I don't want to mix SQL and PL together.
Due to lack of experience, I can not soberly judge what is good and what is bad. Help me to understand!

Answer the question

In order to leave comments, you need to log in

4 answer(s)
M
MonkAlex, 2015-11-22
@MonkAlex

But they also write that ORM systems are "bad and overloaded" ..
X * d is written on the fence. Any ORM is better than a situation where an sql query is written for each sneeze.
And you need to start with the architecture, if you have experience, or at least with the data model.

T
TyzhSysAdmin, 2015-11-22
@POS_troi

An application that uses a database begins with the design of the database structure - as for me, this is the most difficult part, here you need to think a lot and take into account many subtleties.

O
OnYourLips, 2015-11-22
@OnYourLips

From the receipt of the technical task. If this task is for you, then with the definition of goals, terms, processes and writing this task.

M
Misha Petrov, 2015-11-22
@islk

Understand the entities of the subject area - what we are dealing with. What properties they, entities, have, which of them are important to us, and which are not. How these entities are related to each other. The conceptual model of the subject area, in a good way, is drawn up by a graphical diagram with explanations. Then, if possible, analyze all the use cases - who will use it, why, what information should be obtained and what changes in the data should occur. Use cases are called. Then, proceeding from this, everything else that is said here.
If you skip this stage, then the day before the delivery you can easily find that the existing database structure, in principle, does not allow you to solve the task that is most important for the customer, and that the data structure needs to be redone, and all the code written for it must be rewritten from scratch.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question