Centralizing information

Asked

Viewed 27 times

0

Good morning. We are starting to develop several small solutions for web (We Use Laravel) to meet the needs of our customers, based on this I came up with a great question. I would like to centralize all the information that will be used throughout the projects to stay in one place and each application with its peculiarity in another, example: I have a tax document module and another request, I would like to centralize customer information in one place so that both the order module and the tax documents module access the same information. Any suggestions on how I can do this ?

  • Table relationship, the customer table with the customer data, and for example the table of tax documents, with a customer id field for table relationship, so you identify which tax document is which customer. One of the solutions is this, it has other means, depending on which database you make use of.

  • You say, use the same database for all applications ?

  • Yes, but creating relationship between the tables, through a field that identifies the customer, or a table the part that relates the tables, for example, in the tax document a field that stores the customer’s ID, or a cliente_documents table where you have a document ID field and another client ID field.

  • Yes, this way I already work. The problem is that I think the database is getting too big, I wondered if there was another way to do this so that my comic book is more organized. Imagine what a database would look like for 10 different applications ? srsrs

  • and what is the difficulty in working with database with large volume of information?

  • I say by the fact of organization, has worked like this kind of situation ? If yes you see no problem ?

  • No problem, work with data volume where one . Exported SQL reaches 200mb, other smaller ones, other bigger ones, it is only a matter of a good structuring of your DB and the relationship of tables. Even for maintenance is easier.

  • cool, @Eliseub. Thanks a lot for the tip.

  • Work with procedures, which also helps a lot in the performance process and maintenance of your DB, and even taking into account that you gain time. Hug.

  • You could create an API that centralized the information of your applications. The idea would work more or less like a shared bank. And your application would consume the services of the API (Responsible for cross-checking the data of your modules etc).

Show 5 more comments
No answers

Browser other questions tagged

You are not signed in. Login or sign up in order to post.