多用户数据应用程序架构

本文介绍了多用户数据应用程序架构的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述 29岁程序员，3月因学历无情被辞！ 我正在努力将我的应用程序从单个用户转换为 多用户。目前的架构是MSDE数据后端 （很快转换到SQLExpress，但尚未完成）。每个用户直接连接数据库 - 连接字符串加密存储在本地 文件中，所有设置等都存储在数据库中。问题是它似乎很快就会出现可扩展性和安全性问题。另一个问题是有一些文件，如图像文件， 存储在本地文件系统中，存储在数据库中的是文件的 路径。例如，如果UserA将图像添加到记录中，那么 UserB打开该记录，他们将无法看到图像，因为文件实际上是 在UserA的机器上。任何方向都可以通过这个方式获得赞赏。 解决方案 查看n层架构。特别是web服务和.NET 远程处理。 我会将图像和您拥有的任何其他二进制文件存储在数据库中 本身而不仅仅是指向其文件位置的指针。这很容易 足以将二进制文件直接写入图像字段类型并读取 它退出。 查看n层架构。特别是web serviecs和.NET 远程处理。 I''m working on converting my application from a single user, to amulti-user. The current architecture is with an MSDE data back end(switching to SQLExpress soon, but not quite yet). Each user connects tothe database directly - the connection string is stored encrypted in a localfile, and all settings etc. are stored in the database. The problem is itseems that this could rapidly run into problems with scalability andsecurity. The other issue is there are some files such as image files thatare stored in the local file system and what is stored in the database is apath to the file. For example, if UserA add an image to a record, thenUserB opens that record, they won''t be able to see the image as the file isactually on UserA''s machine. Any direction in where to go with this wouldbe appreciated. 解决方案Look into n-tier architecture. In particular web serviecs and .NETremoting.I''d store the images and any other binaries you have in the databaseitself rather than just a pointer to its file location. It''s easyenough to write the binary straight into an image field type and readit back out.Look into n-tier architecture. In particular web serviecs and .NETremoting. 这篇关于多用户数据应用程序架构的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！ 上岸，阿里云！