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

Hello World but in VR

By :

The mission was simple- create some interactive objects and also a futuristic environment. I stood at the crossroads, uncertain where to begin, so the first thing that I did was open YouTube and type-” how to build your first game in VR”. After watching a couple of videos, one thing was definite-” Oculus “. Oculus is the hardware used for most VR applications. So, I went ahead and placed an order for the Oculus which took around 15 days to get delivered. The unboxing felt like I had the key to the future, and now what? I ended up playing some games to understand how VR works and also just playing games.


Imagination part I

Then, I got a call from my manager-” Vignesh, Where is my metaverse?” 

The burgeoning weight of expectations compelled me to set aside gaming and delve into development. So, hopped onto my laptop which at times was a little specced out. Nevertheless, I started to do some research on how to build VR apps on YouTube, Oculus development page, Unity development page, and a few others. The information was quite overwhelming at the beginning and most of it bounced over my head. Took some time to understand the terminologies used in game engines, effective workflows, and finally how to import 3D models from Blender. I made some test Models in Blender with some free source files “sketchfab.com” because that was the fastest way to run a trial in Unity and Blender. Once I got the free resources, I tried to export it to Unity but for some reason, it was not working. So you guessed it right, YouTube became my refuge, and YES I found the solution. The feeling of successfully importing the 3D file to Unity was like I had accomplished 70% of the task but in reality, it was just 10%. There were a lot more things to figure out, like UV unwrapping, texturing, baking, emission materials, and baking animation which I still need to discover. A month’s time had already passed and I had made no major progress just as I grappled with this, a message from my manager appeared:“ Vignesh, when can I see the metaverse??”



Imagination part II

This is when I realized I needed to learn faster and work more efficiently and by chance I ended up on this amazing YouTube channel called Dilmer Valecillos where he teaches and explains VR development fundamentals and also shares the source code for some tutorials. That’s when I came across Oculus Interaction SDK. SDK (Software development kit) is a framework which apps and software are built upon. Thankfully Oculus development site provides their SDK which helps to develop games for Oculus. Having all the necessary knowledge and resources for development, I began to create 3D models in Blender, import them to Unity, and use the interaction SDK to make the models interactable. 

ALL was fine until I had to install the game into Oculus. The game would simply not install on Oculus. So I did some research and found that I had to change some settings in Unity for it to install.

Finally, I donned the Oculus on eagerly waiting for the game to start, when the loading screen disappeared I could see the environment created in VR but I wasn’t able to move or interact with the objects. This was a huge setback after spending nearly 4 months learning different tools and software needed for the development.


OK! Reality

This setback ushered in introspection and I realized my focus was not on learning the software extensively so, made a plan with the guidance of my manager to focus on one tool at a time and to understand it at the fundamental level. The tools were Blender and Unity, I previously had some experience in 3D so Blender was a bit easier to learn compared to Unity which has coding and I don’t know how to code. The fear of coding was hindering my learning curve in Unity but I figured not everything requires coding. Also, my fellow colleague was kind enough to help me out with coding. We decided that I would be focusing on creating 3D environments and some basic interaction on Unity and Rabi would do the coding. So, we set sail and within a few weeks we were ready to finally show the prototype to our manager. We tried our best to get it as expected but it was far from that and it needed more creative inputs, quality renders, and intuitive interactions. These were a few key pieces of feedback we got from presenting the prototype to the manager.

These experiences will undoubtedly shape my growth as a VR developer and provide valuable insights that extend beyond the world of virtual reality. I hope it resonates with many aspiring people who venture into the world of virtual reality.

P.S. The Project Metaverse is still ongoing.

About the Author: Vignesh is a creative visual designer and quirky art director! With a heart full of innovation, he crafts designs that tell vibrant stories and leave lasting impressions. Beyond design, he’s an adrenaline junkie seeking excitement in life.

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 estimate that 60%-73% of enterprise data goes unused for analytics, highlighting the governance gap in traditional lake implementations.

Is the Data Lakehouse the Best of Both Worlds?

This gap gave rise to the data lakehouse, a hybrid approach that marries the flexibility of data lakes with the structure and governance of warehouses. The lakehouse supports both structured and unstructured data, enabling real-time querying for business intelligence (BI) while also accommodating AI/ML workloads. Tools like Databricks Lakehouse and Snowflake Lakehouse integrate features like ACID transactions and unified metadata layers, ensuring data remains clean, compliant, and accessible.

Retailers, for instance, use lakehouses to analyze customer behavior in real time while simultaneously training AI models for predictive recommendations. Streaming services like Disney+ integrate structured subscriber data with unstructured viewing habits, enhancing personalization and engagement. In manufacturing, lakehouses process vast IoT sensor data alongside operational records, predicting maintenance needs and reducing downtime. According to a report by Databricks, organizations implementing lakehouse architectures have achieved up to 40% cost reductions and accelerated insights, proving their value as a future-ready data solution.

As businesses navigate this evolving data ecosystem, the choice between these architectures depends on their unique needs. Below is a comparison table highlighting the key attributes of data warehouses, data lakes, and data lakehouses:

FeatureData WarehouseData LakeData Lakehouse
Data TypeStructuredStructured, Semi-Structured, UnstructuredBoth
Schema ApproachSchema-on-WriteSchema-on-ReadBoth
Query PerformanceOptimized for BISlower; requires specialized toolsHigh performance for both BI and AI
AccessibilityEasy for analysts with SQL toolsRequires technical expertiseAccessible to both analysts and data scientists
Cost EfficiencyHighLowModerate
ScalabilityLimitedHighHigh
GovernanceStrongWeakStrong
Use CasesBI, ComplianceAI/ML, Data ExplorationReal-Time Analytics, Unified Workloads
Best Fit ForFinance, HealthcareMedia, IoT, ResearchRetail, E-commerce, Multi-Industry
Conclusion

The interplay between data warehouses, data lakes, and data lakehouses is a tale of adaptation and convergence. Just as IBM’s Deep Blue showcased the power of structured data but left questions about unstructured insights, businesses today must decide how to harness the vast potential of their data. From tools like Azure Data Lake, Amazon Redshift, and Snowflake Data Warehouse to advanced platforms like Databricks Lakehouse, the possibilities are limitless.

Ultimately, the path forward depends on an organization’s specific goals—whether optimizing BI, exploring AI/ML, or achieving unified analytics. The synergy of data engineering, data analytics, and database activity monitoring ensures that insights are not just generated but are actionable. To accelerate AI transformation journeys for evolving organizations, leveraging cutting-edge platforms like Snowflake combined with deep expertise is crucial.

At Mantra Labs, we specialize in crafting tailored data science and engineering solutions that empower businesses to achieve their analytics goals. Our experience with platforms like Snowflake and our deep domain expertise makes us the ideal partner for driving data-driven innovation and unlocking the next wave of growth for your enterprise.

Cancel

Knowledge thats worth delivered in your inbox

Loading More Posts ...
Go Top
ml floating chatbot