Today's distributed systems are based on internet and HTTP connection. Which means the private protocols other than TCP/IP connection are less supported and non-open standard. And beyond the Level 4 Network concept framework, HTTP and SOAP definitely dominate the way in transmission among those distributed systems. Here I wanna discuss several aspects of the technology design strategy existed in those distributed system. Before we expand the discussion, here are some terminology that lay out the system development.
Three-Tier System Architecture: In traditional distributed system, three-tier system has UI Layer, AP Layer and Data Layer. In Web-like distributed system, the UI Layer involve the browser and web page container. The AP Layer might involve a lot of SOAP-like service. If it's necessary, we sometimes have to dig into TCP/IP connection for communicating with legacy system which has no HTTP protocol OS support. The Data Layer is Database or File System on legacy system.
Development Stack: The technology we use to develop the distributed system. Corresponding to the Three-Tier system, the web page container and SOAP-like service management would rely on server we choose such as IIS, Tomcat, Jetty etc. You can see the application server could determine the development framework and languages - .Net and Java. There are some other popular application frameworks like Rail, PHP, Djongo would be based on Apache server. Those application frameworks have different Web UI rendering strategy, SOAP or RESTful management model and Data Persistent Framework for adoption in your project.
No comments:
Post a Comment