Try : Insurtech, Application Development

AgriTech(1)

Augmented Reality(20)

Clean Tech(8)

Customer Journey(17)

Design(44)

Solar Industry(8)

User Experience(67)

Edtech(10)

Events(34)

HR Tech(3)

Interviews(10)

Life@mantra(11)

Logistics(5)

Strategy(18)

Testing(9)

Android(48)

Backend(32)

Dev Ops(11)

Enterprise Solution(29)

Technology Modernization(8)

Frontend(29)

iOS(43)

Javascript(15)

AI in Insurance(38)

Insurtech(66)

Product Innovation(57)

Solutions(22)

E-health(12)

HealthTech(24)

mHealth(5)

Telehealth Care(4)

Telemedicine(5)

Artificial Intelligence(146)

Bitcoin(8)

Blockchain(19)

Cognitive Computing(7)

Computer Vision(8)

Data Science(21)

FinTech(51)

Banking(7)

Intelligent Automation(27)

Machine Learning(47)

Natural Language Processing(14)

expand Menu Filters

5 key points from day 3, Google I/O 2017

In continuation of the last two days the IO event became more detail oriented with deep dive technical sessions covering various aspects of the improvements in Google products and enhanced capabilities that developer can access.

c_93a5qvyaejdde-large

Here is our summary of some important discussions.

1.Improved sign-in, payments and forms in Apps

Google is trying to tackle the challenges of critical flows like login, payments and forms by using new APIs. Android now has Autofill, Google Smart Lock, and Backup and Restore APIs for your apps. These new APIs will help users

1) The login and payment experience,

2) Seamlessly syncing logins between your website and mobile app, and

3) Preventing users from getting locked out when they switch devices.

Watch the complete video here Link

2. Android meets TensorFlow

TensorFlow is powering google AI. A detailed session on AI technology for production Android apps was conducted. One of the main benefits of TensorFlow is Portability. You can easily move the neural network model to Android and run the prediction inside mobile phones, to do many AI tricks things like image recognition, motion recognition and etc.

Google provided the tips and tricks to overcome the challenges of the model size and CPU consumption for neural network prediction.

Watch the complete video here Link

3. Performance and Memory improvements in Android Run Time

Android Run Time (ART) is getting major improvements like the new concurrent copying garbage collector (GC) based on read barriers, and improvements to the ahead-of-time (AOT) and just-in-time (JIT) compiler. The new GC will reduce pause times and heap sizes compared to its predecessor.

Watch full video here Link

4. Kotlin

kotlin_800x320

Kotlin is now an officially supported language for Android. Kotlin is a language that runs on the JVM (Java Virtual Machine), and it’s already possible to use Kotlin and many other JVM languages for Android development.  This is the Link https://youtu.be/X1RVYt2QKQE to know the tips for developers to get started with it.

5. Machine Learning APIs

Google has introduced new machine earning APIs that provide access to pre-trained machine learning models with a single API call. Now you can make use of Google’s machine learning expertise to power your applications. Google Cloud Platform (GCP) offers five APIs that provide : Google Cloud Vision API, Cloud Speech API, Cloud Natural Language API, Cloud Translation API and Cloud Video API. Using these APIs, you can focus on adding new features to your app rather than building and training your own custom models.

watch full video here Link

Cancel

Knowledge thats worth delivered in your inbox

Lake, Lakehouse, or Warehouse? Picking the Perfect Data Playground

By :

In 1997, the world watched in awe as IBM’s Deep Blue, a machine designed to play chess, defeated world champion Garry Kasparov. This moment wasn’t just a milestone for technology; it was a profound demonstration of data’s potential. Deep Blue analyzed millions of structured moves to anticipate outcomes. But imagine if it had access to unstructured data—Kasparov’s interviews, emotions, and instinctive reactions. Would the game have unfolded differently?

This historic clash mirrors today’s challenge in data architectures: leveraging structured, unstructured, and hybrid data systems to stay ahead. Let’s explore the nuances between Data Warehouses, Data Lakes, and Data Lakehouses—and uncover how they empower organizations to make game-changing decisions.

Deep Blue’s triumph was rooted in its ability to process structured data—moves on the chessboard, sequences of play, and pre-defined rules. Similarly, in the business world, structured data forms the backbone of decision-making. Customer transaction histories, financial ledgers, and inventory records are the “chess moves” of enterprises, neatly organized into rows and columns, ready for analysis. But as businesses grew, so did their need for a system that could not only store this structured data but also transform it into actionable insights efficiently. This need birthed the data warehouse.

Why was Data Warehouse the Best Move on the Board?

Data warehouses act as the strategic command centers for enterprises. By employing a schema-on-write approach, they ensure data is cleaned, validated, and formatted before storage. This guarantees high accuracy and consistency, making them indispensable for industries like finance and healthcare. For instance, global banks rely on data warehouses to calculate real-time risk assessments or detect fraud—a necessity when billions of transactions are processed daily, tools like Amazon Redshift, Snowflake Data Warehouse, and Azure Data Warehouse are vital. Similarly, hospitals use them to streamline patient care by integrating records, billing, and treatment plans into unified dashboards.

The impact is evident: according to a report by Global Market Insights, the global data warehouse market is projected to reach $30.4 billion by 2025, driven by the growing demand for business intelligence and real-time analytics. Yet, much like Deep Blue’s limitations in analyzing Kasparov’s emotional state, data warehouses face challenges when encountering data that doesn’t fit neatly into predefined schemas.

The question remains—what happens when businesses need to explore data outside these structured confines? The next evolution takes us to the flexible and expansive realm of data lakes, designed to embrace unstructured chaos.

The True Depth of Data Lakes 

While structured data lays the foundation for traditional analytics, the modern business environment is far more complex, organizations today recognize the untapped potential in unstructured and semi-structured data. Social media conversations, customer reviews, IoT sensor feeds, audio recordings, and video content—these are the modern equivalents of Kasparov’s instinctive reactions and emotional expressions. They hold valuable insights but exist in forms that defy the rigid schemas of data warehouses.

Data lake is the system designed to embrace this chaos. Unlike warehouses, which demand structure upfront, data lakes operate on a schema-on-read approach, storing raw data in its native format until it’s needed for analysis. This flexibility makes data lakes ideal for capturing unstructured and semi-structured information. For example, Netflix uses data lakes to ingest billions of daily streaming logs, combining semi-structured metadata with unstructured viewing behaviors to deliver hyper-personalized recommendations. Similarly, Tesla stores vast amounts of raw sensor data from its autonomous vehicles in data lakes to train machine learning models.

However, this openness comes with challenges. Without proper governance, data lakes risk devolving into “data swamps,” where valuable insights are buried under poorly cataloged, duplicated, or irrelevant information. Forrester analysts