![]() But the size was an issue, servers really contain a lot of services, task managers, data handlers, connection managers, authentication managers and so on and so forth. In such cases, it was a good approach to have the server installed with the application. If we skip out all of the problems of network based data instances, such as, security vulnerabilities etc, even then we are left out with other issues such as, what application will do when the network is down? Or what happens to all customers, if server goes down, or server is upgrading and many other similar issues. The problem with older database systems was that they were installed at a location and a network connection was required to retrieve or store the data. Software developers wanted to develop application software, that would run on the machines themselves and store the data locally instead of having to build a large server processing and storing the data. However, you can always use tokens, or account systems to allow them to perform some administrative tasks.īut as the world progressed, there were changes to the way applications were developed. Other machines were agnostic as per this information. Only one machine, or program needed to know the authentication, or the mechanisms to retrieve the data and how to store the data.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |