本文介绍了前端,后端和中间件的Web开发的区别的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我想知道如果任何人都可以比较/对比度前端,后端和中间件之间的差异(中端?)简洁。

I was wondering if anyone can compare/contrast the differences between frontend, backend, and middleware ("middle-end"?) succinctly.

有没有在那里它们重叠的情况下?
在那里,他们必须重叠的情况下,和前/后端不能分开?
在瓶颈方面,一端与哪种类型的瓶颈相关的?

Are there cases where they overlap?Are there cases where they MUST overlap, and frontend/backend cannot be separated?In terms of bottlenecks, which end is associated with which type of bottlenecks?

推荐答案

这里有一个细目:

前端层 - >用户界面层通常由HTML,使用Javascript,CSS,Flash和各种服务器端code像ASP.Net,传统的ASP,PHP等想到这混合的为是最接近用户在code方面

Front-end tier -> User Interface layer usually consisting of a mix of HTML, Javascript, CSS, Flash, and various server-side code like ASP.Net, classic ASP, PHP, etc. Think of this as being closest to the user in terms of code.

中间件,中间层 - >一层背面,一般被称为系统的管道的一部分。 Java和C#是用于写这部分可能被视为UI和数据之间的胶,并且可以是web服务或WCF部件或其它SOA组件可能共同语言

Middleware, middle-tier -> One tier back, generally referred to as the "plumbing" part of a system. Java and C# are common languages for writing this part that could be viewed as the glue between the UI and the data and can be webservices or WCF components or other SOA components possibly.

后段层 - >数据库和其他数据存储一般都在这个水平。甲骨文,MS-SQL,MySQL和SAP,以及软件的各种现成的,货架件浮现在脑海中的这个软件是数据的最终处理。

Back-end tier -> Databases and other data stores are generally at this level. Oracle, MS-SQL, MySQL, SAP, and various off-the-shelf pieces of software come to mind for this piece of software that is the final processing of the data.

重叠可以任何这些之间存在如你可以有一切倾入一层象使用一个ASP.Net网站内置生成的Javascript而code后面可包含数据库命令使得$ AJAX功能C $ç背后同时包含中间和后端层。或者,可以使用VBScript作为使用ADO对象和合并所有三层为一体的所有图层。

Overlap can exist between any of these as you could have everything poured into one layer like an ASP.Net website that uses the built-in AJAX functionality that generates Javascript while the code behind may contain database commands making the code behind contain both middle and back-end tiers. Alternatively, one could use VBScript to act as all the layers using ADO objects and merging all three tiers into one.

类似地,服用中间件和前端或后端可以在某些情况下进行组合。

Similarly, taking middleware and either front or back-end can be combined in some cases.

瓶颈通常有几个不同的层次对他们说:

Bottlenecks generally have a few different levels to them:

1)数据库或后端处理 - >这可以从工资单或销售或其他任务,其中吞吐量数据库受困下来的东西有所不同。

1) Database or back-end processing -> This can vary from payroll or sales or other tasks where the throughput to the database is bogging things down.

2)中间件瓶颈 - >这将是在那里一些web服务可以被击中的容量,但在前后端部具有的带宽来处理更多的流量。可替代地,可能有某些服务器是一个系统,该系统是不太使用者介面部分或原始数据,可使用类似Biztalk的或MSMQ成为瓶颈的一部分。

2) Middleware bottlenecks -> This would be where some web service may be hitting capacity but the front and back ends have bandwidth to handle more traffic. Alternatively, there may be some server that is part of a system that isn't quite the UI part or the raw data that can be a bottleneck using something like Biztalk or MSMQ.

3)前端的瓶颈 - >这可能客户端或服务器端的问题。例如,如果你把一个低端PC,把它加载一个网页,包括大量的数据被下载,客户端可能是那里的瓶颈。同样,服务器可能被排队的请求,如果它是越来越像请求敲定什么Amazon.com或其他高流量的网站可能有时得到的。

3) Front-end bottlenecks -> This could client or server-side issues. For example, if you took a low-end PC and had it load a web page that consisted of a lot of data being downloaded, the client could be where the bottleneck is. Similarly, the server could be queuing up requests if it is getting hammered with requests like what Amazon.com or other high-traffic websites may get at times.

其中的一些是受跨pretation,所以它用任何手段因人而异。

Some of this is subject to interpretation, so it isn't perfect by any means and YMMV.

编辑:值得考虑的是,一些系统可以有多个前端或后端。例如,一个内容管理系统将可能对网站访问者的方式来查看这是一个前端,但怎么样怎么样的编辑内容可以更改网站上的数据内容?拉起此数据的能力可以被看作是前端,因为它是一个UI组件或因为它是用来通过内部用户,而不是一般公众查看的网站它可以被看作是一个后端。因此,存在对于这里上下文中所述的东西。

Something to consider is that some systems can have multiple front-ends or back-ends. For example, a content management system will likely have a way for site visitors to view the content that is a front-end but what about how content editors are able to change the data on the site? The ability to pull up this data could be seen as front-end since it is a UI component or it could be seen as a back-end since it is used by internal users rather than the general public viewing the site. Thus, there is something to be said for context here.

这篇关于前端,后端和中间件的Web开发的区别的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

08-23 04:51