Geo-replication systems are designed to provide improved availability and disaster tolerance by using geographically distributed data centers. This is intended to improve the response time for applications such as web portals. Geo-replication can be achieved using software, hardware or a combination of the two. == Software == Geo-replication software is a network performance-enhancing technology that is designed to provide improved access to portal or intranet content for users at the most remote parts of large organizations. It is based on the principle of storing complete replicas of portal content on local servers, and then keeping the content on those servers up-to-date using heavily compressed data updates. === Portal acceleration === Geo-replication technologies are used to provide replication of the content of portals, intranets, web applications, content and data between servers, across wide area networks WAN to allow users at remote sites to access central content at LAN speeds. Geo-replication software can improve the performance of data networks that suffer limited bandwidth, latency and periodic disconnection. Terabytes of data can be replicated over a wide area network, giving remote sites faster access to web applications. Geo-replication software uses a combination of data compression and content caching technologies. differencing technologies can also be employed to reduce the volume of data that has to be transmitted to keep portal content accurate across all servers. This update compression can reduce the load that portal traffic places on networks, and improve the response time of a portal. === Portal replication === Remote users of web portals and collaboration environments will frequently experience network bandwidth and latency problems which will slow down their experience of opening and closing files, and otherwise interacting with the portal. Geo-replication technology is deployed to accelerate the remote end user portal performance to be equivalent to that experienced by users locally accessing the portal in the central office. === Differencing engine technologies === To deliver this reduction in the size of the required data updates across a portal, geo-replication systems often use differencing engine technologies. These systems are able to difference the content of each portal server right down to the byte level. This knowledge of the content that is already on each server enables the system to rebuild any changes to the content on one server, across each of the other servers in the deployment from content already hosted on those other servers. This type of differencing system ensures that no content, at the byte level, is ever sent to a server twice. === Offline portal replication on laptops === Geo-replication systems are often extended to deliver local replication beyond the server and down to the laptop used by a single user. Server to laptop replication enables mobile users to have access to a local replica of their business portal on a standard laptop. This technology may be employed to provide in the field access to portal content by, for example, sales forces and combat forces. == Geo-replication systems ==
Elastic cloud storage
An elastic cloud is a cloud computing offering that provides variable service levels based on changing needs. Elasticity is an attribute that can be applied to most cloud services. It states that the capacity and performance of any given cloud service can expand or contract according to a customer's requirements and that this can potentially be changed automatically as a consequence of some software-driven event or, at worst, can be reconfigured quickly by the customer's infrastructure management team. Elasticity has been described as one of the five main principles of cloud computing by Rosenburg and Mateos in The Cloud at Your Service - Manning 2011. == History == Cloud computing was first described by Gillet and Kapor in 1996; however, the first practical implementation was a consequence of a strategy to leverage Amazon's excess data center capacity. Amazon and other pioneers of the commercial use of this technology were primarily interested in providing a “public” cloud service, whereby they could offer customers the benefits of using the cloud, particularly the utility-based pricing model benefit. Other suppliers followed suit with a range of cloud-based models all offering elasticity as a core component, but these suppliers were only offering this service as an element of their public cloud service. Due to perceived weaknesses in security, or at least a lack of proven compliance, many organizations, particularly in the financial and public sectors, have been slow adopters of cloud technologies. These wary organizations can achieve some of the benefits of cloud computing by adopting private cloud technologies. An alternative form of the elastic cloud has been offered by vendors such as EMC and IBM, whereby the service is based around an enterprise's own infrastructure but still retains elements of elasticity and the potential to bill by consumption. == Description == Elasticity in cloud computing is the ability for the organization to adjust its storage requirements in terms of capacity and processing with respect to operational requirements. This has the following benefits: Operational Benefits - Services can be acquired quickly, meaning that the evolving requirements of the business can be addressed almost immediately, giving an organization a potential agility advantage. A properly implemented elastic system will provision/de-provision according to application demands, so if a particular business has activity spikes then the provision can be enabled to match the demand and the capacity can be re-allocated. Research and Development (R&D) Projects - R&D activities are no longer hindered by a requirement to secure a capex budget prior to a project starting. Capability can simply be provisioned from the cloud and released at the end of the exercise. Testing and Deployment - With most large-scale projects a size test needs to be performed prior to final rollout. By taking advantage of the elasticity of the cloud and creating a full-scale avatar of the proposed production system, realistic data and traffic volumes can be provisioned and released as needed. Expensive Resources Allocated - This will normally apply only in the context where a customer is applying at least some of their own servers as part of a cloud infrastructure, specifically where a business (for performance reasons) has decided to invest in solid-state storage as opposed to spinning platters. There are instances when, due to activity spikes, a less critical process may need to be moved from the high-performance resources to more traditional storage. Server Specification - When a customer has elected to own/lease hardware, they can select and specify servers that are specifically tuned to meet the likely needs of their operation (i.e., directly controlling the cost/benefit equation). Utility Based Payments - There is, of course, a key cost driver in this process, and the notion that you should pay for what you consume is acceptable for many organizations. When hardware capacity is sourced internally, organizations need to over-provision. This applies just as much to traditional outsourcing as it does to capex-related expenditure on in-house servers. Cloud Platform – At the heart of any cloud storage system is the ability to manage hyperscale object storage and a Hadoop Distributed Files System (HDFS). Elastic storage capability is particularly well suited to hyperscale and Hadoop environments, where its capability to rapidly respond to changing circumstances and priorities is essential
Transliteracy
Transliteracy is "a fluidity of movement across a range of technologies, media and contexts". It is an ability to use diverse techniques to collaborate across different social groups. Transliteracy combines a range of capabilities required to move across a range of contexts, media, technologies and genres. Conceptually, transliteracy is situated across five capabilities: information capabilities (see information literacy), ICT (information and communication technologies), communication and collaboration, creativity and critical thinking. It is underpinned by literacy and numeracy. (See figure below) The concept of transliteracy is impacting the system of education and libraries. == History == While the term appears to come from the prefix trans- ('across') and the word literacy, the scholars who coined it say they developed it from the practice of transliteration, which means to use the letters of one language to write down a different language. The study of transliteracy was first developed in 2005 by the Transliteracies Research Project, directed by University of California at Santa Barbara Professor Alan Liu. The concept of 'transliteracies' was developed as part of research into online reading. It was shared and refined at the Transliteracies conference, held at UC Santa Barbara in 2005. The conference inspired the at the time De Montfort University Professor, Sue Thomas, to create the Production in Research and Transliteracy (PART) group, which evolved into the Transliteracy Research Group. The current meaning of transliteracy was defined in the group's seminal paper Transliteracy: crossing divides as "the ability to read, write, and interact across a range of platforms, tools, and media from signing and orality through handwriting, print, TV, radio, and film, to digital social networks." The concept was enthusiastically adopted by a number of professional groups, notably in the library and information field. Transliteracy Research Group Archive 2006–2013 curates numerous resources from this period. For a number of years, there was a gap between significant interest in transliteracy among professional groups and the scarcity of research. A group of academics from the University of Bordeaux considered transliteracy mainly in the school context. Freelance writer and consultant, Sue Thomas, studied transliteracy and creativity, while Suzana Sukovic, executive director of educational research and evidence-based practice at HETI, researched transliteracy in relation to digital storytelling. The first book on the topic, Transliteracy in complex information environment by Sukovic, is based on research and experience with practice-based projects. == Transliteracy in education == Transliteracy is making an impact on the classroom setting because of how technologically advanced younger generations are today. In 2012, Adam Marcus, a teacher and librarian at the New York City Department of Education (NYCDOE), decided to incorporate transliteracy into his school's public library summer reading program. He had a desire to enhance the experience of reading for his students by allowing them to connect to the text differently by using social media. He used a tool called VoiceThread in order to have his students "take part in conversations, formulate ideas, and share higher-order thinking through a variety of media channels: video, audio, text, images, and music". Students were also enabled to communicate with the book's author through blogs and websites, and were given multiple modes of media to comprehend and engage with the text on a deeper level. Some of these examples include an audio-video glossary and web links that aimed to bring the details of the text to life. The results of his experiment were deemed to have a positive effect on the program as students responded well to this interactive experience they were given. Marcus believes that it is important for educators and librarians to enhance storytelling for children by providing them with a modern and transliterate experience that one could not receive back then. The Agence nationale de la recherche funded a program at a French high school from 2013 to 2015, where the transliteracy skills of students were tested and observed. Students were placed in groups of three or four members and were required to use all sorts of media and tools in order to collect data for their projects. They were not allowed to only use digital sources, and were advised to use a diversity of sources. The focus of this experiment was to observe "the possible diversity of media and tools employed, on the ways of and reasons for switching from one to another, on how these different media and tools are distributed within contexts, according to the academic requirements and tasks individually and collectively performed by the students." The conclusions of the experiment dealt with physical space and organization being an issue for students and teachers to deal with. Spatially, it was challenging for students to navigate through different mediums when their space inside the classroom was limited. It was noticed that students were prone to use something that took up less space, rather than focusing on expanding their diversity of sources. Organizationally, it was challenging for students to organize all of the information they collected since everything was not being search and collected for digitally. In addition, students were not allotted a lot of time to complete their projects which also impacted their final product. == Transliteracy in libraries == In 2009, Dr. Susie Andretta, senior lecturer in Information Management at London Metropolitan University, conducted interviews with four different information professionals including an academic librarian, an outreach librarian, a content manager, and a scholar within the library science and information discipline. She was aiming to explore how transliteracy was colliding and combining with the print-world of libraries. Dr. Andretta defines transliteracy as "an umbrella term encompassing different literacies and multiple communication channels that require active participation with and across a range of platforms, and embracing both linear and non-linear messages (3)." The goals of these interviews ranged from the following: to test the information professional's awareness of transliteracy, to have them identify transliteracy and how it is integrated into their work, and to explain the impact transliteracy has had on they library they work at. Andretta found that out of all the information professionals interviewed, it was only the academic librarian who was vaguely familiar with the concept of transliteracy. Bernadette Daly Swanson, an Academic Librarian at UC Davis, expresses in her interview with Dr. Andretta how she would "like to think that the transliterate library is more of an environment where we do different things [...] I would take maybe about a third of the first floor of our library and transform it into a lab [...] where we can start to evolve [..] explore, and experiment in media development, content development, and do it not just with librarians; so open up the space for other people [...] so you don't get people working in isolation." Although the other three candidates that Dr. Andretta interviewed had not heard of the term transliteracy, they responded well to the concept once it was explained to them and agreed with its impact on the workplace. Dr. Michael Stephens, an assistant professor in the Graduate School of Library and Information Science at Dominican University, explains in his interview how the term transliteracy describes the courses he teaches on libraries and Web 2.0 technologies. Dr. Stephens states that students being educated in Web 2.0 technologies gives them "the opportunity to experience what the channel can be and the potential for that sharing learning, for asking questions, just for out loud thinking – I think it's incredibly valuable. [..] this is where this wonderful concept comes in, it was teaching them transliteracy and the fact that they can move across channels without getting worried about it." Dr. Andretta concluded from her interviews how although transliteracy may not be a very well-known term yet, it has nonetheless established itself into the intuition of libraries while also transforming the traditional library to a world of enhanced and expanded services. "Inherent in this transition are the challenges of having to adapt to a constantly changing technological landscape, the multiple literacies that this generates, and the need to establish a multifaceted library profession that can speak the multiple-media languages of its diverse users." Thomas Ipri, a librarian at the University of Nevada, advocates for libraries needing to make a change in their literary functions. He argues that the divide between digital and print makes it harder for libraries to accommodate their patrons and to share information. He f
Chandy–Misra–Haas algorithm resource model
The Chandy–Misra–Haas algorithm resource model checks for deadlock in a distributed system. It was developed by K. Mani Chandy, Jayadev Misra and Laura M. Haas. == Locally dependent == Consider the n processes P1, P2, P3, P4, P5,, ... ,Pn which are performed in a single system (controller). P1 is locally dependent on Pn, if P1 depends on P2, P2 on P3, so on and Pn−1 on Pn. That is, if P 1 → P 2 → P 3 → … → P n {\displaystyle P_{1}\rightarrow P_{2}\rightarrow P_{3}\rightarrow \ldots \rightarrow P_{n}} , then P 1 {\displaystyle P_{1}} is locally dependent on P n {\displaystyle P_{n}} . If P1 is said to be locally dependent to itself if it is locally dependent on Pn and Pn depends on P1: i.e. if P 1 → P 2 → P 3 → … → P n → P 1 {\displaystyle P_{1}\rightarrow P_{2}\rightarrow P_{3}\rightarrow \ldots \rightarrow P_{n}\rightarrow P_{1}} , then P 1 {\displaystyle P_{1}} is locally dependent on itself. == Description == The algorithm uses a message called probe(i,j,k) to transfer a message from controller of process Pj to controller of process Pk. It specifies a message started by process Pi to find whether a deadlock has occurred or not. Every process Pj maintains a boolean array dependent which contains the information about the processes that depend on it. Initially the values of each array are all "false". === Controller sending a probe === Before sending, the probe checks whether Pj is locally dependent on itself. If so, a deadlock occurs. Otherwise it checks whether Pj, and Pk are in different controllers, are locally dependent and Pj is waiting for the resource that is locked by Pk. Once all the conditions are satisfied it sends the probe. === Controller receiving a probe === On the receiving side, the controller checks whether Pk is performing a task. If so, it neglects the probe. Otherwise, it checks the responses given Pk to Pj and dependentk(i) is false. Once it is verified, it assigns true to dependentk(i). Then it checks whether k is equal to i. If both are equal, a deadlock occurs, otherwise it sends the probe to next dependent process. == Algorithm == In pseudocode, the algorithm works as follows: === Controller sending a probe === if Pj is locally dependent on itself then declare deadlock else for all Pj,Pk such that (i) Pi is locally dependent on Pj, (ii) Pj is waiting for 'Pk and (iii) Pj, Pk are on different controllers. send probe(i, j, k). to home site of Pk === Controller receiving a probe === if (i)Pk is idle / blocked (ii) dependentk(i) = false, and (iii) Pk has not replied to all requests of to Pj then begin "dependents""k"(i) = true; if k == i then declare that Pi is deadlocked else for all Pa,Pb such that (i) Pk is locally dependent on Pa, (ii) Pa is waiting for 'Pb and (iii) Pa, Pb are on different controllers. send probe(i, a, b). to home site of Pb end == Example == P1 initiates deadlock detection. C1 sends the probe saying P2 depends on P3. Once the message is received by C2, it checks whether P3 is idle. P3 is idle because it is locally dependent on P4 and updates dependent3(2) to True. As above, C2 sends probe to C3 and C3 sends probe to C1. At C1, P1 is idle so it update dependent1(1) to True. Therefore, deadlock can be declared. == Complexity == Suppose there are n {\displaystyle n} controllers and m {\displaystyle m} processes, at most m ( n − 1 ) / 2 {\displaystyle m(n-1)/2} messages need to be exchanged to detect a deadlock, with a delay of O ( n ) {\displaystyle O(n)} messages.
Information architecture
Information architecture is the structural design of shared information environments, in particular the organisation of websites and software to support usability and findability. The term information architecture was coined by Richard Saul Wurman. Since its inception, information architecture has become an emerging community of practice focused on applying principles of design, architecture and information science in digital spaces. Typically, a model or concept of information is used and applied to activities which require explicit details of complex information systems. These activities include library systems and database development. == Definition == The term information architecture has different meanings in different branches of information systems or information technology. === User experience === In user experience design, information architecture has been described as the structural design of shared information environments, comprising the study and practice of organising and labelling web sites, intranets, online communities, and software to support user experience, in particular, the findability and usability of information. It has also been described as an emerging community of practice focused on bringing principles of design and architecture to the digital landscape. === Information systems === Technically speaking, information architecture comprises the combination of organization, labeling, search and navigation systems within websites and intranets, serving as a navigational aid to the content of information-rich systems. === Data architecture === Information architecture can be described as a subset of data architecture where usable data is constructed, designed, and arranged in a fashion most useful to the users of data. === Systems design === In the field of systems design, for example, information architecture is a component of enterprise architecture that deals with the information component when describing the structure of an enterprise. Some system design practitioners regard information architecture as strictly the application of information science to web design, which considers such issues as classification and information retrieval, and not factors like user experience and information design. == Principles == Principles of information architecture include the following: The principle of objects The principle of choices The principle of disclosure The principle of exemplars The principle of front doors The principle of multiple classification The principle of focused navigation The principle of growth == History == Richard Saul Wurman is credited with coining the term information architecture in relation to the design of information. From 1998 to 2015, Peter Morville and Louis Rosenfeld were co-authors of Information Architecture for the World Wide Web. Other authors include Jesse James Garrett and Christina Wodtke.
Connectionist expert system
Connectionist expert systems are artificial neural network (ANN) based expert systems where the ANN generates inferencing rules e.g., fuzzy-multi layer perceptron where linguistic and natural form of inputs are used. Apart from that, rough set theory may be used for encoding knowledge in the weights better and also genetic algorithms may be used to optimize the search solutions better. Symbolic reasoning methods may also be incorporated (see hybrid intelligent system). (Also see expert system, neural network, clinical decision support system.)
Grid-oriented storage
Grid-oriented Storage (GOS) was a term used for data storage by a university project during the era when the term grid computing was popular. == Description == GOS was a successor of the term network-attached storage (NAS). GOS systems contained hard disks, often RAIDs (redundant arrays of independent disks), like traditional file servers. GOS was designed to deal with long-distance, cross-domain and single-image file operations, which is typical in Grid environments. GOS behaves like a file server via the file-based GOS-FS protocol to any entity on the grid. Similar to GridFTP, GOS-FS integrates a parallel stream engine and Grid Security Infrastructure (GSI). Conforming to the universal VFS (Virtual Filesystem Switch), GOS-FS can be pervasively used as an underlying platform to best utilize the increased transfer bandwidth and accelerate the NFS/CIFS-based applications. GOS can also run over SCSI, Fibre Channel or iSCSI, which does not affect the acceleration performance, offering both file level protocols and block level protocols for storage area network (SAN) from the same system. In a grid infrastructure, resources may be geographically distant from each other, produced by differing manufacturers, and have differing access control policies. This makes access to grid resources dynamic and conditional upon local constraints. Centralized management techniques for these resources are limited in their scalability both in terms of execution efficiency and fault tolerance. Provision of services across such platforms requires a distributed resource management mechanism and the peer-to-peer clustered GOS appliances allow a single storage image to continue to expand, even if a single GOS appliance reaches its capacity limitations. The cluster shares a common, aggregate presentation of the data stored on all participating GOS appliances. Each GOS appliance manages its own internal storage space. The major benefit of this aggregation is that clustered GOS storage can be accessed by users as a single mount point. GOS products fit the thin-server categorization. Compared with traditional “fat server”-based storage architectures, thin-server GOS appliances deliver numerous advantages, such as the alleviation of potential network/grid bottle-necks, CPU and OS optimized for I/O only, ease of installation, remote management and minimal maintenance, low cost and Plug and Play, etc. Examples of similar innovations include NAS, printers, fax machines, routers and switches. An Apache server has been installed in the GOS operating system, ensuring an HTTPS-based communication between the GOS server and an administrator via a Web browser. Remote management and monitoring makes it easy to set up, manage, and monitor GOS systems. == History == Frank Zhigang Wang and Na Helian proposed a funding proposal to the UK government titled “Grid-Oriented Storage (GOS): Next Generation Data Storage System Architecture for the Grid Computing Era” in 2003. The proposal was approved and granted one million pounds in 2004. The first prototype was constructed in 2005 at Centre for Grid Computing, Cambridge-Cranfield High Performance Computing Facility. The first conference presentation was at IEEE Symposium on Cluster Computing and Grid (CCGrid), 9–12 May 2005, Cardiff, UK. As one of the five best work-in-progress, it was included in the IEEE Distributed Systems Online. In 2006, the GOS architecture and its implementations was published in IEEE Transactions on Computers, titled “Grid-oriented Storage: A Single-Image, Cross-Domain, High-Bandwidth Architecture”. Starting in January 2007, demonstrations were presented at Princeton University, Cambridge University Computer Lab and others. By 2013, the Cranfield Centre still used future tense for the project. Peer-to-peer file sharings use similar techniques.