<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>XML Archives - Artificial Intelligence</title>
	<atom:link href="https://www.aiuniverse.xyz/tag/xml/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.aiuniverse.xyz/tag/xml/</link>
	<description>Exploring the universe of Intelligence</description>
	<lastBuildDate>Sat, 18 May 2019 06:00:27 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.2</generator>
	<item>
		<title>Making Sense Of Big Data</title>
		<link>https://www.aiuniverse.xyz/making-sense-of-big-data/</link>
					<comments>https://www.aiuniverse.xyz/making-sense-of-big-data/#comments</comments>
		
		<dc:creator><![CDATA[aiuniverse]]></dc:creator>
		<pubDate>Sat, 18 May 2019 06:00:27 +0000</pubDate>
				<category><![CDATA[Big Data]]></category>
		<category><![CDATA[Big data]]></category>
		<category><![CDATA[cloud based]]></category>
		<category><![CDATA[data mining]]></category>
		<category><![CDATA[JSON]]></category>
		<category><![CDATA[Machine learning]]></category>
		<category><![CDATA[Traditional]]></category>
		<category><![CDATA[XML]]></category>
		<guid isPermaLink="false">http://www.aiuniverse.xyz/?p=3504</guid>

					<description><![CDATA[<p>Source:- metrology.news Big data analytics is the use of advanced analytic techniques against very large, diverse data sets that include structured, semi-structured and unstructured data, from different sources, <a class="read-more-link" href="https://www.aiuniverse.xyz/making-sense-of-big-data/">Read More</a></p>
<p>The post <a href="https://www.aiuniverse.xyz/making-sense-of-big-data/">Making Sense Of Big Data</a> appeared first on <a href="https://www.aiuniverse.xyz">Artificial Intelligence</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Source:- metrology.news</p>
<p>Big data analytics is the use of advanced analytic techniques against very large, diverse data sets that include structured, semi-structured and unstructured data, from different sources, and in different sizes from terabytes to zettabytes.</p>
<p>Big data is a term applied to data sets whose size or type is beyond the ability of traditional relational databases to capture, manage and process the data with low latency. Big data has one or more of the following characteristics: high volume, high velocity or high variety. Artificial intelligence (AI), mobile, social and the Internet of Things (IoT) are driving data complexity through new forms and sources of data. For example, big data comes from sensors, devices, video/audio, networks, log files, transactional applications, web, and social media — much of it generated in real time and at a very large scale.</p>
<p>Analysis of big data allows analysts, researchers and business users to make better and faster decisions using data that was previously inaccessible or unusable. Businesses can use advanced analytics techniques such as text analytics, machine learning, predictive analytics, data mining, statistics and natural language processing to gain new insights from previously untapped data sources independently or together with existing enterprise data.</p>
<p>The life of an enterprise architect is becoming busy and difficult. Before the era of big data, the enterprise architect “only” had to worry about the data and systems within their own data center. However, over the past decade there were revolutionary changes to the way information is used by businesses and how data management platforms support the information available from modern data sources.</p>
<p>Cloud broke down the boundaries of enterprise data centers, with applications housed and data created outside the “four walls” of an organization. This introduced a host of complexities for enterprise architects focused on security, privacy, and control. Mobile influences continued to push data outside the data center. Maintaining data flows to each of those data access points, often as tablets or mobile phones, introduced additional troubles. Incoming data from mobile devices brought new data formats and a flood of information to the enterprise architect.</p>
<p>These alterations in the formats and locations of systems and data created massive change for data-driven organizations who want to develop competitive advantage. That advantage may come in the form of new data sources such as device sensor logs, social media streams, and mobile device geolocation information; create new projects to take advantage of these new data sources; and establish environments with diverse data management platforms to support these efforts.]</p>
<p><strong>New and Exciting Data Sources</strong><br />
The transformations over the past decade mandated and created a range of additional data sources, both inside and outside an organization, for enterprise architects to consider.</p>
<p>External data sources from third-party content, often via cloudbased providers, can change their data structure without notification to downstream organizations using that information. Event log and device sensor information also have variability based on their individual configuration and frequently come in the form of multistructured formats such as XML or JSON. Social data sources created by customers and the general public are based on textual formats and audio/video content. Both text and audio/visual are difficult to store and utilize due to the nature of the information.</p>
<p>Traditional relational data sources are also included in the wave of big data change, but they have their own challenges. Increasingly, the information is coming from outside the data center from third parties or cloud-based implementations of corporate data, which requires enterprise architects to seek out and learn how to utilize that information.</p>
<p>Business-oriented data consumers can manage their own pursuits, which can take the form of data discovery or exploratory activities to find new uses for big data sources. They can be analytical projects to align costs via cost-management activities, or advanced analytical projects to find the next set of attributes for high-revenue customers.</p>
<p>This is not a one-off implementation like a “spreadmart” or an unmanaged shadow IT project. Instead, it is a supervised and administered environment strategically provided to business stakeholders so they can meet their own needs while utilizing corporate assets. This may be in the form of new big data sources and platforms, and capturing valuable metadata that can be utilized across the organization.</p>
<p>Enterprise architects create self-service capabilities for big data. By designing and implementing application environments with configurable software components, empowering technologists through skills development, and actively sanctioning interaction between technology implementation teams and the various lines of business, enterprise architects provide environments where business stakeholders can have requirements met at the “speed of business” rather than the speed of an implementation backlog. The business can focus on how to best use new big data resources without waiting on tactical IT workflows while maintaining the implementation components for distribution and continued development across the organization.</p>
<p>The post <a href="https://www.aiuniverse.xyz/making-sense-of-big-data/">Making Sense Of Big Data</a> appeared first on <a href="https://www.aiuniverse.xyz">Artificial Intelligence</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.aiuniverse.xyz/making-sense-of-big-data/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>The value of APIs and microservices gateway tools</title>
		<link>https://www.aiuniverse.xyz/the-value-of-apis-and-microservices-gateway-tools/</link>
					<comments>https://www.aiuniverse.xyz/the-value-of-apis-and-microservices-gateway-tools/#comments</comments>
		
		<dc:creator><![CDATA[aiuniverse]]></dc:creator>
		<pubDate>Thu, 11 Apr 2019 05:34:07 +0000</pubDate>
				<category><![CDATA[Microservices]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[API management]]></category>
		<category><![CDATA[Application program]]></category>
		<category><![CDATA[Digital Transformation]]></category>
		<category><![CDATA[JSON Web Tokens]]></category>
		<category><![CDATA[XML]]></category>
		<guid isPermaLink="false">http://www.aiuniverse.xyz/?p=3423</guid>

					<description><![CDATA[<p>Source:- searchmicroservices.techtarget.com APIs help run the world. They allow software applications and digital platforms to interact with each other, orchestrating the exchange of requests between apps that have <a class="read-more-link" href="https://www.aiuniverse.xyz/the-value-of-apis-and-microservices-gateway-tools/">Read More</a></p>
<p>The post <a href="https://www.aiuniverse.xyz/the-value-of-apis-and-microservices-gateway-tools/">The value of APIs and microservices gateway tools</a> appeared first on <a href="https://www.aiuniverse.xyz">Artificial Intelligence</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Source:- searchmicroservices.techtarget.com</p>
<p>APIs help run the world. They allow software applications and digital platforms to interact with each other, orchestrating the exchange of requests between apps that have their own architectures. And, when properly managed, APIs ensure a neat, simplified experience for developers.</p>
<p>The challenge is to be sure proper API management is entrenched in your ongoing IT operations. Otherwise, you run the risk of introducing a break change, exposing an API to security vulnerabilities, among other dangers that can disrupt the effectiveness of a modern business.</p>
<h3 class="section-title">The power of a microservices gateway</h3>
<p>The API is an essential part of communication in distributed networks. Digital transformation and other major organizational shifts push companies to deliver cross-device, cross-platform applications, but those initiatives wouldn&#8217;t be possible without the right APIs providing the links between these platforms.</p>
<section class="section main-article-chapter" data-menu-title="The power of a microservices gateway">Traditionally, application program interfaces were used to manage traffic between monolithic applications and clients. In the current era of the web API, developers can integrate disparate internal systems to create distributed microservice applications. If anything bridges the gap between microservices and a traditional system, it&#8217;s an API. It is what exposes the complete usability of microservices and makes them consumable by traditional systems.</p>
<p>Say you have a microservices-based architecture that has more than 100 services. How do you provide a unified entry point to each service? This can be easily managed with the help of an API gateway. When each microservice has a public endpoint, you achieve better integration, and, in turn, you are better serving business objectives.</p>
<p>API management, however, can be arduous. To build a secure and agile API, you need to take a pragmatic approach.</p>
</section>
<section class="section main-article-chapter" data-menu-title="Why API gateways are crucial">
<h3 class="section-title">Why API gateways are crucial</h3>
<p>With an API gateway in front of an API, you create a way for microservices to organize themselves in an orderly way. API gateways allow developers to encapsulate the internal structure of an application in multiple ways, depending upon the use case.</p>
<p>Where an organization can trip itself up is when developers fail to keep a microservices gateway current. Whenever a microservice is added or removed, the gateway needs to be adjusted. For this reason, especially, the update process for your microservices gateway should be made as simple as possible.</p>
<p>Large organizations face the challenge of migrating from their existing monolithic systems to microservices-based architectures. When you want to refactor an existing architecture into cloud-native microservices, the change needs to be made without disruption to your users. To succeed in this, you&#8217;ll need to be able to use the monolithic application as a gateway.</p>
<p>A crucial challenge with microservices is to enable communication among microservices applications, i.e., getting different services to communicate with each other and then return data. How a user&#8217;s call is treated by the client-facing microservice front end is a major task. APIs provide the interface for external callers to properly format a service request.</p>
<p>Cloud-native microservices require rapid releases and additional validations that go beyond the traditional linear development pipeline. These complexities can be managed only with the aid of APIs.</p>
<section class="section main-article-chapter" data-menu-title="Why API gateways are crucial">The large cloud vendors recognize the importance of APIs in the management of container-based applications. In Red Hat&#8217;s view, distributed integration, containers and APIs represent the three pillars of agile integration.</p>
<p>Once your application code is refactored the microservices way, and your infrastructure is distributed with containers, the next logical step is to complement them with an effective API layer. This allows each service to be exposed to the outside world in a predictable and secure manner.</p>
</section>
<section class="section main-article-chapter" data-menu-title="API management pitfalls">
<h3 class="section-title">API management pitfalls</h3>
<p>Companies rely on APIs more than ever. As a result, developers tasked with creating the right API architecture will focus on extensibility instead of getting coiled into the programming language. As they do so, developers should be careful to avoid certain pitfalls of API management.</p>
<p>The following are among the biggest mistakes made in this area:</p>
<ul class="default-list">
<li><strong>Introducing break changes to existing API endpoints.</strong> A break change is when one API is updated and that change causes a break in another existing API. This happens when there isn&#8217;t consistency in API design. Break changes as such must be avoided, and the best way to do this is to establish what your API design will be at the start. This should be the shared culture of your development team irrespective of which team particular developers belong to or their seniority in the organization.</li>
<li><strong>Not separating the APIs from the app.</strong> There&#8217;s a common assumption with API gateways: If the user application that is driven by the API works fine, then your API is perfect. Such assumptions get washed away as soon as your application encounters trouble. Your efforts to manage an API should be separate from the application. That way you can more easily know whether the API is working as expected.</li>
<li><strong>Not testing your API as an end user.</strong> Even though an API acts as an interface between two applications or services, it should be thought of as a definite application. Check if your API makes it easy for integration to be made or if it scales to real volumes of user traffic. Automated API testing is a starting point, but should also be complemented with testing APIs under real-world conditions on various mobile devices and under peak loads.</li>
<li><strong>Security inadequacy.</strong> When it comes to security, many APIs are mishandled. Without reasonable security provisions, the very foundational functionality will be shaken. With distributed denial-of-service attacks, XML bombs, cross-site scripting and other advanced threats occurring frequently, basic API key authentication might not be enough. A combination of advanced encryption techniques such as JSON Web Tokens and OAuth must be added to ensure zero compromise.</li>
<li><strong>Not identifying future integration mishaps.</strong> Simple integrations seem straightforward &#8212; at least at first. As an application scales, with constantly changing tools, developers face many challenges in the creation and maintenance of integrations. For instance, a developer who initially builds a one-way integration because that was the need at the time will have a hard time when the need to support two-way updates arrives. Furthermore, tools are upgraded every few months. Each change in the integration will create more trouble in traceability. Finally, when the integration fails at some point, the organization suffers as a whole.</li>
</ul>
<p>It&#8217;s important to follow the changing design patterns and anti-patterns, engage the testing team and then map integrations. This also ensures that the next developer coming onboard doesn&#8217;t feel alienated when handling APIs created by other developers.</p>
<p>Anyone who works on a monolithic codebase looks for better code maintainability, and that means making use of APIs. The same will be true for anyone beginning to explore the many advantages of microservices. Success in this arena will depend on remembering that API gateways are an important ally. They help to manage interactions, adapt to change and let developers develop.</p>
<p>APIs have the potential to transform your application delivery. When you avoid the common errors in API management, you free your developers to build application experiences that usher in a new world of possibilities &#8212; thanks to the humble API.</p>
</section>
</section>
<p>The post <a href="https://www.aiuniverse.xyz/the-value-of-apis-and-microservices-gateway-tools/">The value of APIs and microservices gateway tools</a> appeared first on <a href="https://www.aiuniverse.xyz">Artificial Intelligence</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.aiuniverse.xyz/the-value-of-apis-and-microservices-gateway-tools/feed/</wfw:commentRss>
			<slash:comments>4</slash:comments>
		
		
			</item>
	</channel>
</rss>
