Microservice architecture works on the principle of displaying only the relevant details to the end-user. It conceals the complexities associated with software and hardware, operating systems, and development toolkits inside a standard service available to employees on network.

IT personnel refer to this functionality as an “abstraction layer”. If an employee is using a certain application and even if its vendors completely modify the physical location of the data center, hardware, or the programing language, the productivity of the application will not be affected in any manner. CIOs will find that for an internal software application, they no longer have to worry about the time-consuming and expensive labor of rewriting complex connections and interfaces between systems when using microservice architecture. The architecture runs on a standardized order management process and will deliver the exact results regardless of the application used, and the shift to a different platform will be seamless for any application that uses the service.

Best ways to implement a microservice architecture

IT leaders state that the best way to integrate the service is by using them in the organization’s service architecture. Most business applications and modern end-user applications are high-level logic and end-user interface that interacts via multiple microservices.

CIOs must be aware that these services require keys or registration and some services require payment after a point. This investment is however, less compared to building custom codes and maintaining them. Employees working on building microservices can identify the key services that the organization can deploy either externally or internally. Some examples of internal microservice include customer information that can be utilized by the organization’s customer support team, call center, and logistics application.

Microservices as a part of the technology tack

CIOs acknowledge that microservices have leveled the technology playing area to a huge extent. They are considering investing in it, as a measure to decrease the dependency on the legacy and proprietary systems. Using internal microservices ensures that organizations are independent of particular software or hardware third-party vendor and can easily upgrade parts of the infrastructure without affecting other applications.

Many IT leaders have put the concept of exploring microservices on hold as they consider the idea to be confusing and complex, but the service is pretty easy to be implemented.

The post Advantages of Embracing Micro services appeared first on Artificial Intelligence.

Digging towards more technical aspects of new-age technologies like Artificial Intelligence, Machine Learning, and Data Science, we come across various platforms, tools, and libraries that support the algorithms of these innovative approaches. But when it comes to robotics, all we can think of is mechanical parts and a mere intelligent software that helps operate it.

Little did we know about Robotics Operating Systems (ROS), which is also a great part of Robotics mechanisms.

As noted by the Tech Republic, “ROS” stands for robot operating system, though it’s not really an operating system; instead, it’s a set of software libraries and tools that help developers build robot applications. While ROS (1.0) started off as more of an academic, hobbyist tool, a new version was released in 2017 (2.0) that has a more enterprise flavor, with support for real-time, multiple robots working together, production environments, and more. Though it sounds like a cool upgrade on a venerable (non) operating system, ROS 2 broke many of the APIs that ROS developers depend on.”

Moreover, in an interview with IEEE Spectrum, Brian Gerkey, CEO of Open Robotics, the foundation behind ROS development said, “but it’s still worth it to make the jump to ROS 2. The future of robotics depends on it.”

What Changed from ROS 1 to ROS 2?

Each change is described as briefly as possible from ROS1 to ROS 2.

Platforms

ROS 1 is only being CI tested on Ubuntu. It is actively supported by the community on other Linux flavors as well as OS X.

ROS 2 is currently being CI tested and supported on Ubuntu Xenial, OS X El Capitan as well as Windows 10 (see ci.ros2.org).

Languages

C++ standard

The core of ROS 1 is targeting C++03 and doesn’t make use of C++11 features in its API. ROS 2 uses C++11 extensively and uses some parts from C++14. In the future ROS 2 might start using C++17 as long as it is supported on all major platforms.

Python

ROS 1 is targeting Python 2. ROS 2 requires at least Python version 3.5.

Reusing existing middleware

ROS 1 uses a custom serialization format, a custom transport protocol as well as a custom central discovery mechanism. ROS 2 has an abstract middleware interface, through which serialization, transport, and discovery is being provided. Currently, all implementations of this interface are based on the DDS standard. This enables ROS 2 to provide various Quality of Service policies that improve communication over different networks.

Build system

For more information about the build system please see the ament article.

Support other build systems beside CMake

Every ROS package is a CMake project. In ROS 2 other build systems can be easily supported. For now, the build tool supports plain Python packages beside CMake.

Python packages

In ROS 1 a package with Python code can only use a small subset of the features available in setup.py files since the setup.py file is being processed by custom logic from within CMake. In ROS 2 a Python package can use anything in setup.py files, e.g. entry points since they are being invoked with python3 setup.py install.

Environment setup

In ROS 1 the build tool generates scripts that must be sourced in order to set up the environment before being able to use the built ROS packages. This approach only works when the ROS packages are being built with ROS specific build tool.

In ROS 2 the environment setup is separated into package-specific scripts and workspace-specific scripts. Each package provides the necessary scripts to make itself usable after being built. The build tool only invokes the workspace-specific scripts which then call the package-specific scripts.

The post DIVING INTO THE FUNCTIONING OF ROBOTICS OPERATING SYSTEMS (ROS) appeared first on Artificial Intelligence.

The global robot operating system market is anticipated to grow at an exponential rate, according to a report by Transparency Market Research. Top six vendors in the market are ABB Ltd., Clearpath Robotics, Omron Adept Technologies Inc, iRobot Corporation, Kuka AG, and Stanley Innovation, who are continuously investing in research and development activities, thus balancing the supply-demand chain. Companies like ABB and Faunc Corporation are looking forward to invest more on research and innovation, in order to make quality robots and a better ROS. These organizations are expanding geographical footprints by collaborating or acquiring local company in order to reach to the target customers. These expansion of these major players are providing a lucrative demand for ROS market.

It is anticipated that the healthcare industry to boost the growth of the ROI market under the commercial and industrial sectors. Healthcare sector is expected to push the growth of the market. Geographically, Asia Pacific has shown an impressive growth in robots, both in volume and robots.

Countries such as Japan, Thailand, and The republic of Korea manufacturing commercial and industrial robots both in high volume and is expected to show in years to come. The global robot operating system is anticipated to rise with a CAGR of 8.8% during the forecast period which is from 2018 to 2026. During this period the market is envisaged to reach US$402.7 mn.

Rise In Funds for Research and Developments, Promotes the Market Growth

Factors such as adoption and funding in research and development activities is expected to drive the global ROS market. Rise in need of hardware and software which are easily adopted in research work and at considerable low amount is trying to boost the growth of the market. ROS helps in reducing the complexities of while developing robotics projects. Other factors such as the increase in speed during the software development process by ROS is considered as one of the major reason behind the upswing of the market. These days, healthcare facilities are showing interest in robotics, by bringing robots in operation theatre. Robots have already gained the trust of patients and doctors, and is expected to continue growing in future.

Request To Access Market Data Robot Operating System (ROS) Market

Customized Robots Makes the Demand Grow For the Market

Commercial robots have seen a surge in the inflow of funds, in order to develop a user-friendly operating system.  The ROS market is witnessing a surge in installation and deployment of commercial and industrial robots throughout the world, is pushing the market growth during the forecast period. It is anticipated due to these factors, that there will be more than 1.9 million of robots all around the world, due to its flexibility and user friendly nature.  The market is known to see a rise in the demand for customized order. Robot making organization can easily pull out the required code from the web and can provide with the customized robots or ROS.

The post Robot Operating System (ROS) Market To 2026 Pin-Point Analysis For Changing Competitive Dynamics appeared first on Artificial Intelligence.

Google uses a clustering algorithm to automatically analyze Android apps and detect which ones can be considered intrusive, write Google security engineers Martin Pelikan, Giles Hogben, and Ulfar Erlingsson.

Intrusive apps are those that require the user to grant a larger set of capabilities than what would be strictly required for their proper functioning. For example, as Google engineers explain, a coloring book app will not usually need access to geolocation data. Other examples of capabilities that not all apps need to do their job are access to personal data, camera, address book, etc. Granting more privileges than strictly necessary is a potentially harmful, since you cannot really know what those data are used for. Among the most frequent cases of harmful app behaviours are: backdoors, spyware, data collection, denial of service, and many more.

The approach that Google follows to detect intrusive apps is based on the concept of functional peer group, i.e. a group of apps that share similar features and that should therefore require a similar set of authorizations. Once those groups are formed, it becomes possible to detect anomalous apps in each group, meaning those apps that require more privileges than similar apps do. This approach requires monitoring the Android Play Store, collecting detailed statistics, and discovering user expectations, so that app groups can be determined automatically. Indeed, according to Google engineers, fixed categorization and manual curation would be a tedious and error-prone task.

To make this approach more effective, Google uses deep learning to discover groups of apps that share similar characteristics using those apps’ metadata, which include textual descriptions and install metrics. Once peer groups are defined, anomaly detection is used inside of each group to identify anomalous apps, i.e. apps that show a mismatch between the privileges they require and their functionality. Anomalous apps are then inspected thoroughly to decide which ones are actually intrusive. That information is used also to determine which apps should be promoted, as well as to get in touch with potentially intrusive apps’ developers and help them improve the privacy and security of their apps.

The post Google Uses Machine Learning to Identify Intrusive Android Apps appeared first on Artificial Intelligence.