DOCSLIB.ORG

An Overview on the Architecture of Whatsapp

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
An Overview on the Architecture of Whatsapp Umesh Gupta / International Journal of Computer Science & Engineering Technology (IJCSET) An Overview on the Architecture of WhatsApp Umesh Gupta, Asst Professor,Jagannath Management International School, Kalkajii, E Mail Id: [email protected] Abstract: WhatsApp Messenger Application is a messagingn application that uses the Internet to connect to the person whose number is registered with WhatsApp Account. Various Databases have been used in the distributed applications so far. In this Application of Mnesia Database ushers us into a new set of opportunities to be explored and XMPP server is used to maintain the messages queue. In this paper , a general overview on the architecture used by Whatsapp makinng it one of the most reliable and fast media transfer application has been explored. Keywords: WhatsApp, CountFly,XMPP,Mnesia Introduction: WhatsApp is the most sought after messaging application that has revolutionized the messaging app market and it is an alternative to any Smartphone’s built –in SMS application. It uses the Internet to connect the person to anyone whose phone number is registered in the installed phone’s address book. This platform can also be used for downloading any media. WhatsApp Messenger Application when installed in any Smartphone will scan the Smartphone for all of the phone numbers of the contacts and validates those numbers from the database. It also integrates the Smartphone’s gallery and camera, enabling the user to send the data immediately. One of the basic reason behind the Whatsapp application to be free is this is knowledge era resulting into the companies need to dig into the personal information of the users. XMPP server: WhatsApp makes use of XMPP server (XMPP-Extensible Messaging and Presence Protocol). Ejabberd is an open source Jabber server facility that can transfer messages between two or more users at any point of time provided the internet connection is feasible. ISSN : 2229-3345 Vol. 7 No. 07 Jul 2016 335 Umesh Gupta / International Journal of Computer Science & Engineering Technology (IJCSET) In the above described architecture, the Scheduler has double linked lists that stores the tickets in the FIFO order and checks the database for new requests, avoids duplication with creation of action tickets. Data Fetcher threads are responsible for establishing the XMPP server connection, gets the data from the node and in the end it sends the received values to be stored in the Mnesia DB. Action Threads consume the action tickets and with the information based on this tickets will verify if the rules are matching or not, thereby further processing the tickets for action. Database Handler is a thread that has specific functionality, connecting to database and handling query’s. The programming language used is ERLANG that helps to quickly adapt instant updates and hot fixes. It is also help in push notifications that can be used to reach to the user, in case the user is offline. WhatsApp has chosen Erlang a language built for writing scalable applications that are designed to withstand errors. Erlang uses an abstraction called the Actor model for it's concurrency Instead of the more traditional shared memory approach, actors communicate by sending each other messages. Actors unlike threads are designed to be lightweight. Actors could be on the same machine or on different machines and the message passing abstractions works for both. Implementation : A simple implementation of WhatsApp could be: Each user/device is represented as an actor. This actor is responsible for handling the inbox of the user, how it gets serialized to disk, the messages that the user sends and the messages that the user receives Whatsapp is an application that is able to handle approximately 50 billion message transfers a day. The main reason behind its popularity is the data processing of the message queue length which is associated with a node is being monitored. In case of multimedia messages, the contents are uploaded into a HTTP server and then the receiving node can accept or block it depending on its preferences. WhatsApp utilizes XMPP protocol where the queue is maintained and the messages will wait till the queue message is received by the receiver node. The Notifications is received by the sender when the message is received by the receiver. After the delivery of the messages , the messages are immediately removed from the server. Registration of WhatsApp account: The registration of the WhatsApp account is based on the mobile IMEI number where the user is permitted to select the username and the password. The new registration also considers a 5 digit PIN which acts as an unique key, that further intensifies the security and lowers the interdependence on the device. ISSN : 2229-3345 Vol. 7 No. 07 Jul 2016 336 Umesh Gupta / International Journal of Computer Science & Engineering Technology (IJCSET) The database that is used to handle the large amount of data by the WhatsApp is Mnesia DB. Mnesia DB is a multiuser distributed DBMS which is the default database of the ERLANG that is programming language of Whatsapp. This Database helps to achieve quicker request responses, thereby improving the efficiency and main reason for the popularity of the WhatsApp. Mnesia DB also helps to save in the user logins and also helps to maintain the user credentials from the personal data. WhatsApp is implemented on the operating system of FreeBSD that helps to optimize the working of the social media platform. Web Server YAWS is used by the application specifically to store the multimedia files and it helps in quicker transformation. Conclusion: In this paper, a simple overview of the WhatsApp has been made. In future , we would like to explore the problems faced in the security and database storage of Mnesia. References: [1] https://middlewaresensing.wordpress.com/tag/architecture-xmpp [2] https://en.wikipedia.org/wiki/Mnesia [3] Boulos, M.N.K., Wheeler, S., Tavares, C., Jones, R. How smartphones are changing the face of mobile and participatory healthcare: an overview, with example from eCAALYX. Biomed. Eng. Online.2011;10:24. [4] Hsieh, C.H., Jeng, S.F., Chen, C.Y., Yin, J.W., Yang, J.C., Tsai, H.H., Yeh, M.C. Teleconsultation with the mobile camera- phone in remote evaluation of replantation potential. J. Trauma. 2005;58:1208–1212. ISSN : 2229-3345 Vol. 7 No. 07 Jul 2016 337.
Load more

Recommended publications
  • Webrtc and XMPP
    webRTC and XMPP Philipp Hancke, XMPP Summit 2013 What is this webRTC thing … …and why should XMPP developers care? . I assume you know what XMPP is… . … you might have heard of Jingle . the XMPP framework for establishing P2P sessions . used for VoIP, filesharing, … . … you might have also heard about this webRTC thing . doing VoIP in the browser . without plugins . „no more flash“ . Do you want to know how it relates to XMPP ? Philipp Hancke © ESTOS GmbH 2013 2 What is webRTC? . P2P sessions between browsers . no servers involved in media transfer . using open standards . Javascript API in the browser . also an BSD-licensed C++ library from Google . Want to know more? . Listen to the evangelists! . Justin Uberti http://www.youtube.com/watch?v=E8C8ouiXHHk . Jose de Castro http://vimeo.com/52510068 . Cullen Jennings http://vimeo.com/cullenfluffyjennings/rtcwebexplained Philipp Hancke © ESTOS GmbH 2013 3 Initiating P2P sessions . initiate a P2P session between two browsers . negotiate media codecs, NAT traversal, etc . media is sent P2P . you need a session initiation protocol . SIP? . JSEP? . H.323? . Jingle! . webRTC does not mandate a signalling protocol . WG decision Philipp Hancke © ESTOS GmbH 2013 4 Call Flow - JSEP Philipp Hancke © ESTOS GmbH 2013 5 Jingle . You can use Jingle as signalling protocol . together with BOSH or XMPP over websockets in the browser . Demo later . But… . webRTC uses the Session Description Protocol as an API . Jingle does not use SDP . You need a mapping SDP -> Jingle -> SDP . Complicated, but doable . Topic for breakout Philipp Hancke © ESTOS GmbH 2013 6 Call Flow - Jingle Philipp Hancke © ESTOS GmbH 2013 7 webRTC-Jingle usecases .
    [Show full text]
  • Cheat Sheet – Common Ports (PDF)
    COMMON PORTS packetlife.net TCP/UDP Port Numbers 7 Echo 554 RTSP 2745 Bagle.H 6891-6901 Windows Live 19 Chargen 546-547 DHCPv6 2967 Symantec AV 6970 Quicktime 20-21 FTP 560 rmonitor 3050 Interbase DB 7212 GhostSurf 22 SSH/SCP 563 NNTP over SSL 3074 XBOX Live 7648-7649 CU-SeeMe 23 Telnet 587 SMTP 3124 HTTP Proxy 8000 Internet Radio 25 SMTP 591 FileMaker 3127 MyDoom 8080 HTTP Proxy 42 WINS Replication 593 Microsoft DCOM 3128 HTTP Proxy 8086-8087 Kaspersky AV 43 WHOIS 631 Internet Printing 3222 GLBP 8118 Privoxy 49 TACACS 636 LDAP over SSL 3260 iSCSI Target 8200 VMware Server 53 DNS 639 MSDP (PIM) 3306 MySQL 8500 Adobe ColdFusion 67-68 DHCP/BOOTP 646 LDP (MPLS) 3389 Terminal Server 8767 TeamSpeak 69 TFTP 691 MS Exchange 3689 iTunes 8866 Bagle.B 70 Gopher 860 iSCSI 3690 Subversion 9100 HP JetDirect 79 Finger 873 rsync 3724 World of Warcraft 9101-9103 Bacula 80 HTTP 902 VMware Server 3784-3785 Ventrilo 9119 MXit 88 Kerberos 989-990 FTP over SSL 4333 mSQL 9800 WebDAV 102 MS Exchange 993 IMAP4 over SSL 4444 Blaster 9898 Dabber 110 POP3 995 POP3 over SSL 4664 Google Desktop 9988 Rbot/Spybot 113 Ident 1025 Microsoft RPC 4672 eMule 9999 Urchin 119 NNTP (Usenet) 1026-1029 Windows Messenger 4899 Radmin 10000 Webmin 123 NTP 1080 SOCKS Proxy 5000 UPnP 10000 BackupExec 135 Microsoft RPC 1080 MyDoom 5001 Slingbox 10113-10116 NetIQ 137-139 NetBIOS 1194 OpenVPN 5001 iperf 11371 OpenPGP 143 IMAP4 1214 Kazaa 5004-5005 RTP 12035-12036 Second Life 161-162 SNMP 1241 Nessus 5050 Yahoo! Messenger 12345 NetBus 177 XDMCP 1311 Dell OpenManage 5060 SIP 13720-13721
    [Show full text]
  • Instant Messaging
    Instant Messaging Internet Technologies and Applications Contents • Instant Messaging and Presence • Comparing popular IM systems – Microsoft MSN – AOL Instant Messenger – Yahoo! Messenger • Jabber, XMPP and Google Talk ITS 413 - Instant Messaging 2 Internet Messaging •Email – Asynchronous communication: user does not have to be online for message to be delivered (not instant messaging) • Newsgroups • Instant Messaging and Presence – UNIX included finger and talk • Finger: determine the presence (or status) of other users • Talk: text based instant chatting application – Internet Relay Chat (IRC) • Introduced in 1988 as group based, instant chatting service • Users join a chat room • Networks consist of servers connected together, and clients connect via a single server – ICQ (“I Seek You”) • Introduced in 1996, allowing chatting between users without joining chat room • In 1998 America Online (AOL) acquired ICQ and became most popular instant messaging application/network – AIM, Microsoft MSN, Yahoo! Messenger, Jabber, … • Initially, Microsoft and Yahoo! Created clients to connect with AIM servers • But restricted by AOL, and most IM networks were limited to specific clients • Only recently (1-2 years) have some IM networks opened to different clients ITS 413 - Instant Messaging 3 Instant Messaging and Presence • Instant Messaging – Synchronous communications: message is only sent to destination if recipient is willing to receive it at time it is sent •Presence – Provides information about the current status/presence of a user to other
    [Show full text]
  • XEP-0156: Discovering Alternative XMPP Connection Methods
    XEP-0156: Discovering Alternative XMPP Connection Methods Joe Hildebrand Peter Saint-Andre Lance Stout mailto:jhildebr@cisco:com mailto:xsf@stpeter:im mailto:lance@andyet:com xmpp:hildjj@jabber:org xmpp:peter@jabber:org xmpp:lance@lance:im http://stpeter:im/ 2020-07-07 Version 1.3.1 Status Type Short Name Draft Standards Track alt-connections This document defines an XMPP Extension Protocol for discovering alternative methods of connecting to an XMPP server using two ways: (1) DNS TXT Resource Record format; and (2) Web Host Metadata Link format. Legal Copyright This XMPP Extension Protocol is copyright © 1999 – 2020 by the XMPP Standards Foundation (XSF). Permissions Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the ”Specification”), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specifi- cation, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or sub- stantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or pub- lisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation. Warranty ## NOTE WELL: This Specification is provided on an ”AS IS” BASIS, WITHOUT WARRANTIES OR CONDI- TIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE.
    [Show full text]
  • Is Bob Sending Mixed Signals?
    Is Bob Sending Mixed Signals? Michael Schliep Ian Kariniemi Nicholas Hopper University of Minnesota University of Minnesota University of Minnesota [email protected] [email protected] [email protected] ABSTRACT Demand for end-to-end secure messaging has been growing rapidly and companies have responded by releasing applications that imple- ment end-to-end secure messaging protocols. Signal and protocols based on Signal dominate the secure messaging applications. In this work we analyze conversational security properties provided by the Signal Android application against a variety of real world ad- versaries. We identify vulnerabilities that allow the Signal server to learn the contents of attachments, undetectably re-order and drop messages, and add and drop participants from group conversations. We then perform proof-of-concept attacks against the application to demonstrate the practicality of these vulnerabilities, and suggest mitigations that can detect our attacks. The main conclusion of our work is that we need to consider more than confidentiality and integrity of messages when designing future protocols. We also stress that protocols must protect against compromised servers and at a minimum implement a trust but verify model. 1 INTRODUCTION (a) Alice’s view of the conversa-(b) Bob’s view of the conversa- Recently many software developers and companies have been inte- tion. tion. grating end-to-end encrypted messaging protocols into their chat applications. Some applications implement a proprietary protocol, Figure 1: Speaker inconsistency in a conversation. such as Apple iMessage [1]; others, such as Cryptocat [7], imple- ment XMPP OMEMO [17]; but most implement the Signal protocol or a protocol based on Signal, including Open Whisper Systems’ caching.
    [Show full text]
  • Learn Online with Cisco Live!
    Cisco Unified Communications and Microsoft Integrations Darren Henwood, Technical Solution Architect Common Customer Situations Windows Phones Office IP Communicator Video Endpoints Lync (IM&P) Lync (P2P) Video Bridges 3 Agenda Office Client System Meeting Integration Integration Integration Integration 4 Office Integration 5 Outlook Integration 2010/2013 2016 6 Contact Card Integration Contact Card Integration • Cisco Jabber for Windows uses published Microsoft Office APIs to provide Cisco communications tasks directly from Office applications Presence Instantly view the availability of your contacts Chat / IM Voice/Video Launch Jabber chat Launch Jabber high definition sessions directly from video calls directly from Office Office Contact Card Contact Card 7 Microsoft SharePoint Integration Adam McKenzie 8 Requirements AD [HKEY_CURRENT_USER\Software\IM Providers\Cisco Jabber] "UpAndRunning"=dword:00000002 9 Application Interoperability Additional Integrations Powered by Cisco Jabber… Outlook Web Access (OWA) integration with Cisco Jabber Web SDK http://www.pstech.rs/business-solutions/connectors/cisco- jabber-microsoft-owa/ 10 Application Interoperability Additional integrations powered by Cisco Jabber… Jabborate integrations with Cisco Jabber Web SDK Web based user experience cross multiple platforms • Microsoft SharePoint • IBM Connections • SAP http://www.jabborate.com 11 Client Integration 12 CUCILync (incl SfB) Experience Old Experience New Experience 13 CUCILync (incl SfB) Experience IM&P (SIMPLE) • Create CSF device • Existing regions, etc • Controlled devices • Softphone • Hardphone Voice/Video (SIP) • Standard MSI 14 Simplify User Experience Registry Editor HKLM\Software\Policies\Microsoft\Office\15.0\Lync\TelephonyMode=5 15 System Integration 16 System Integration 17 Architectural Considerations 18 Platforms 19 Microsoft Lync (2010 & 2013) • SIP/SIMPLE Federation • XMPP Federation • For Microsoft Lync 2010 and Office Communication Server 2007 via a separate OCS 2007 R2 XMPP Gateway.
    [Show full text]
  • Screener Shared Media Player Project Report
    Screener Shared Media Player Project Report Dwayne Bent Jateen Joshi [email protected] [email protected] Jonathan M. Smith Advisor April 27, 2009 Abstract Screener is a cross-platform media player which enables geographi- cally disperse participants to enjoy media together as if they were all at a \screening party." Screener enables participants to have a synchronized experience such that if one participant pauses the media then the media is paused for all participants; if one participant seeks to a certain time, all participants seek to that time, et cetera. All participants can also com- municate through text using the open Extensible Messaging and Presence Protocol (XMPP). Screener allows for the use of "video overlays", PNG images that can overlayed on top of the playing video. Screener allows participants to use local media or any media accessible through a URI. Screener supports a variety of features. Screener can play a wide va- riety of formats, it supports N-way synchronization, text chat, and video overlays. Screener utilizes open source libraries and open standards such as the GStreamer media framework, XMPP through the library xmpppy, and the Python programming language. 1 1 Related Work There are a variety of web applications, plugins, and desktop applications that have a subset of features similar to those proposed for Screener. Most, however, are closed source and don't have many features required for the proposed ex- perience or are too restrictive to be generally useful. Major examples of such projects are listed below. 1.1 NBC Viewing Parties NBC Viewing Parties are a feature of NBC's online video site.
    [Show full text]
  • Considerations for Deploying a Geographically Distributed Video Conferencing System
    Considerations for deploying a geographically distributed video conferencing system Boris Grozev George Politis Emil Ivov Thomas Noel Atlassian and Atlassian and Atlassian University of Strasbourg University of Strasbourg University of Strasbourg [email protected] [email protected] [email protected] [email protected] Abstract—In this paper we report on our ongoing work to the user experience in video conferencing applications, and in improve the user experience of video conferencing by using geo- particular those based on WebRTC. location. We discuss the problem of selecting a media server for In this paper we describe a state-of-the-art multi-party video a video conference, introduce one state-of-the-art system which uses a simple method, and discuss a model for distributing conferencing system, which uses centralized media servers a conference among a set of media servers. We perform a with a basic form of geo-location. We analyze its performance measurement study of a production service, and find that in many and propose the first steps towards improving it. More specif- cases, contrary to common wisdom, connecting each participant ically, we explore the extent to which we can improve the to their closest server is not only costly, but counter-productive system if we introduce a distributed mode, in which a single in terms of decreasing the round-trip time. While, the approach may still seem viable in some use cases, more research is needed conference can be split to multiple servers. in order to understand when that may be, and define specific We structure the remainder of this paper as follows: section algorithms for server selection in the case of a distributed media II discusses other work related to our problem; section III conference.
    [Show full text]
  • Smartserver XMPP Client Developer's Guide
    SmartServer XMPP Client Developer’s Guide 078-0471-01A Echelon, LON, LONWORKS, LonTalk, Neuron, LONMARK, 3120, 3150, LNS, LonMaker, and the Echelon logo are trademarks of Echelon Corporation registered in the United States and other countries. LonPoint and LonSupport are trademarks of Echelon Corporation. Other brand and product names are trademarks or registered trademarks of their respective holders. Neuron Chips, LonPoint Modules, and other OEM Products were not designed for use in equipment or systems which involve danger to human health or safety or a risk of property damage and Echelon assumes no responsibility or liability for use of the Neuron Chips or LonPoint Modules in such applications. Parts manufactured by vendors other than Echelon and referenced in this document have been described for illustrative purposes only, and may not have been tested by Echelon. It is the responsibility of the customer to determine the suitability of these parts for each application. ECHELON MAKES NO REPRESENTATION, WARRANTY, OR CONDITION OF ANY KIND, EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE OR IN ANY COMMUNICATION WITH YOU, INCLUDING, BUT NOT LIMITED TO, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, SATISFACTORY QUALITY, FITNESS FOR ANY PARTICULAR PURPOSE, NONINFRINGEMENT, AND THEIR EQUIVALENTS. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of Echelon Corporation. Printed
    [Show full text]
  • Whiteboard-Based Teleconferencing Application on Mobile Devices Over Existing Xmpp Servers
    WHITEBOARD-BASED TELECONFERENCING APPLICATION ON MOBILE DEVICES OVER EXISTING XMPP SERVERS John Bennedict T. Lorenzo and Rowel O. Atienza Electrical and Electronics Engineering Institute, University of the Philippines, Diliman, Quezon City, Philippines Keywords: Remote Collaboration, Digital Whiteboard, VoIP, Mobile Application. Abstract: The need for internet teleconferencing is fueled by businesses which do not have the time and resources to transport all the needed employees located around the world to work on a project or collaborate on an idea. Current solutions to internet teleconferencing include VoIP and video conferencing, e.g. Skype. VoIP permits a natural way of communication through voice but lacks visual information communication. On the other hand, video conferencing requires a lot of bandwidth. The proposed approach uses a shared drawing board, which all collaborators can see in realtime, together with VoIP to provide an intuitive and effective communication medium. Our approach requires less bandwidth than video conferencing and is able to communicate ideas such as ways of solving a circuit problem, collaborating on an interface prototype for a new project, or strategizing a basketball game. Our approach utilizes the touch screen interface of current tablets and smartphones as an intuitive way to draw. The application uses Google’s existing XMPP servers, for three reasons: (1) most people already have accounts on them, (2) those accounts have existing contacts, and (3) offload server maintenance to another entity. The system obtained a passing SUS score and a lower than expected MOS. 1 INTRODUCTION whiteboards or blackboards on lecture halls in a university. Collaboration over the internet is a convenient way Looking at the available technologies for remote to meet people from across the globe without having collaboration, videoconferencing systems can bring to wait for them to arrive and without spending for a more realistic collaboration experience to users.
    [Show full text]
  • Nabu – a Semantic Archive for XMPP Instant Messaging
    Nabu – A Semantic Archive for XMPP Instant Messaging Frank Osterfeld, Malte Kiesel, Sven Schwarz DFKI GmbH - Knowledge Management Dept. Erwin-Schrodinger-Straße,¨ Bldg. 57 D-67663 Kaiserslautern, Germany {frank.osterfeld, malte.kiesel, sven.schwarz}@dfki.de Abstract While e-mail can be archived in a long-term manner on server-side using the IMAP standard, there is no standard for Instant messaging (IM) has become more and more archiving IM conversations. Chat logs are mostly stored lo- common these days, and is complementing e- cally on the client machine, using proprietary file formats. mail and other means of electronic communication. This has several disadvantages: storing the archive locally on However, due to its heavily context-dependent na- the client computers is inconvenient when using more than ture, searching archives of instant messages using one computer, archives are spread over different installations, only full text search is a tedious task. Also, in and they quickly become out of sync. In addition, informa- contrast to mails, files, and other electronic me- tion gets lost easily. Using proprietary, client- and protocol- dia, instant messages typically do not feature a specific formats to store the information complicates manag- unique identifier or location, making it difficult to ing and searching the stored information using other inter- reference a particular instant messaging conversa- faces than the client UI. tion. Nabu is a semantic archive for XMPP in- In this paper we present Nabu1, an open–source system stant messaging designed to address these problems providing server-side logging of instant messages. Nabu is by implementing a semantic message store, using implemented for the XML-based Jabber/XMPP protocol2.
    [Show full text]
  • The Role of Spring in an ESB.Pdf
    Welcome to The Role of Spring in an ESB Mark Fisher Interface21 [email protected] Introduction Enterprise Service Bus (ESB) Key Topics: – Messaging – Transformation – Routing www.springone.com Introduction: Messaging low-impact extensibility promotes encapsulation (vis a vis RPC) normalized / canonical format scalable (avoids n(n-1)/2 endpoints) Service A Service B Message Message www.springone.com Introduction: Transformation data format change data enhancement / modification message normalization if XML-based, may use XSLT Service A Object Transformer XML Service B www.springone.com Introduction: Routing content-based (CBR) by payload type content-based by property’s value rule-based (JSR-94) if XML-based, may use XPath Service B Service A Message CBR Service C www.springone.com An ESB has…MANY BUZZWORDS According to Wikipedia: “In computing, an enterprise service bus refers to a software architecture construct, implemented by technologies found in a category of middleware infrastructure products usually based on Web services standards, that provides foundational services for more complex service-oriented architectures via an event-driven and XML-based[1] messaging engine (the bus). An enterprise service bus generally provides an abstraction layer on top of an Enterprise Messaging System which allows integration architects to exploit the value of messaging without writing code. Contrary to the more classical EAI approach of a monolithic stack in a hub and spoke architecture, the foundation of an enterprise service bus is built of
    [Show full text]