Information system architecture
Solved
albert
-
mike -
mike -
Hello everyone,
I would like to know the implementation architectures of information systems (business, establishment...) or a site where I can find them. If someone can help me, I would be grateful. Thank you.
I would like to know the implementation architectures of information systems (business, establishment...) or a site where I can find them. If someone can help me, I would be grateful. Thank you.
8 answers
I understand,
thank you for your responses which have been a great help to me and I am truly grateful. Take care and have a good evening. Thanks again and see you later!
thank you for your responses which have been a great help to me and I am truly grateful. Take care and have a good evening. Thanks again and see you later!
The question is too broad.
There are so many different cases that you could spend your life listing them...
You should clarify your question.
There are so many different cases that you could spend your life listing them...
You should clarify your question.
You are asking for help with a task in a small business involving scattered data across databases and office files. You need to gather this data into a central database and want to visualize various IT architecture options to understand the possible architectures that will allow you to create this central database. Thank you.
ok... in that case, we need to plan a robust database server to handle the load.
We should try to assess the number of simultaneous SQL connections, the amount of data received/sent by different applications, evaluate the data volumes,
to determine what type of server to buy (CPU power? RAM? hard drive capacity?)
Also plan for backups
(on what medium, how often?)
Prepare the network infrastructure to support all this traffic (where are the applications accessing the database located (same site or not?) etc.
Choose a database server capable of handling a good load (LIKE MySQL, NOT Access, but rather Oracle or PostgreSQL, or even MS SQL Server...)
Also contact the development managers of each application, and see if it's possible to change their current database to the one you choose (and IF it's possible!).
And I'm forgetting things...
In short... you see, there isn't a miracle and absolute recipe for this kind of thing.
We need to assess the needs, the constraints, and find the best solution.
We should try to assess the number of simultaneous SQL connections, the amount of data received/sent by different applications, evaluate the data volumes,
to determine what type of server to buy (CPU power? RAM? hard drive capacity?)
Also plan for backups
(on what medium, how often?)
Prepare the network infrastructure to support all this traffic (where are the applications accessing the database located (same site or not?) etc.
Choose a database server capable of handling a good load (LIKE MySQL, NOT Access, but rather Oracle or PostgreSQL, or even MS SQL Server...)
Also contact the development managers of each application, and see if it's possible to change their current database to the one you choose (and IF it's possible!).
And I'm forgetting things...
In short... you see, there isn't a miracle and absolute recipe for this kind of thing.
We need to assess the needs, the constraints, and find the best solution.
The problem is that applications must always continue to function. And users should not notice the change. In fact, this centralized database is created by the company as part of a CRM project that it anticipates by implementing a customer information system. So we need to take into account the needs of each user and ensure that the necessary information for each application is included in the repository. If data appears in multiple sources, it must be represented uniquely in the centralized database. Do you think that the data warehouse will be the best solution for this? Thank you.
Absolutely, the data warehouse would be well suited.
But it remains completely separate from the normal operation of the applications.
It consists of importing copies of data from the different application databases.
This does not affect the existing applications at all, and these applications will continue to work with their respective databases.
But it remains completely separate from the normal operation of the applications.
It consists of importing copies of data from the different application databases.
This does not affect the existing applications at all, and these applications will continue to work with their respective databases.
That's exactly what I think. But I have a little problem; if the company emphasizes such a need that the foundations will have to be forgotten after loading the data and after verifying the quality of the data in a unique customer database, do you think in this case that the data warehouse could do the job?
No, what I mean is that the company may wish for the centralized database to serve as the support for all applications, as soon as it is functional.
In this case, it doesn't align at all with the data warehouse.
In this case, it doesn't align at all with the data warehouse.