Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Special pages
Niidae Wiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Middleware (distributed applications)
(section)
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Use== Middleware services provide a more functional set of [[application programming interface]]s to allow an application to: *Locate transparently across the network, thus providing interaction with another service or application *Filter data to make them friendly usable or public via [[Anonymization#Anonymity on the Internet|anonymization process]] for privacy protection (for example) *Be independent from network services *Be reliable and always available *Add complementary attributes like [[semantics]] when compared to the operating system and network services. Middleware offers some unique technological advantages for business and industry. For example, traditional database systems are usually deployed in closed environments where users access the system only via a restricted network or [[intranet]] (e.g., an enterprise’s internal network). With the phenomenal growth of the [[World Wide Web]], users can access virtually any database for which they have proper access rights from anywhere in the world. Middleware addresses the problem of varying levels of [[interoperability]] among different database structures. Middleware facilitates transparent access to legacy [[database management system]]s (DBMSs) or applications via a [[web server]] without regard to database-specific characteristics.<ref>Peng, C, Chen, S, Chung, J, Roy-Chowdhury, A, and Srinivasan, V. (1998). Accessing existing business data from the World Wide Web. IBM Systems Journal, 37(1), 115-132. Retrieved March 7, 2009, from ABI/INFORM Global database. (Document ID: 26217517) </ref> Businesses frequently use middleware applications to link information from departmental databases, such as payroll, sales, and accounting, or databases housed in multiple geographic locations.<ref>Bougettaya, A, Malik, Z, Rezgui, A, and Korff, L. (2006). A Scalable Middleware for Web Databases. Journal of Database Management, 17(4), 20-39,41-46. Retrieved March 7, 2009, from ABI/INFORM Global database. (Document ID: 1155773301). </ref> In the highly competitive healthcare community, laboratories make extensive use of middleware applications for [[data mining]], [[laboratory information system]] (LIS) backup, and to combine systems during hospital mergers. Middleware helps bridge the gap between separate LISs in a newly formed healthcare network following a hospital buyout.<ref>Bagwell, H. (2008). [http://www.devicelink.com/ivdt/archive/08/07/007.html Middleware: providing value beyond autoverification] {{Webarchive|url=https://web.archive.org/web/20091012130823/http://www.devicelink.com/ivdt/archive/08/07/007.html |date=2009-10-12 }}. IVDT. Retrieved March 3, 2009. .</ref> Middleware can help software developers avoid having to write [[application programming interface]]s (API) for every control program, by serving as an independent programming interface for their applications. For [[Future Internet]] network operation through traffic monitoring in [[Network management|multi-domain scenarios]], using mediator tools (middleware) is a powerful help since they allow [[Telecommunications service provider|operators]], searchers and [[service providers]] to supervise [[Quality of service]] and analyse eventual failures in [[telecommunication service]]s.<ref>{{Cite web|author=Kai Oswald Seidler |url=http://www.fp7-moment.eu/ |title=MOMENT |publisher=Fp7-moment.eu |access-date=2010-08-19}}</ref> The Middleware stack is devised of several components (CSMS, TV Statistics & Client applications). It is known as the software brains of OTT platforms as it controls and interconnects all the components of the solution. The Content and Subscriber Management System (CSMS) is the central part of the solution commonly referred to as an administration portal. Apart from being the main interface for operator personnel to administer the TV service (Subscribers, Content, Packages, etc.) it also controls the majority of TV services and interacts with streaming & CDN and DRM serves to deliver Live, VOD and recorded content to the end users. It also integrates with external systems for billing, provisioning and with EPG and VOD content providers. Client applications authorize the CSMS and communicate with it, to provide required TV services to the end users on different devices. <ref>{{Cite web |last=Pirtovsek |first=Nino |date=September 16, 2021 |title=Guide to OTT Technology For Network Operators |url=https://www.uniqcast.com/blog/ott-technology-guide-network-operators |url-status=live |archive-url=https://web.archive.org/web/20221208133529/https://www.uniqcast.com/blog/ott-technology-guide-network-operators |archive-date=December 8, 2022 |access-date=May 10, 2023 |website=Uniqcast}}</ref> Finally, e-commerce uses middleware to assist in handling rapid and secure transactions over many different types of computer environments.<ref>Charles, J. (1999). [https://ieeexplore.ieee.org/Xplore/login.jsp?url=%2Fielx5%2F2%2F16523%2F00762786.pdf&authDecision=-203 Middleware moves to the forefront] {{subscription required}}. Technology News. Retrieved March 2, 2009.</ref> In short, middleware has become a critical element across a broad range of industries, thanks to its ability to bring together resources across dissimilar networks or computing platforms. In 2004 members of the [[European Broadcasting Union]] (EBU) carried out a study of Middleware with respect to system integration in broadcast environments. This involved system design engineering experts from 10 major European broadcasters working over a 12-month period to understand the effect of predominantly software-based products to media production and broadcasting system design techniques. The resulting reports Tech 3300 and Tech 3300s were published and are freely available from the EBU web site.<ref>{{Cite web|url=http://tech.ebu.ch/docs/tech/tech3300.pdf |title=EBU middleware report Tech 3300 |access-date=2010-08-19}}</ref><ref>{{Cite web|url=http://tech.ebu.ch/docs/tech/tech3300s.pdf |title=EBU middleware reports Tech 3300s |access-date=2010-08-19}}</ref>
Summary:
Please note that all contributions to Niidae Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Encyclopedia:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Search
Search
Editing
Middleware (distributed applications)
(section)
Add topic