Podcasts about nipun

Watch this episode featuring Nipun Mehta, Founder of ServiceSpace, to discover why the IDG skill "Mobilisation" is not just about organizing—it's a key to creating meaningful, transformational change rooted in kindness.In this engaging conversation, Nipun shares his journey from Silicon Valley to founding a global community focused on small acts of generosity. He also highlights the importance of shifting from transactional to relational approaches in social movements.00:00 Preview00:43 Introduction01:20 About Nipun Mehta04:02 Nipun and Anita's Karma Kitchen experience10:04 Nipun's big career shift: From tech to service16:17 What Nipun learned on a 1,000 miles walking pilgrimage in India with his wife19:53 The transformative power of compassion23:07 How inner transformation can redefine personal goals and larger systems30:25 How the IDG definition of “Mobilisation” resonates with Nipun34:20 How Nipun's spontaneous act of kindness sparked a street movement in India38:01 Different forms of wealth40:16 What is “Deep Casting”?43:16 Why we need laddership, not leadership47:51 Why the best leaders don't always lead53:22 n integrating social change in a society58:17 Nipun Mehta's Purposeful Empathy storyCONNECT WITH ANITA✩ Email purposefulempathy@gmail.com ✩ Website https://www.anitanowak.com✩ Buy a copy of Purposeful Empathy http://tiny.cc/PurposefulEmpathyCA✩ LinkedIn https://www.linkedin.com/in/anitanowak/✩ Instagram https://tinyurl.com/anitanowakinstagram✩ Podcast Audio https://tinyurl.com/PurposefulEmpathyPodcast✩ Bluesky https://bsky.app/profile/anitanowak.bsky.socialCONNECT WITH NIPUN✩ Website https://nipun.servicespace.org/✩ Company https://www.servicespace.org/SHOW NOTES✩ Inner Development Goals✩ TED TalkVideo edited by Green Horizon Studio

Is it time to rethink how restaurants are built—literally from the ground up?On this episode Kyle sits down with Nipun Sharma, CEO and co-founder of Appetronix, to talk about how robotics, AI, and first-principles thinking are completely transforming what a “restaurant” can be. With nearly two decades of global food experience and a sharp eye for operational pain points, Nipun is leading the charge with fully autonomous restaurant pods that slash labor, rent, and delivery inefficiencies—all while delivering chef-quality food.From launching in Columbus Airport with Donato's Pizza to raising funds in a post-hype market, Nipun shares how thinking like a restaurant operator—not a tech bro—is what sets Appetronix apart.

This episode is brought to you by HalloCasa, the SEO-ranked digital business card for real estate agents. Looking to find the right agent, no matter where you are?Visit https://home.hallocasa.com/ to discover and connect with top real estate agents globally.Explore and get started today: https://hallocasa.com/brokersIn Episode 154 of HalloCasa, I speak with Nipun, the founder of Happinest.ai, a groundbreaking proptech startup redefining property management. From seamless tenant communication and smart analytics to maximizing rental income and unlocking operational efficiencies, Nipun shares the journey of building Happinest.ai, the tech behind it, and the startup's go-to-market strategy. Learn how property owners and managers can leverage this AI-powered platform to outperform neighborhood benchmarks and scale their operations.00:00:48 Introduction00:02:00 About the Use Cases covered by happiness.ai00:06:50 Lead Qualification Process in Detail00:10:00 Communication between tenants and property managers via happinest.ai and Analytics Features00:10:00 Additional Use Cases from a property management´s point of view00:17:00 Happinest.ai as an orchestra00:24:00 Outperforming the local neighborhood market price through efficiencies with happinest.ai 00:29:40 Using Happinest.ai as an individual property owner and creating strong efficiencies00:35:00 The technology behind happinest.ai00:36:00 Nipun´s previous journey and his motivation to start happinest.ai00:41:20 Happinest.ai Pricing Model00:44:11 Next steps and raising money with Happinest.ai00:47:27 Conclusion and Final ThoughtsFeel free to reach out to Nipun via: https://www.linkedin.com/in/nipundubey/

Welcome Back to Pizza Quest!As you know, our usual focus is on the celebration of artisanship in pizza and anywhere else we find it. But what if the next generation of "artisan" pizza makers are robots? Or is this a non sequitur? Hey, before you shoot the messenger, listen to this revelatory conversation with Nipun Sharma, the CEO of Appetronix, who is about to launch the first fully robotic pizza kiosk in partnership with Donatos Pizza -- with more locations on their way. But how can this be? And how long before this technology scales up and shows up across the country? A lot of major implications here, so buckle your seat belts and join us as we explore a brave new world in this very unique episode of Pizza Quest.

Our feature guest this week is Nipun Mahajan, EVP at ISACA Denver. News from and a lot more! Support us on Patreon! Fun swag available - all proceeds will directly support the Colorado = Security infrastructure. Come join us on the new Colorado = Security Slack channel to meet old and new friends. Sign up for our mailing list on the main site to receive weekly updates - https://www.colorado-security.com/. If you have any questions or comments, or any organizations or events we should highlight, contact Alex and Robb at info@colorado-security.com This week's news: Join the Colorado = Security Slack channel Boulder, Colorado Named New Host of Sundance Film Festival Beginning in 2027 Popular grocery chain plans expansion into the Denver-metro area Denver sporting goods maker expands more than threefold Denver-based Angi Inc. completes spin-off, becomes independent Ball Corp. offloads product line to new joint venture Denver cryptocurrency company is being bought by a major industry player Five Critical Insights from the State of Trust Summit What does Google's $32B acquisition of cloud security startup Wiz mean for security operations? | Red Canary Upcoming Events: Check out the full calendar ISSA Denver - Insider Threats: A Hacker's Perspective - 4/9 CSA Colorado - Securing the Cloud - Attack Vectors - 4/15 Denver OWASP - The Attacker's Distributed Supercomputer: Your Browser - 4/16 ISACA Denver - Annual General Meeting - 4/17 Let's Talk Software Security - Can't We Just Automate Application Security? - 4/17 ISSA Pikes Peak - Chapter Meeting - 4/23 View our events page for a full list of upcoming events * Thanks to CJ Adams for our intro and exit! If you need any voiceover work, you can contact him here at carrrladams@gmail.com. Check out his other voice work here. * Intro and exit song: "The Language of Blame" by The Agrarians is licensed under CC BY 2.0

On this Screaming in the Cloud Replay, Corey is joined by Nipun Agarwal, Senior Vice President of MySQL HeatWave Development at Oracle, to discuss the release of MySQL HeatWave and how it will benefit users among the sea of database offerings on AWS. Nipun reveals why Oracle decided to develop HeatWave, how HeatWave is providing meaningful cost savings to users, and how HeatWave has been optimized for the cloud. Nipun explains how they've lowered the barriers to entry for new users of HeatWave, and Oracle's focus on implementing customer feedback when developing new offerings.Show Highlights(0:00) Intro(0:55) The Duckbill Group sponsor read(1:28) The significance of HeatWave coming to AWS(2:20) What is MySQL HeatWave?(5:13) What jumped out to Corey during his conversations with Nipun on Oracle(8:40) What's “under the hood” of MySQL HeatWave(14:12) How Oracle built out its pricing for MySQL HeatWave(16:41) Why MySQL HeatWave doesn't show up on AWS bills(21:27) The Duckbill Group sponsor read(22:09) Oracle's historical customer base and the company's credit system(24:30) The point behind MySQL HeatWave(27:51) How MySQL HeatWave runs(33:53) Where you can find more from Nipun and OracleAbout Nipun AgarwalNipun Agarwal is a Senior Vice President, MySQL HeatWave and Advanced Development, Oracle. His interests include distributed data processing, machine learning, cloud technologies and security. Nipun was part of the Oracle Database team where he introduced a number of new features. He has been awarded over 170 patents., Nipun Agarwal is Senior Vice President of MySQL Database & HeatWave Development. He leads a global engineering organization responsible for Oracle's MySQL innovations that enable organizations to use a single database for both transactional and analytical workloads. His interests include data processing, distributed systems, machine learning, cloud computing and security. Prior to his current position, Nipun was with Oracle Labs and the Oracle Database team, where he introduced a number of new features. He has been awarded over 175 patents.LinksOracle: https://oracle.comMySQL HeatWave info: https://www.oracle.com/mysql/ MySQL Service on AWS and OCI login (Oracle account required): https://cloud.mysql.comOriginal Episodehttps://www.lastweekinaws.com/podcast/screaming-in-the-cloud/heatwave-and-the-latest-evolution-of-mysql-with-nipun-agarwal/SponsorThe Duckbill Group: duckbillgroup.com

In this episode, Nipun Kathuria, co-founder and CEO of Smile Genius Dental, shares his journey from India to Ireland, discussing the importance of a positive mindset, cultural transitions, and his unexpected path into the world of dentistry. He chats about personal growth, the challenges of adapting to new environments, and the intricacies of the dental industry. He discusses the technological advancements in dentistry, highlighting the lag in software innovation compared to other industries. Finally, Nipun shares insights on entrepreneurship, personal growth, and the challenges faced in the dental tech market. Topics: - Was there a time you can look back on your childhood and say this is why I am the person I am today? - Tell us about your move from Ireland to do an MBA at Trinity College. - How did you find this transition – from leaving family, a new continent, different culture? - What sort of work experience did you gain in the early days? - How did you get into dentistry? - When did you start looking at workflows for clear aligners? - Do the patient, the practice and the lab need to be aligned for progress to be made? Is there a weak link? - Who do you see at the forefront of this market? - Align is clearly a dominant player in this market but could this change over time with tech, workflows, cost to deliver, etc shifting over time? - Are labs behind the game in marketing themselves and their services? - If you can take only one learning from your entrepreneurial journey - what is it?

We are welcoming Nipun Mehta, founder of ServiceSpace, a global movement that touches millions of people through the merging of volunteerism, technology and the gift-economy.Tamsin spoke to Nipun about the potential and far-reaching impacts of an unexpected act of kindness. Not only for the recipient, but for oneself, society and the world at large. Nipun set up ServiceSpace after quitting his first and only job as a software engineer to become a full-time volunteer. Fast forward more than two decades and ServiceSpace has evolved to become a global ecosystem of over 1.5 million members, delivering millions of dollars in service for free. He has also been honoured by the Dalai Lama as an "Unsung Hero of Compassion".Our podcast is hosted and produced by Tamsin Walker. Executive producer is IGD co-founder Jeroen Janss. For more information, visit us on LinkedIn, innergreendeal.com or write to info@innergreendeal.com.   In the four years since it has been running, the Inner Green Deal podcast has been entirely self-funded and we are committed to keeping it that way, which means commercials-free. To live up to this ambition, we are inviting you to support us. Every contribution, however small, makes a difference and allows us to continue sharing inspiring stories that highlight how understanding what is going inside can help in tackling the climate crisis. If you would like to donate, click here for more details.Hosted by Ausha. See ausha.co/privacy-policy for more information.

”We need to move from transaction to relationship.” Nipun Mehta brings us on a transcendental journey to find our compassionate selves. Through the transforming story of his walking pilgrimage across India, Nipun kicks off by sharing his three key values: success, service and stillness. Further life snippets trigger us to ask ourselves fundamental questions such as “Where did you learn to be good?” or “Who must we be to walk towards futures we cannot imagine?” For one thing is certain, Nipun loves life and the humans that constitute it. He generously shares with the audience the guiding statements shaping his daily life, work and service, as they are all intertwined. By taking inspiration from figures of compassion and wisdom such as Mother Teresa, Gandhi or Desmond Tutu, he insists that creating a “we-to-we” community centred around our relationship to the other rather than the value involved in the transaction process will make us all more complete humans. As he concludes, “we are not merely what we do but we become who we are by what we do”. A true lesson of community, service and humility to help us navigate the unknown of tomorrow.

ENVISION radical generosity with Nupin Mehta.Nipun Mehta is the founder of ServiceSpace, a global community working at the intersection of technology, volunteerism, and gift culture.As a designer of large-scale social movements that are rooted in small acts of service and powered by micro-moments of inner transformation, his work has uniquely catalyzed "many to many" networks of community builders grounded in their localities and rooted in practices of cultivating compassion. More recently, ServiceSpace's pandemic response showcased the beauty of its agile ecosystem.Today, ServiceSpace reaches millions every month, is powered by thousands of volunteers, and blossoms into ever-expanding local and virtual service projects that aim to ignite a "whole greater than the sum of its parts".Nipun was honored as an "Unsung hero of compassion" by the Dalai Lama, not long before former U.S. President Obama appointed him to a council for addressing poverty and inequality in the USA.Yet the core of what strikes anyone who meets him is the way -his life is an attempt to bring smiles in the world and silence in his heart. I quote him: "I want to live simply, love purely, and give fearlessly. That's me.”Welcome NIPUN, is an honor to share this moment, here with you!About Nipun    |     ServiceSpace I invite you to join my email list, if you want to hear about the new episodes or the food for thought I am pondering on. https://www.auroramorfin.com/ Aligned Beings our online community has opened its doors. If you want to hear more about it and all the details, visit the site. All the info is there! Also, I'm launching a new chapter of the New Beginning Workshop, all the details are out there on the site as well. Much love gorgeous Human Being! ❤️

Folge 5. Nipun Mehta ist einer der Stars in diesem Forumsjahr. Thomas Seifert hat den ehemaligen Obama-Berater und Wirtschaftsvisionär aus dem Silicon Valley getroffen. Und Anna Wallner besucht das Dorffest, das die Erste Stiftung Samstagabend geschmissen hat - mit Butter, Honig und einem Konzert der Musikerin Alicia Edelweiss.

Nipun Mehta is the founder of ServiceSpace, a global community working at the intersection of technology, volunteerism and a gift culture. As a designer of large-scale social movements that are rooted in small acts of service and powered by micro moments of inner transformation, his work has uniquely catalyzed "many to many" networks of community builders grounded in their localities and rooted in practices of cultivating deeper connection -- with oneself, each other and our systems. Today, ServiceSpace reaches millions every month, is powered by thousands of volunteers, and blossoms into ever-expanding local and virtual service projects that aim to ignite a "whole great than the sum of its parts". Nipun was honored as an "unsung hero of compassion" by the Dalai Lama, not long before former U.S. President Obama appointed him to a council for addressing poverty and inequality in the US. Yet the core of what strikes anyone who meets him is the way his life is an attempt to bring smiles in the world and silence in his heart: "I want to live simply, love purely, and give fearlessly. That's me."See omnystudio.com/listener for privacy information.

Using modern tools to support inner transformation, ServiceSpace founder Nipun Mehta offers innovative solutions for turning artificial intelligence into collective heart intelligence.Learn more about ServiceSpace's unique model of organizing small acts of service at servicespace.org.In this episode, Nipun and Raghu chat about: Nipun's upbringing and finding the infinity behind each momentLiving a life of serviceUsing artificial intelligence for inner transformation and the emergence of compassionFear of AI versus it's potential positive usesCollective heart Intelligence versus today's artificial intelligenceTaking care of others as others take care of youNipun and his wife's pilgrimage through IndiaLooking at what we can do to offer kindness to the worldBeing sustainable through being relatedThe physical and emotional rewards of being generousShifting from transaction into relationshipAbout Nipun Mehta:Nipun Mehta is the founder of ServiceSpace (formerly CharityFocus), an incubator of projects that works at the intersection of volunteerism, technology, and the gift economy. What started as an experiment with four friends in Silicon Valley has now grown to a global ecosystem of over 400,000 members that has delivered millions of dollars in service for free. Mehta has received many awards, including the Jefferson Award for Public Service, the President's Volunteer Service Award, and Wavy Gravy's Humanitarian award. He serves on the advisory boards of the Seva Foundation, the Dalai Lama Foundation, and the Greater Good Science Center. Check out some of Nipun's TedTalks HERE and HERE.“Can we bring in this vision, this intention, this possibility? Can our modern tools support our inner transformation, which then can out of a heart of service flow out into the world through a very different design pattern?” – Nipun MehtaSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

In this episode of Eyeway Conversations, host George Abraham sits down with Nipun Malhotra, founder of the Nipman Foundation, to discuss the challenges faced by people with disabilities and the fight for a more inclusive society. Despite being restricted to a wheelchair, Nipun is one of the strongest advocates for disability rights in India. Through this candid conversation, he shares his personal journey and the inspiration behind founding the Nipman Foundation. We delve into the foundation's work on changing attitudes towards disability through sensitization workshops, accessibility audits, and the Equal Opportunity Awards. A major focus of the episode is Nipun's recent legal battle against Sony Pictures for the derogatory portrayal of disabilities in the film "Aankh Micholi." We explore the details of the case, the Supreme Court's landmark ruling, and its implications for the representation of people with disabilities in media. Nipun also shares his insights on the challenges faced by the disability community, including the importance of accurate representation, dispelling stereotypes, and creating a society where everyone has equal opportunities. Key topics covered: The experiences of people with disabilities in India The role of media in shaping perceptions The impact of the Supreme Court's ruling on disability representation Advocacy and activism for disability rights This episode provides a powerful and informative discussion on disability rights and the ongoing struggle for a more inclusive world.

On this episode of the CFA Society San Francisco Podcast, we had the pleasure of speaking with Pooja Malik, CFA, Founding Partner and Managing Member at Nipun Capital. Nipun Capital is a specialized asset management firm that focuses on alpha extraction from Asia and emerging markets.Pooja founded Nipun based on the outlook that Asia ex-Japan equity markets would double in size from 2010 to 2030 as a portion of global market cap. She is a strong advocate for sustainability and impact investing which she integrates into Nipun's investment process with the goal of outperforming benchmarks and delivering above average market returns. She has over 20 years of asset management experience, with a focus on portfolio management and research.Prior to Nipun, Pooja was a Managing Director at Barclays Global Investors (BGI)/BlackRock in the Active/Scientific Equities group, where she led teams that managed various long-only and long-short portfolios in excess of $100 billion for institutional investors. Pooja graduated from Delhi University and received an MBA from Indian Institute of Management, Bangalore. She holds the Chartered Financial Analyst designation and has earned the CFA Institute Certificate in ESG Investing.Listen to the full interview, where Pooja discusses emerging markets.This podcast is produced by CFA Society San Francisco, a not-for-profit professional association, providing professional learning and career resources to over 13,000 investment industry professionals worldwide. To learn more about CFA Society San Francisco, visit our website or connect with us on LinkedIn.The information contained in this podcast does not constitute financial or investment advice. Please consult your own financial advisor for information concerning your specific situation.

“Wong-wong sing ora ngalahake perkara-perkara cilik, bakal ora nduweni kuwasa moral kanggo nglawan panggodha sing luwih gedhe” - ”Gusti Allah nyatakake salah sawijining wewadi-niPun marang ratu kang nyembah brahala ing zaman kuno“

“Awak kita dibangun saka panganan sing kita pangan” - “Pracayaa marang kang Gusti Allah dhawuhake; ugemana prasetya-Nipun ing atimu”

Right now, says Nipun Mehta, founder of Service Space, an incubator of gift economy projects that inspire people to be the change they wish to see, the world needs a little more kindness. And yes, with so many challenges happening globally, it might feel like such an insignificant act isn't going to affect anything but says Nipun, that's how history changes. 25 years ago, in Silicon Valley, Nipun started Service Space as an experiment with friends. Today it's a global ecosystem with around 1.5 million members. And they've not only delivered millions of dollars in service for free, but they're also regenerating a gift culture. In this incredibly insightful conversation, Vesna and Nipun discuss how small acts of kindness can change the world. To find out more, download and listen to this episode. On today's podcast:What we can learn from the gratitude economyThe future potential of AIAligning AI with heart intelligenceThe 1,000 km journey to himselfThe long term solution for businessLinks:https://www.servicespace.org/ Hosted on Acast. See acast.com/privacy for more information.

“Wong-wong sing menang kayadene Kristus kang wis menang perlu tansah njaga diri kanggo nglawan panggodhane Setan” - ”Pikajenge Gusti Yesus yakuwi supaya kita nggawa para kanca kita kang ringkih marak ing ngarsa-Nipun.“

In this Ortho Marketing Podcast, Dean Steinman is joined by Nipun Kathuria, CEO and Co-Founder of Smile Genius Dental. They discuss digital tools that can help you launch and manage your clear aligner businesses easily.Ready to elevate your practice? Contact us!https://orthomarketing.com/contact-us/About Nipun KathuriaNipun Kathuria is the CEO and Co-Founder of Smile Genius Dental. Smile Genius is a startup based in Dublin, Ireland which is also backed by the the government entity, Enterprise Ireland. Smile Genius launched world's first all-in-one clear aligner platfom that connects doctors, manufacturing labs and patient with its remote monitoring app. Nipun has been pivotal in the company's recognition and success to date globally. Smile Genius works with clinics, DSOs and labs in Europe, UK, US and Middle East. Nipun is on a mission to help build Smile Genius as the go to single platform for all things orthodontics and dentistry. Nipun's prior experience has been in Businesses and Marketing where he led digital transformations for various retails brands in India and Ireland. Nipun graduated as a software engineer in India prior to doign is MBA from Trinity College Dublin.

In this Ortho Marketing Podcast, Dean Steinman is joined by Nipun Kathuria, CEO and Co-Founder of Smile Genius Dental. They discuss digital tools that can help you launch and manage your clear aligner businesses easily.Ready to elevate your practice? Contact us!https://orthomarketing.com/contact-us/About Nipun KathuriaNipun Kathuria is the CEO and Co-Founder of Smile Genius Dental. Smile Genius is a startup based in Dublin, Ireland which is also backed by the the government entity, Enterprise Ireland. Smile Genius launched world's first all-in-one clear aligner platfom that connects doctors, manufacturing labs and patient with its remote monitoring app. Nipun has been pivotal in the company's recognition and success to date globally. Smile Genius works with clinics, DSOs and labs in Europe, UK, US and Middle East. Nipun is on a mission to help build Smile Genius as the go to single platform for all things orthodontics and dentistry. Nipun's prior experience has been in Businesses and Marketing where he led digital transformations for various retails brands in India and Ireland. Nipun graduated as a software engineer in India prior to doign is MBA from Trinity College Dublin.

“Angger-anggering Gusti Allah katulis kanthi asta-Nipun ing saben saraf, saben otot, saben panca indera kang wis kapercayaaké marang manungsa.” - “Tugas kita yakuwi kangge ngundang sak-akehe wong kangge milih Sang Kristus”

“Allah ora diluhurake menawa badan dilirwaake utawa disalahgunaake lan kanthi mangkono ora pantes kanggo peladosan-Nipun.” - “Ing sauruting sejarah, Sang Yehuwah Allah tansah nduweni umat kang setya nulada karakter-Ipun lan tansah mituhu”

“Neuroprotectors minangka zat antioksidan sing nglindhungi otak lan kabeh sistem saraf saka karusakan lan kondisi aus.” - “Pitadosa dumateng pamgandikanipun Gusti Allah; tampinen prasetya-prasetya-Nipun lumebet panggalih panjenengan”

“Neuroprotectors minangka zat antioksidan sing nglindhungi otak lan kabeh sistem saraf saka karusakan lan kondisi aus.” - “Pitadosa dumateng pangandikanipun Gusti Allah; tampinen prasetya-prasetya-Nipun lumebet panggalih panjenengan”

DSO Overflow S3EP8Static Application Security TestingwithNipun GuptaIn this episode, Glenn is joined by Nipun Gupta, a seasoned technology executive, entrepreneur, and speaker to talk about static code analysis, its benefits, its pitfalls and how best to integrate tools into developer workflows.  Based nowadays in London, UK after a decade in Silicon Valley, Nipun has developed a reputation as a thought leader and innovator in cybersecurity at places like NCC Group, Deutsche Bank, and Deloitte. Prior to leading Integrations Product at Devo, he served as the Vice President, Global Cyber Security Strategy & Innovation Lead at Deutsche Bank's Silicon Valley office. Currently serving as the COO at Bearer, a fast-growing static code analysis platform that is redefining what code security can do, Nipun is at the forefront of the DevSecOps revolution, helping companies of all sizes adopt modern approaches to software development and security.Resources mentioned in this podcast:Nipun's LinkedIn profileNipun's Twitter FeedBearer CLI documentationBearer on GitHubBearer on TwitterDSO Overflow is a DevSecOps London Gathering production. Find the audio version on all good podcast sources like Spotify, Apple Podcast and Buzzsprout.This podcast is brought to you by our sponsors:  Prisma Cloud,, Apiiro, and SysdigYour HostsSteve Giguere linkedin.com/in/stevegiguereGlenn Wilson linkedin.com/in/glennwilsonJessica Cregg linkedin.com/in/jessicacreggDevSecOps - London GatheringKeep in touch with our events associated with this podcast via our website.For more about DevSecOps - London Gathering check out https://dsolg.com

feedback @ ryan@soulsearching.in EPISODE LINKS: Nipun's Linkedin : https://www.linkedin.com/in/nipun-gupta-b900574b/ Twitter : https://twitter.com/nipun4189 PODCAST INFO: Podcast website: https://anchor.fm/ryandsouza Apple Podcasts: https://apple.co/3NQhg6S Spotify: https://spoti.fi/3qJ3tWJ Amazon Music: https://amzn.to/3P66j2B Google Podcasts: https://bit.ly/3am7rQc Gaana: https://bit.ly/3ANS4v1 RSS: https://anchor.fm/s/609210d4/podcast/rss --- Send in a voice message: https://podcasters.spotify.com/pod/show/ryandsouza/message

Opposition BNP in poll-bound Bangladesh is seen as anti-India and anti-Hindu. Its top Hindu faces, Nitai Roy Chowdhury and his daughter Nipun, are trying to counter this perception.----more----Read full article here: https://theprint.in/world/will-uphold-secular-values-hindu-leaders-seek-to-shed-bangladesh-national-partys-anti-hindu-tag/1685643/

Turns out, we can have many kinds of wealth besides money: creativity, time, community, compassion, friendships, attention, and patience, to name a few. We can each give those things to others liberally, and in the process, live extraordinarily happy lives. Today's guest, Nipun Mehta, will help you see that in a world where “capital” like time, ideas, and kindness are priceless, what you have to contribute makes you very wealthy. 00:00 Preview 00:40 Intro & Welcome 03:34 The Power of Volunteering Nipun may have started reversing the hopelessness narrative long before it was popular. Nipun has always felt that there's a spark in people that longs to be in service and longs to be compassionate. He has an implicit faith in himself and everyone else. In the late 90's Nipun started a project called ‘DailyGood' which started with an automatic email sent out every morning with good news. This has been done every day since 1996. It started with his yearning to empower the impulse to serve. The belief is that the world is held together with a lot of goodness and a lot of care. The biggest leaps in human history started with quiet givers and people who turned their backs on something that offended them at the core of their humanity. Ghandi for instance, started his movement based on him being thrown off a train in South Africa for being brown. He was able to do this without burning bridges or creating enemies. Martin Luther King Jr., Ghandi, Mandela, The Dalai Lama all took the stance that they would not create an enemy while resisting an action. They would resist an action without creating an enemy. They could resist an action but love the person. The best ideas don't need an enemy. 11:00 Reserving Our Clicks for Things That Matter Wealth currently has a narrow definition based on things like money, power and outward appearance. This has led us to want more and more, and it is this wanting more that typically creates separation & inequality. How do we start to play a much bigger game? We can start by accepting that different forms of wealth exist such as: Stories Attention Connection So much is done to circulate money and the ideas of fame and power as measures of wealth. We can also do the same with our time capital. Small actions might change the entire world and are just as meaningful as newsworthy or Nobel Prize worthy acts. Maybe it's the small things that matter the most. In the words of Mother Teresa, “You can do no big things, only small things with great love”. Those who tend to the small acts tend to be happier and more connected, secure and grounded. Nipun's very successful found out his first son was autistic.. He was initially worried, but soon recognized that this might be the biggest gift of his life as it showed him that everyone is good at something. He went on to hire several people on the autism spectrum, and the initiative was so successful that it became a Harvard Case Study. Last week's episode, (Episode 137) with Temple Grandin, the most famous autistic person in the world spoke to the limitlessness and beauty of different minds. 46:12 Break 18:50 Hunger is Invisible Nipun's Organization, ServiceSpace, started by building websites for non-profit organizations. It started when Nipun and his 3 friends went to a homeless shelter in 1999 and offered to build them a website in their earliest effort to practice generosity. They intuitively knew that they could exercise compassion & kindness and grow them as one would grow muscles. Giving is beneficial to both the giver and the receiver. They started spreading the word on how small acts of kindness can improve everyone's lives. These acts garnered media coverage as website building was expensive at the time, and here were some young men who could be making money building websites for free. The reward comes from nature. The idea of the movement is to hold space to allow people to be able to give of themselves in return for nature's reward...

Harrison and our new interns, Nipun and Turner, discuss earnings data from CSCO and WMT, the ban of TikTok in Montana, and spending data showing that the consumer is becoming more judicious.For information on how to join the Zoom calls live each morning at 8:30 EST, visit https://www.narwhalcapital.com/blog/daily-market-briefingsPlease see disclosures:https://www.narwhalcapital.com/disclosure

#ula #ecommerce #Internet #Indonesia Ula's Nipun Mehra: Conquering Indonesia's Vast and Fast-Growing E-Commerce Market  Nipun Mehra, the Founder and CEO of Indonesia-based e-commerce firm Ula, came to entrepreneurship late in life, having first worked at Sequoia Capital, Flipkart, Pine Labs, Amazon and Boston Consulting.  The delay didn't hurt though, with Ula now counting Jeff Bezos, Prosus Ventures, Tencent and B-Capital Group among its investors, hoping to capture a portion of the $300B+ retail market in the region. This is his story and life- and business lessons.  (This interview was part of a collaboration with CGS-CIMB and Endeavor Malaysia as part of the 'Thought Inspire' Series, filmed at the Asia School of Business, a partnership between MIT Sloan School of Management and Bank Negara Malaysia.)  ---  CONTENTS  00:00:00 - Intro 00:00:53 - Which Came First: Employment or Entrepreneurship?  00:03:22 - Get a Job First?  00:05:05 - When Was the Plunge Taken?  00:06:11 - Which Skills Were Most Valuable?  00:07:15 - What Do Blue-Chip Investors Like Sequioa Seek in Entrepreneurs?  00:12:49 - Does Academic Excellence Matter?  00:15:31 - Should Entrepreneurs Expand to Indonesia, ASEAN's Biggest Market?  00:18:24 - In New World Order, Should Entrepreneurs Pivot to Profit Instead?  00:22:08 - How To Choose A Market to Operate In?  00:28:46 - In Tech, Layoffs & Cost Cuts. Discuss.  00:31:19 - Have Valuations Suffered in the Current Market Conditions?  00:34:48 - Managing Investors When Valuations Fall  00:38:27 - Where to List? Asia or US?  00:42:36 - Why Did Jeff Bezos Invest in Ula (And In His Personal Capacity)  00:45:31 - Nipun's 60-Second Pitch to Amazon's Jeff Bezos  00:46:20 - What Does it Take to Succeed in Indonesia?  00:48:18 - How to Scale In Indonesia  00:49:26 - How to Develop Expectations Jointly With Investors  00:52:40 - What Are Tencent's Expectations?  FOLLOW NIPUN HERE:  LinkedIn: https://t.co/8lI1IVZcuf  Twitter: @nipunmehra  Endeavor: https://endeavorindonesia.org/nipun-mehra/  --- Follow Chuang here: URL: http://www.domore.my/ LinkedIn: https://www.linkedin.com/in/hsu-chuang-khoo-ab199343/ FB: https://www.facebook.com/khoo.chuang/ IG: https://www.instagram.com/khoohsuchuang .. Follow DoMore here: WEBSITE: https://www.domore.my/ YOUTUBE: https://www.youtube.com/c/DoMoreTakeChargeofYourLife ITUNES: https://apple.co/2lQ47mS GOOGLE PLAY: https://bit.ly/3b1l8iO SPOTIFY: https://tinyurl.com/y6zufvcp PODBEAN: https://domoreasia.podbean.com/ INSTAGRAM: https://www.instagram.com/domore.asia/

Nipun Mehta, founder of ServiceSpace, joins host Martin Schreiber to discuss the importance of gratitude, empathy and small acts of kindness.

In part two of our conversation, host Martin Schreiber explores the art of pilgrimage with Nipun Mehta.

This week Allan is joined by Nipun Gupta, and industry veteran who has been a consultant, practitioner, vendor, advisor and investor. The topic is "What are we really protecting in cyber?" and the nuances of that question are explored in depth - as well as the interrelationships. Is "protect the business" a guardrail statement while "protect data and people" is the mission? How do we tie protecting people to protecting the business?  For the people?  For the business? How do we map data to the business mission? How far do we go to protect data? What about this new DevOps, application-centric world? Enjoy this conversation!  It's a lively one.

Money cannot buy you happiness. We have all heard this famous quote, but is this the right way of viewing life? The truth is, you need wealth to be happy, but not the kind of wealth you are probably thinking about. For Nipun Mehta, simple acts of kindness, compassion, and giving are forms of wealth that are oftentimes more treasured than tangible money. He is the founder of ServiceSpace, a series of volunteers that center around the gift-economy, and has won multiple awards for his passion in helping others. Follow our Instagram and YouTube @moneymadeeasypod --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app

We met with Nipun Mehta, the founder of ServiceSpace, to discuss gratitude and generosity. Revealing the how and why of, "giving like a rose that gives away its scent," we were ourselves transformed by the conversation. As a small sampling of the conversation's many gems, we touched on the hierarchy of generosity, and the ability to "throw a better party" when we replace transactions with relationships. Nipun advocated for our own personal experimentation with generosity, knowing that if we listen closely, we may discover wonderful changes happening within ourselves. He explained how gratitude can be regenerative, and reminded us that it emerges from the recognition that we are nestled in so many gifts that we can never reciprocate. This knowledge invites us to pay forward what we can never pay back. Apparently the most valuable resource in navigating this path is to have noble friends who help us find the way through these and many other inspiring insights. We invite you to be our noble friends, and join us on this transformative journey through Thanksgiving and beyond.

MySQL is the most popular open source database in the world. Oracle's new MySQL Heatwave makes MySQL the only cloud service with a built-in, high performance, in-memory query accelerator—HeatWave. In this episode, hosts Matt Kimball and Steve McDowell, principal analysts at Moor Insights & Strategy, catch up with Oracle's Nipun Agarwal, Oracle's SVP of MySQL and Heatwave, at the recent Oracle OpenWorld event to about what it all means. This is wide-ranging conversation about the history of MySQL, where it plays well, and how Oracle MySQL HeatWave brings added value to the MySQL ecosystem. Special Guest: Nipun Agarwal.

For a podcast that usually talks about money and how to grow our wealth, it's important to take a step back to understand why we want to do this in the first place: we want to be happy. For Nipun Mehta, the founder of ServiceSpace, simple acts of kindness, compassion, and giving are forms of wealth that are oftentimes more treasured than tangible money. In this interview, he talks about how giving and taking part in making others happy will in turn make you feel even better about yourself. Follow our Instagram and YouTube @moneymadeeasypod pravarjain34@gmail.com arnavjain123aj@gmail.com --- This episode is sponsored by · Anchor: The easiest way to make a podcast. https://anchor.fm/app

About NipunNipun Agarwal is a Senior Vice President, MySQL HeatWave Development, Oracle. His interests include distributed data processing, machine learning, cloud technologies and security. Nipun was part of the Oracle Database team where he introduced a number of new features. He has been awarded over 170 patents.Links Referenced: Oracle: https://oracle.com MySQL HeatWave info: https://www.oracle.com/mysql/ MySQL Service on AWS and OCI login (Oracle account required): https://cloud.mysql.com TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is brought to us in part by our friends at Datadog. Datadog's SaaS monitoring and security platform that enables full stack observability for developers, IT operations, security, and business teams in the cloud age. Datadog's platform, along with 500 plus vendor integrations, allows you to correlate metrics, traces, logs, and security signals across your applications, infrastructure, and third party services in a single pane of glass.Combine these with drag and drop dashboards and machine learning based alerts to help teams troubleshoot and collaborate more effectively, prevent downtime, and enhance performance and reliability. Try Datadog in your environment today with a free 14 day trial and get a complimentary T-shirt when you install the agent.To learn more, visit datadoghq.com/screaminginthecloud to get. That's www.datadoghq.com/screaminginthecloudCorey: This episode is sponsored in part by our friends at Sysdig. Sysdig secures your cloud from source to run. They believe, as do I, that DevOps and security are inextricably linked. If you wanna learn more about how they view this, check out their blog, it's definitely worth the read. To learn more about how they are absolutely getting it right from where I sit, visit Sysdig.com and tell them that I sent you. That's S Y S D I G.com. And my thanks to them for their continued support of this ridiculous nonsense.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. This promoted episode is sponsored by our friends at Oracle, and back for a borderline historic third round going out and telling stories about these things, we have Nipun Agarwal, who is, as opposed to his first appearance on the show, has been promoted to senior vice president of MySQL HeatWave. Nipun, thank you for coming back. Most people are not enamored enough with me to subject themselves to my slings and arrows a second time, let alone a third. So first, thanks. And are you okay, over there?Nipun: Thank you, Corey. Yeah, very happy to be back.Corey: [laugh]. So, since the last time we've spoken, there have been some interesting developments that have happened. It was pre-announced by Larry Ellison on a keynote stage or an earnings call, I don't recall the exact format, that HeatWave was going to be coming to AWS. Now, you've conducted a formal announcement, this usual media press blitz, et cetera, talking about it with an eye toward general availability later this year, if I'm not mistaken, and things seem to be—if you'll forgive the term—heating up a bit.Nipun: That is correct. So, as you know, we have had MySQL HeatWave on OCI for just about two years now. Very good reception, a lot of people who are using MySQL HeatWave, are migrating from other clouds, specifically from AWS, and now we have announced availability of MySQL HeatWave on AWS.Corey: So, for those who have not done the requisite homework of listening to the entire back catalog of nearly 400 episodes of this show, what exactly is MySQL HeatWave, just so we make sure that we set the stage for what we're going to be talking about? Because I sort of get the sense that without a baseline working knowledge of what that is, none of the rest of this is going to make a whole lot of sense.Nipun: MySQL HeatWave is a managed MySQL service provided by Oracle. But it is different from other MySQL-based services in the sense that we have significantly enhanced the service such that it can very efficiently process transactions, analytics, and in-database machine learning. So, what customers get with the service, with MySQL HeatWave, is a single MySQL database which can process OLTP, transaction processing, real-time analytics, and machine learning. And they can do this without having to move the data out of MySQL into some other specialized database services who are running analytics or machine learning. And all existing tools and applications which work with MySQL work as is because this is something that enhances the server. In addition to that, it provides very good performance and very good price performance compared to other similar services out there.Corey: The idea historically that some folks were pushing around the idea of multi-cloud was that you would have workloads that—oh, they live in one cloud, but the database was going to be all the way across the other side of the internet, living in a different provider. And in practice, what we generally tend to see is that where the data lives is where the compute winds up living. By and large, it's easier to bring the compute resources to the data than it is to move the data to the compute, just because data egress in most of the cloud providers—notably exempting yours—is astronomically expensive. You are, if I recall correctly, less than 10% of AWS's data egress charge on just retail pricing alone, which is wild to me. So first, thank you for keeping that up and not raising prices because I would have felt rather annoyed if I'd been saying such good things. And it was, haha, it was a bait and switch. It was not. I'm still a big fan. So, thank you for that, first and foremost.Nipun: Certainly. And what you described is absolutely correct that while we have a lot of customers migrating from AWS to use MySQL HeatWave and OCI, a class of customers are unable to, and the number one reason they're unable to is that AWS charges these customers all very high egress fees to move the data out of AWS into OCI for them to benefit from MySQL HeatWave. And this has definitely been one of the key incentives for us, the key motivation for us, to offer MySQL HeatWave on AWS so that customers don't need to pay this exorbitant data egress fees.Corey: I think it's fair to disclose that I periodically advise a variety of different cloud companies from a perspective of voice-of-the-customer feedback, which essentially distills down to me asking really annoying slash obnoxious questions that I, as a customer, legitimately want to know, but people always frown at me when I asked that in vendor pitches. For some reason, when I'm doing this on an advisory basis, people instead nod thoughtfully and take notes, so that at least feels better from my perspective. Oracle Cloud has been one of those, and I've been kicking the tires on the AWS offering that you folks have built out for a bit of time now. I have to say, it is legitimate. I was able to run a significant series of tests on this, and what I found going through that process was interesting on a bunch of different levels.I'm wondering if it's okay with you, if we go through a few of them, just things that jumped out to me as we went through a series of conversations around, “So, we're going to run a service on AWS.” And my initial answer was, “Is this Oracle? Are you sure?” And here we are today; we are talking about it and press releases.Nipun: Yes, certainly fine with me. Please go ahead.Corey: So, I think one of the first questions I had when you said, “We're going to run a database service on AWS itself,” was, if I'm true to type, is going to be fairly sarcastic, which is, “Oh, thank God. Finally, a way to run a MySQL database on AWS. There's never been one of those before.” Unless you count EC2 or Aurora or Redshift depending upon how you squint at it, or a variety of other increasingly strange things. It feels like that has been a largely saturated market in many respects.I generally don't tend to advise on things that I find patently ridiculous, and your answer was great, but I don't want to put words in your mouth. What was it that you saw that made you say, “Ah, we're going to put a different database offering on AWS, and no, it's not a terrible decision.”Nipun: Got it. Okay, so if you look at it, the value proposition which MySQL HeatWave offers is that customers of MySQL or customers have MySQL compatible databases, whether Aurora, or whether it's RDS MySQL, right, or even, like, you know, customers of Redshift, they have been migrating to MySQL HeatWave on OCI. Like, for the reasons I said: it's a single database, customers don't need to have multiple databases for managing different kinds of workloads, it's much faster, it's a lot less expensive, right? So, there are a lot of value propositions. So, what we found is that if you were to offer MySQL HeatWave on AWS, it will significantly ease the migration of other customers who might be otherwise thinking that it will be difficult for them to migrate, perhaps because of the high egress cost of AWS, or because of the high latency some of the applications in the AWS incur when the database is running somewhere else.Or, if they really have an ecosystem of applications already running on AWS and they just want to replace the database, it'll be much easier for them if MySQL HeatWave was offered on AWS. Those are the reasons why we feel it's a compelling proposition, that if existing customers of AWS are willing to migrate the cloud from AWS to OCI and use MySQL HeatWave, there is clearly a value proposition we are offering. And if we can now offer the same service in AWS, it will hopefully increase the number of customers who can benefit from MySQL HeatWave.Corey: One of the next questions I had going in was, “Okay, so what actually is this under the hood?” Is this you effectively just stuffing some software into a machine image or an AMI—or however they want to mispronounce that word over an AWS-land—and then just making it available to your account and running that, where's the magic or mystery behind this? Like, it feels like the next more modern cloud approach is to stuff the whole thing into a Docker container. But that's not what you wound up doing.Nipun: Correct. So, HeatWave has been designed and architected for scale-out processing, and it's been optimized for the cloud. So, when we decided to offer MySQL HeatWave on AWS, we have actually gone ahead and optimize our server for the AWS architecture. So, the processor we are running on, right, we have optimized our software for that instance types in AWS, right? So, the data plane has been optimized for AWS architecture.The second thing is we have a brand new control plane layer, right? So, it's not the case that we're just taking what we had in OCI and running it on AWS. We have optimized the data plane for AWS, we have a native control plane, which is running on AWS, which is using the respective services on AWS. And third, we have a brand new console which we are offering, which is a very interactive console where customers can run queries from the console. They can do data management from the console, they're able to use Autopilot from the console, and we have performance monitoring from the console, right? So, data plane, control plane, console. They're all running natively in AWS. And this provides for a very seamless integration or seamless experience for the AWS customers.Corey: I think it's also a reality, however much we may want to pretend otherwise, that if there is an opportunity to run something in a different cloud provider that is better than where you're currently running it now, by and large, customers aren't going to do it because it needs to not just be better, but so astronomically better in ways that are foundational to a company's business model in order to justify the tremendous expense of a cloud migration, not just in real, out of pocket, cost in dollars and cents that are easy to measure, but also in terms of engineering effort, in terms of opportunity cost—because while you're doing that you're not doing other things instead—and, on some level, people tend to only do that when there's an overwhelming strategic reason to do it. When folks already have existing workloads on AWS, as many of them do, it stands to reason that they are not going to want to completely deviate from that strategy just because something else offers a better database experience any number of axes. So, meeting customers where they are is one of the, I guess, foundational shifts that we've really seen from the entire IT industry over the last 40 years, rather than you will buy it from us and you will tolerate it. It's, now customers have choice, and meeting them where they are and being much more, I guess, able to impedance-match with them has been critical. And I'm really optimistic about what the launch of this service portends for Oracle.Nipun: Indeed, but let me give you another data point. We find a very large number of Aurora customers migrating to MySQL HeatWave on OCI, right? And this is the same workload they were running on Aurora, but now they want to run the same workload on MySQL HeatWave on OCI. They are willing to undertake this journey of migration because their applications, they get much faster, and for a lot less price, but they get much faster. Then the second aspect is, there's another class of customers who are for instance running, on Aurora or other transactions or workloads, but then they have to keep moving the data, they'll keep performing the ETL process into some other service, whether it's Snowflake, or whether it's Redshift for analytics.Now, with this migration, when they move to MySQL HeatWave, customers don't need to, like, have multiple databases, and they get real-time analytics, meaning that if any data changes inside the server inside the OLTP as a database service, right? If they were to run a query, that query is giving them the latest results, right? It's not stale. Whereas with an ETL process, it gets to be stale. So, given that we already found that there were so many customers migrating to OCI to use MySQL HeatWave, I think there's a clear value proposition of MySQL HeatWave, and there's a lot of demand.But like, as I was mentioning earlier, by having MySQL HeatWave be offered on AWS, it makes the proposition even more compelling because, as you said, yes, there is some engineering work that customers will need to do to migrate between clouds, and if they don't want to, then absolutely now they have MySQL HeatWave which they can now use in AWS itself.Corey: I think that one of the things I continually find myself careening into, perhaps unexpectedly, is a failure to really internalize just how vast this entire industry really is. Every time I think I've seen it all, all I have to do is talk to one more cloud customer and I learn something completely new and different. Sometimes it's an innovative, exciting use of a thing. Other times, it's people holding something fearfully wrong and trying to use it as a hammer instead. And you know, if it's dumb and it works, is it really dumb? There are questions around that.And this in turn gave rise to one of my next obnoxious questions as I was looking at what you were building at the time because a lot of your pricing and discussions and framing of this was targeting very large enterprise-style customers, and the price points reflected that. And then I asked the question that Big E enterprise never quite expects, for whatever reason, it's like, “That looks awesome if I have a budget with many commas in it. What can I get for $4?” And as of this recording, pricing has not been finalized slash published for the service, but everything that you have shown me so far absolutely makes developing on this for a proof of concept or an evening puttering around, completely tenable: it is not bound to a fixed period of licensing; it's, use it when you want to use it, turn it off when you're done; and the hourly pricing is not egregious. I think that is something that historically, Oracle Database offerings have not really aligned with.OCI very much has, particularly with an eye toward its extraordinarily awesome free tier that's always free. But this feels like it's a weird blending of the OCI model versus historical Oracle Database pricing models in a way that, honestly I'm pretty excited about.Nipun: So, we react to what the customer requirements and needs are. So, for this class of customers who are using, say, RDS, MySQL, Aurora, we understand that they are very cost sensitive, right? So, one of the things which we have done in addition to offering MySQL HeatWave on AWS is based on the customer feedback and such. We are now offering a small shape of HeatWave instance in addition to the regular large shape. So, if customers want to just, you know, kick the tires, if developers just want to get started, they can get a MySQL node with HeatWave for less than ten cents an hour. So, for less than ten cents an hour, they get the ability to run transaction processing, analytics, and machine learning.And if you were to compare the corresponding cost of Aurora for the same, like, you know, core count, it's, like, you know, 12-and-a-half cents. And that's just Aurora, without Redshift or without SageMaker. So yes, you're right that based on the feedback and we have found that it would be much more attractive to have this low-end shape for the AWS developers. We are offering this smaller shape. And yeah, it's very, very affordable. It's about just shy of ten cents an hour.Corey: This brings up another question that I raised pretty early on in the process because you folks kept talking about shapes, and it turns out that is the Oracle Cloud term that applies to instance size over an AWS-land. And as we dug into this a bit further, it does make sense for how you think about these things and how you build them to customers. Specifically, if I want to run this, I log into cloud.oracle.com and sign up for it there, and pay you over on that side of the world, this does not show up on my AWS bill. What drove that decision?Nipun: Okay, so a couple of things. One clarification is that the site people log in to is cloud.mysql.com. So, that's where they come to: cloud.mysql.com.Corey: Oh, my apologies. I keep forgetting that you folks have multiple cloud offerings and domains. They're kind of a thing. How do they work? Given I have a bad domain by habit myself, I have no room to judge.Nipun: So, they come to cloud.mysql.com. From there, they can provision an instance. And we, as, like, you know, Oracle or MySQL, go ahead and create an instance in AWS, in the Oracle tenancy. From there, customers can then, you know, access their data on AWS and such. Now, what we want to provide the customers is a very seamless experience, that they just come to cloud.mysql.com, and from there, they can do everything: provisioning an instance, running the queries, payment and such. So, this is one of the reasons that we want customers just to be able to come to the site, cloud.mysql.com, and take care of the billing and such.Now, the other thing is that, okay, why not allow customers to pay from AWS, right? Now, one of the things over there is that if you were to do that and there's a customer, they'll be like, “Hey, I got to pay something to AWS, something to Oracle, so we'd prefer, it'd be better to have a one-stop shop.” And since many of these are already Oracle customers, it's helpful to do it this way.Corey: Another approach you could have taken—and I want to be very clear here that I am not suggesting that this would have been a good idea—but an approach that you could have taken would have been to go down the weird AWS partner rabbit hole, and we're going to provide this to customers on the AWS Marketplace. Because according to AWS, that's where all of their customers go to discover new softwares. Yeah, first, that's a lie. They do not. But aside from that, what was it about that Marketplace model that drove you to a decision point where okay, at launch, we are not going to be offering this on the AWS Marketplace? And to be clear, I'm not suggesting that was the wrong decision.Nipun: Right. The main reason is we want to offer the MySQL HeatWave service at the least expensive cost to the user, right, or like, the least cost. If you were to, like, have MySQL HeatWave in the Marketplace, AWS charges a premium. This the customers would need to pay. So, we just didn't want the customers to have to pay this additional premium just because they can now source this thing from the Marketplace. So, it's really to, like, save costs for the customer.Corey: The value of the Marketplace, from my perspective, has been effectively not having to deal as much with customer procurement departments because well, AWS is already on the procurement approved list, so we're just going to go ahead and take the hit to wind up making it accessible from that perspective and calling it good. The downside to this is that increasingly, as customers are making larger and longer-term commitments that are tied to certain levels of spend on AWS, they're increasingly trying to drag every vendor with whom they do business into the your AWS bill so they can check those boxes off. And the problem that I keep seeing with that is vendors who historically have been doing just fine, have great working relationships with a customer are reporting that suddenly customers are coming back with, “Yeah, so for our contract renewal, we want to go through the AWS Marketplace.” In return, effectively, these companies are then just getting a haircut off whatever it is they're able to charge their customers but receiving no actual value for any of this. It attenuates the relationship by introducing a third party into the process, and it doesn't make anything better from the vendor's point of view because they already had something functional and working; now they just have to pay a commission on it to AWS, who, it seems, is pathologically averse to any transaction happening where they don't get a cut, on some level. But I digress. I just don't like that model very much at all. It feels coercive.Nipun: That's absolutely right. That's absolutely right. And we thought that, yes, there is some value to be going to Marketplace, but it's not worth the additional premium customers would need to pay. Totally agree.Corey: This episode is sponsored in part by our friends at AWS AppConfig. Engineers love to solve, and occasionally create, problems. But not when it's an on-call fire-drill at 4 in the morning. Software problems should drive innovation and collaboration, NOT stress, and sleeplessness, and threats of violence. That's why so many developers are realizing the value of AWS AppConfig Feature Flags. Feature Flags let developers push code to production, but hide that that feature from customers so that the developers can release their feature when it's ready. This practice allows for safe, fast, and convenient software development. You can seamlessly incorporate AppConfig Feature Flags into your AWS or cloud environment and ship your Features with excitement, not trepidation and fear. To get started, go to snark.cloud/appconfig. That's snark.cloud/appconfig.Corey: It's also worth pointing out that in Oracle's historical customer base, by which I mean the last 40 years that you folks have been in business, you do have significant customers with very sizable estates. A lot of your cloud efforts have focused around, I guess, we'll call it an Oracle-specific currency: Oracle Credits. Which is similar to the AWS style of currency just for a different company in different ways. One of the benefits that you articulated to me relatively early on was that by going through cloud.mysql.com, customers with those credits—which can be in sizable amounts based upon various differentiating variables that change from case to case—and apply that to their use of MySQL HeatWave on AWS.Nipun: Right. So, in fact, just for starters, right, what we give to customers is we offer some free credits for customers to try a service on OCI of, you know, $300. And that's the same thing, the same experience you would like customers who are trying HeatWave on AWS to get. Yes, so you're right, this is the kind of consistency we want to have, and yet another reason why cloud.mysql.com makes sense is the entry point for customers to try the service.Corey: There was a time where I would have struggled not to laugh in your face at the idea that we're talking about something in the context of an Oracle database, and well, there's $300 in credit. That's, “What can I get for that? Hung up on?” No. A surprising amount, when it comes to these things.I feel like that opens up an entirely new universe of experimentation. And, “Let's see how this thing actually works with his workload,” and lets people kick the tires on it for themselves in a way that, “Oh, we have this great database. Well, can I try it? Sure, for $8 million, you absolutely can.” “Well, it can stay great and awesome over there because who wants to take that kind of a bet?” It feels like it's a new world and in a bunch of different respects, and I just can't make enough noise about how glad I am to see this transformation happening.Nipun: Yeah. Absolutely, right? So, just think about it. So, you're getting MySQL and HeatWave together for just shy of ten cents an hour, right? So, what you could get for $300 is 3000 hours for MySQL HeatWave instance, which is very good for people to try for free. And then, you know, decide if they want to go ahead with it.Corey: One other, I guess, obnoxious question that I love to ask—it's not really a question so much as a statement; that that's part of the first thing that makes it really obnoxious—but it always distills down to the following that upsets product people left and right, which is, “I don't get it.” And one of the things that I didn't fully understand at the outset of how you were structuring things was the idea of separating out HeatWave from its constituent components. I believe it was Autopilot if I'm not mistaken, and it was effectively different SKUs that you could wind up opting to go for. And okay, if I'm trying to kick the tires on this and contextualize it as someone for whom the world's best database is Route 53, then it really felt like an additional decision point that I wasn't clear on the value of. And I'm still not entirely sure on the differentiation point and the value there, but now you offer it bundled as a default, which I think is so much better, from the user experience perspective.Nipun: Okay, so let me clarify a couple of things.Corey: Please. Databases are not my forte, so expect me to wind up getting most of the details hilariously wrong.Nipun: Sure. So, MySQL Autopilot provides machine-learning-based automation for various aspects of the MySQL service; very popular. There is no charge for it. It is built into MySQL HeatWave; there is no additional charge for it, right, so there never was any SKU for it. What you're referring to is, we have had a SKU for the MySQL node or the MySQL instance, and there's a separate SKU for HeatWave.The reason there is a need to have a different SKU for these two is because you always only have one node of MySQL. It could be, like, you know, running on one core, or like, you know, multiple cores, but it's always, like, you know, one node. But with HeatWave, it's a scale-out architecture, so you can have multiple nodes. So, the users need to be able to express how many nodes of HeatWave are they provisioning, right? So, that's why there is a need to have two SKUs, and we continue to have those two SKUs.What we are doing now differently is that when users instantiate a MySQL instance, by default, they always get the HeatWave node associated with it, right? So, they don't need to, like, you know, make the decision to—okay when to add HeatWave; they always get HeatWave along with the MySQL instance, and that's what I was saying a combination of both of these is, you know, like, just about ten cents an hour. If for whatever reason, they decide that they do not want HeatWave, they can turn it off, and then the price drops to half. But what we're providing is the AWS service that HeatWave is turned on by default.Corey: Which makes an awful lot of sense. It's something that lets people opt out if they decide they don't need this as they continue to scale out, but for the newcomer who does not, in many cases—in my particular case—have a nuanced understanding of where this offering starts and stops, it's clearly the right decision of—rather than, “Oh, yeah. The thing you were trying and it didn't work super well? Well, yeah. If you enable this other thing, it would have been awesome.” “Well, great. Please enable it for me by default and let me opt out later in time as my level of understanding deepens.”Nipun: That's right. And that's exactly what we are doing. Now, this was a feedback we got because many, if not most, of our customers would want to have HeatWave, and we just kind of, you know, mitigating them from going through one more step, it's always enabled by default.Corey: As far as I'm aware, you folks are running this effectively as any other AWS customer might, where you establish a private link connection to your customers, in some cases, or give them a public or private endpoint where they can wind up communicating with this service. It doesn't require any favoritism or special permissions from AWS themselves that they wouldn't give to any other random customer out there, correct?Nipun: Yes, that is correct. So, for now, we are exposing this thing as a public endpoint. In the future, we have plans to support the private endpoint as well, but for now, it's public.Corey: Which means that foundationally what you're building out is something that fits into a model that could work extraordinarily well across a variety of different environments. How purpose-tuned is the HeatWave installation you have running on AWS for the AWS environment, versus something that is relatively agnostic, could be dropped into any random cloud provider, up to and including the terrifyingly obsolete rack I have in the spare room?Nipun: So, as I mentioned, when we decided to offer MySQL HeatWave on AWS, the idea was that okay, for the AWS customers, we now want to have an offering which is completely optimized for AWS, provides the best price-performance on AWS. So, we have determined which instance types underneath will provide the best price performance, and that's what we have optimized for, right? So, I can tell you, like, in terms of many of—for instance, take the case of the cache size of the underlying processor that we're using on AWS is different than what we're using for OCI. So, we have gone ahead, made these optimizations in our code, and we believe that our code is really optimized now for the AWS infrastructure.Corey: I think that makes a fair deal of sense because, again, one of the big problems AWS has had is the proliferation of EC2 instance types to the point now where the answer is super easy, too, “Are you using the correct instance type for your workload?” Because that answer now is, “Of course not. Who could possibly say that they were with any degree of confidence?” But when you take the time to look at a very specific workload that's going to be scaled out, it's worth the time investment to figure out exactly how to optimize things for price and performance, given the constraints. Let's be very clear here, I would argue that the better price performance for HeatWave is almost certainly not going to be on AWS themselves, if for no other reason than the joy that is their data transfer pricing, even for internal things moving around from time to time.Personally, I love getting charged data transfer for taking data from S3, running it through AWS Glue, putting it into a different S3 bucket, accessing it with Athena, then hooking that up to Tableau as we go down and down and down the spiraling rabbit hole that never ends. It's not exactly what I would call well-optimized economically. Their entire system feels almost like it's a rigged game, on some level. But given those constraints, yeah, dialing in it and making it cost-effective is absolutely something that I've watched you folks put significant time and effort into.Nipun: So, I'll make two points, right, to the questions. First is yes, I just want to, like, be clear about it, that when a user provisions MySQL HeatWave via cloud.mysql.com and we create an instance in AWS, we don't give customers a multitude of things to, like, you know, choose from.We have determined which instance type is going to provide the customer the best price performance, and that's what we provision. So, the customer doesn't even need to know or care, is it going to be, like, you know, AMD? Is it going to be Intel? Is it going to be, like, you know, ARM, right? So, it's something which we have predetermined and we have optimized for it. That's first.The second point is in terms of the price performance. So, you're absolutely right, that for the class of customers who cannot migrate away from AWS because of the egress costs or because of the high latency because of AWS, right, sure, MySQL HeatWave on AWS will provide the best price-performance compared to other services out in AWS like Redshift, or Aurora, or Snowflake. But if customers have the flexibility to choose a cloud of their choice, it is indeed the case that customers are going to find that running MySQL HeatWave on OCI is going to provide them, by far, the best price performance, right? So, the price performance of running MySQL HeatWave on OCI is indeed better than MySQL HeatWave on AWS. And just because of the fact that when we are running the service in AWS, we are paying the list price, right, on AWS; that's how we get the gear. Whereas with OCI, like, you know, things are a lot less expensive for us.But even when you're running on AWS, we are very, very price competitive with other services. And you know, as you've probably seen from the performance benchmarks and such, what I'm very intrigued about is that we're able to run a standard workload, like some, like, you know, TPC-H and offer seven times better price-performance while running in AWS compared to Redshift. So, what this goes to show is that we are really passing on the savings to the customers. And clearly, Redshift is not doing a good job of performance or, like, you know, they're charging too much. But the fact that we can offer seven times better price performance than Redshift in AWS speaks volumes, both about architecture and how much of savings we are passing to our customers.Corey: What I love about this story is that it makes testing the waters of what it's like to run MySQL HeatWave a lot easier for customers because the barrier to entry is so much lower. Where everything you just said I agree with it is more cost-effective to run on Oracle Cloud. I think there are a number of workloads that are best placed on Oracle Cloud. But unless you let people kick the tires on those things, where they happen to be already, it's difficult to get them to a point where they're going to be able to experience that themselves. This is a massive step on that path.Nipun: Yep. Right.Corey: I really want to thank you for taking time out of your day to walk us through exactly how this came to be and what the future is going to look like around this. If people want to learn more, where should they go?Nipun: Oh, they can go to oracle.com/mysql, and there they can get a lot more information about the capabilities of MySQL HeatWave, what we are offering in AWS, price-performance. By the way, all the price performance numbers I was talking about, all the scripts are available publicly on GitHub. So, we welcome, we encourage customers to download the scripts from GitHub, try for themselves, and all of this information is available from oracle.com/mysql where they can get this detailed information.Corey: And we will, of course, put links to that in the show notes. Thank you so much for your time. I appreciate it.Nipun: Sure thing, Corey. Thank you for the opportunity.Corey: Nipun Agarwal, Senior Vice President of MySQL HeatWave. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice along with an angry insulting comment. You will then be overcharged for the data transfer to submit that insulting comment, and then AWS will take a percentage of that just because they're obnoxious and can.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

Nipun Sharma, CEO & Co-Founder of SJW Food Robotics, Inc, talks about how robotic restaurant automation can be a game-changer in the food industry. Nipun gave a brief history of his background and how the SJW Robotics Food was created. We also talked about how the entire business model works and how they had a vision for the future generation of quick-service restaurants, which was significant. He also stated that carbon neutrality and sustainability are vital components of his business in terms of food safety and full traceability. We also discussed designer recipes and how they source ingredients and ensure quality by making sure that the impact of machine limitations is not limited to the food that they produce but to greater perfection in taste, as well as how machines do all the hardware robotic stuff that is controlled by programming. SJW Food Robotics, Inc is a pioneering FoodTech firm situated in Toronto, Canada that develops autonomous kitchen robotic systems for the hospitality market. The company's multi-disciplinary core team aims to reshape the foodservice industry through scalable and profitable automated solutions - merging the art of cooking with the science of automation - drawing on sixty years of combined experience in autonomous machine engineering, restaurant concept development, and foodservice manufacturing.

About NipunNipun Agarwal is a Senior Vice President, MySQL HeatWave and Advanced Development, Oracle. His interests include distributed data processing, machine learning, cloud technologies and security. Nipun was part of the Oracle Database team where he introduced a number of new features. He has been awarded over 170 patents.Links:Oracle: https://www.oracle.com TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored in part by our friends at Vultr. Spelled V-U-L-T-R because they're all about helping save money, including on things like, you know, vowels. So, what they do is they are a cloud provider that provides surprisingly high performance cloud compute at a price that—while sure they claim its better than AWS pricing—and when they say that they mean it is less money. Sure, I don't dispute that but what I find interesting is that it's predictable. They tell you in advance on a monthly basis what it's going to going to cost. They have a bunch of advanced networking features. They have nineteen global locations and scale things elastically. Not to be confused with openly, because apparently elastic and open can mean the same thing sometimes. They have had over a million users. Deployments take less that sixty seconds across twelve pre-selected operating systems. Or, if you're one of those nutters like me, you can bring your own ISO and install basically any operating system you want. Starting with pricing as low as $2.50 a month for Vultr cloud compute they have plans for developers and businesses of all sizes, except maybe Amazon, who stubbornly insists on having something to scale all on their own. Try Vultr today for free by visiting: vultr.com/screaming, and you'll receive a $100 in credit. Thats V-U-L-T-R.com slash screaming.Corey: Couchbase Capella Database-as-a-Service is flexible, full-featured and fully managed with built in access via key-value, SQL, and full-text search. Flexible JSON documents aligned to your applications and workloads. Build faster with blazing fast in-memory performance and automated replication and scaling while reducing cost. Capella has the best price performance of any fully managed document database. Visit couchbase.com/screaminginthecloud to try Capella today for free and be up and running in three minutes with no credit card required. Couchbase Capella: make your data sing.Corey: Welcome to Screaming in the Cloud, I'm Corey Quinn. Today's promoted episode is a returning guest with a slight difference. When last we spoke, Nipun Agarwal was a VP over at Oracle, but now—that's right. When people stay in a company long enough and perform well, they wind up getting additional adjectives in lieu of other things—Nipun, you're now a Senior VP over at Oracle. Congratulations, I think, unless that just means you've gotten older. Welcome back.Nipun: Thank you, Corey.Corey: So, now that you're at SVP level, I can ask some of the harder questions that we didn't necessarily—seem fair to get into the last time we spoke, such as what is an Oracle, and what might they do these days? For folks who have, I don't know, been living in a cave for 40 years.Nipun: Corey, glad to be back on your show. And since the last time we spoke, we have had, like, you know, a lot of enhancements and innovations, and I'll be happy to describe those in detail whenever is a good time.Corey: Absolutely so you've been focused on MySQL for a very long time. And you've been using it so long, I really should be calling it YourSQL, but that's neither here nor there. And you've also been focusing on HeatWave, which is effectively MySQL with then some—I'm just going to cheat and call it magic that is layered on top of it. That is probably a terrible descriptor of what it actually does, but understand I'm coming from a perspective where I firmly believe the best database in the world is Amazon Route 53, which is a DNS server, so people look at that and say, ‘well, that's not really what it's designed to do,' which really sounds like a ‘them' problem. And fair enough. We're going to invert it here. So, why is HeatWave a terrible DNS server? What is it exactly?Nipun: So, MySQL is the most popular database in the world—it's the most popular open-source database in the world—lots of people use it. All the major cloud vendors, they take the MySQL database, and either as is or, like, you know, with some enhancements, they offer a managed service, whether it's Amazon, Azure, Google, pretty much all the major cloud vendors. Now, MySQL has been designed and optimized for transaction processing, so it does a great job for transaction processing. But when customers need to run complex queries or when they need to run analytics, customers would have to take the data out of the MySQL database into some other database for running analytics.Corey: Let me make sure I understand your terms properly. When you say ‘transactional,' you're talking about I'm shopping for underpants on a website. I go ahead and make a purchase; that's considered a transaction, and a database change reflecting my purchase makes sense. From an analytics perspective, you're like, “All right, let's see who bought underpants during this time period.” It's effectively, usually, a small individual record versus now we're going to start doing deep dives into effectively a lot of those records in aggregate, is that directionally correct, or is my understanding more than a little flawed about things beyond DNS?Nipun: Right. What you describe is very accurate. That transaction processing is about point queries making frequent changes, whereas when we talk about analytics, it typically involves scanning a much larger amount of data to get the results, and aggregations is a very good example of that.Corey: So historically, that seems that people have used very different tooling for different sides of those. Ideally—I admit, back in the bad old days when I was a systems administrator, we were running MySQL a fair bit, and we had the primary database, which was the thing that handled all of the live transactions and the rest, and whenever we ran business reporting queries on it, it's like, “Huh, why is the website super slow?” And it didn't seem to work very well. Now, back then, at the scale we were operating at the solution was, “Ah, we're going to use a replica, and then we're going to basically beat the crap out of the replica for our reporting queries.” And if that gets a little slow and bogged down, who cares? Well, just other people running reporting queries; people can still buy underpants.So, that was the way that we handled it back then. This was a decade ago. Data sets have gotten significantly larger since then, and apparently, my way of viewing it is, as they say, quaint when they're trying not to be actively insulting. The right way to do it these days is to have completely separate systems that wind up handling those queries with different user interfaces by and large. That is, to my understanding, the rise of ‘Big Data,' and you can hear the initial caps in Big Data with people talk about it like that.Nipun: Correct. So, what you describe is absolutely correct that people would extract the data out of databases, take it to specialized databases, which are [apt 00:05:11] for running decision-making analytic processing. But the downside is that a people need to express the logic and write code to extract this data, and then customers end up with these two different databases. They got to keep the data in sync, they got to move the data periodically. So, there are a lot of, like, you know, issues in terms of having to manage two different databases, one for transaction processing, one for analytics.What we have done with HeatWave is to enhance the MySQL database service in the Oracle Cloud so that now the single MySQL database is optimized both for transaction processing as well as analytics. So, now you have a single database. And whether you want to run point queries or these aggregate queries, you can do it on the same data. So, the data remains as is. You're bringing richness of computation, richness in query processing, to the customers.Corey: One of the truisms of cloud is that it forces a reevaluation, in many cases, of things that people historically hadn't had to think about it. A classic example when I was consulting on cloud migrations, was building up costing models, as you might imagine. And my customers would ask me questions, such is, “Great. So, what's this going to cost us?” And I would come back with, “Well, okay, how many gigabytes in a given month does transfer between this database and that other database, you know, in the machine sitting right next to it?” And their response started off with a, “Why on earth do you think we would know that?” Followed by, “Wait, why do we need to know that?” Followed by, “Oh, God. It costs us to do what?”And very quickly an architectural pattern has emerged within cloud of—you know, people experience this the second time, they plan for it. And as a result, whatever database is the most cost-effective is the one that data is already in because moving data from point to point is inherently an expensive proposition. Depending on where the second point is, it can be an extortionately expensive proposition. Which means that very often, we'll start to see patterns that are, I guess, sacrificing one side of the database interaction model or the other, that transactions are going to be a little slower because you need to have it in the same place you're going to be running large scale analytics on, or alternately, analytics are going to be super crappy, just because you have to wind up querying systems during downtimes and low periods. It just becomes a giant mess, regardless of whether it's bad in one way, bad in another, or just expensive, it hasn't worked for people. And my sense is that that is what HeatWave is directly aimed.Nipun: Yes. Indeed. So, there are multiple reasons why HeatWave is being so successful. One is the case that okay, customers need a single database, instead of having multiple. The second thing is, there is absolutely no change required to MySQL applications, so the MySQL applications or MySQL compatible applications work as-is with this query [unintelligible 00:08:10] HeatWave without any change.But the third reason why this is so popular is that HeatWave has been designed from the ground up for scalability, performance, and optimized for the underlying gear, which is the underlying cloud platform. As a result, it offers a very good price-performance compared to any of the service we have run against. So, not only is it providing the benefits of having a single database, no change to the application, but also it is extremely fast and low price. And that's because a lot of technology innovations we did, like, almost like, over a decade to build this, scale our system for analytic processing, which has been optimized for the underlying cloud [commodity 00:08:55] gear.Corey: So, help me understand. Is HeatWave a, effectively, reengineering of MySQL? Is it a completely separate layer that exists distinct from an existing MySQL database? Or is it something else entirely?Nipun: So, we started off designing HeatWave separately as something ground up, which came out of many years of research and advanced developing. And once we knew that we could scale up HeatWave for analytic processing, and it is very well optimized for the underlying hardware and such. Then we did the work of enhancing the MySQL database so that it can be integrated, right? So yes, it started off as a standalone effort from the ground up so that we didn't have to, you know, [live 00:09:38] any constraints of any existing codebase, so we could design it and optimize it right from the ground up to be the best possible. But then we integrated this thing with the MySQL database so that the customers can use it without requiring any change to the application in terms of the semantics or any new syntax, right? So, there's absolutely no new syntax and no change to the semantics for existing MySQL applications. So, it gives you best of both worlds.Corey: So, this has frequently been described in the context of a competitor to very—again, forgive the Amazonian focus; that's where I spend most of my time, usually complaining about things—but it's been positioned in some ways as a competitor to things such as RDS or Aurora, as well as Redshift, or Snowflake if we're stepping slightly outside that ecosystem. The challenge that I keep running into, very often, is that when I talk to customers using those systems—and yes, those systems invariably show up on the bill as one of the big numbers, regardless of how you slice it—it feels like their use case for each of those is very different, it feels very much like half of those are aimed at purely transactional and half of them are aimed at the data warehousing story, the large amounts of data for analytics queries. And my default knee-jerk reaction, whenever someone says, “Ah, we built a thing that does both of those super well,” it's, “Yeah, I've heard this before, it was the HP multifunction printer where it does three things, none of them well.” And no one has a multifunction printer that they liked for the longest time—because it's moving parts and computers and the devil in equal measure—and it's okay, so you're trying to build something that stands between two worlds, but it's easy to come away with the conclusion, as a result, that it's not the best of breed for either use case, but rather a series of trade-offs or compromises that are made to enable both use cases. I get the sense that that is not your impression of what you've built.Nipun: Correct. And I'll give you a data point for that. In the data point is—Corey: Yay. Data I love that. As opposed to your opinion is bad because my opinion is good. No, no, coming with data is a great approach. Please continue.Nipun: [laugh]. In terms of the customers who are using or adopting MySQL HeatWave, one of the largest segments of the customers who are migrating their production workloads from other databases or other services and coming to HeatWave are AWS customers who are migrating their production workloads from RDS or Aurora and are going production with MySQL HeatWave. So, the fact that the customers are doing that is an evidence that there is some value to it. And the reasons they are doing it is absolutely no change to their application, it is faster, it is cheaper. Now, in addition, what they find is that many of these customers were moving their data from Aurora or RDS into Redshift or Snowflake for analytics. They don't need to do that, right, and that's an additional savings they get.But we have a lot of evidence that existing customers have MySQL-based services—definitely AWS, but even on other clouds—and Aurora are migrating, and that's very encouraging for us that, hey, we should be doing something right for customers to want to migrate their workloads to MySQL HeatWave.Corey: You had a couple of announcements coming out about what's new and what's coming to HeatWave, and one of the ones that we're talking about today is the idea of elasticity. Something you just said reminds me of a couple years ago when Amazon had relatively recently brought out Aurora and they said much the same thing of, “Oh, it's super-elastic. You don't have to take it down to make it bigger.” And it's great. Well, you just talked about people removing data as they migrate somewhere else, and the question I had at the time was, “Okay, great. So, that's how the database embiggens. That's great. How does it emsmallen? Does that wind up having that same elastic property?”And the response was very defensive, “Well, why would someone ever do that? Data only gets bigger.” And it's, yeah, well, you haven't worked with me in production where I accidentally drop a table now and again, and data does get smaller. And the answer for the longest time there was elasticity and auto-scaling was basically unidirectional because that's what customers are asking for. Right. So, I have to ask, when you say elasticity around HeatWave, is that unidirectional, or does it mean that oh, now there's less data, so we're going to go back down again.Nipun: It is bidirectional, so customers can upsize or they can downsize. Now, I have to say that HeatWave is a highly scalable system. And what that means is that as customers add more nodes to the cluster, the performance of the system improves almost linearly with the number of nodes which have been added. So, as a result, we have a lot of customers who start with a cluster size of certain number, and based on the workloads, they either add nodes or they reduce the number of nodes, right? So, it's a very common operation; people want to scale up and scale down.And with the real-time elasticity feature we have introduced, customers can do either operation and with absolutely no downtime. There's absolutely no time when the cluster is not available for queries or for DMLs, right? So, while the resize operation is going on, this cluster is fully available and customers can upsize to a number of nodes and downsize to any number of nodes.Corey: As it scales in or scales out, is that effectively doing its own internal sharding and rebalancing of data under the hood, invisible to customers? Is there something else going on? Like, how does this work?Nipun: Right. So, take the example that customer has, say, four nodes and they want to add two more notes. There are couple of interesting properties over here. We have a technical super-partitioning, by which we know exactly which are the blocks of data which have to be populated to the new nodes which have been added. However, one of the key design points of our elasticity is that there is no data movement between the nodes.So, all the data which has to be populated in the new nodes which are being added is fetched from the object store, the [OCI 00:15:50] object store. As a result, the existing cluster of four nodes is working as is, queries are working as is, without any degradation in performance. When the data has been populated to these additional nodes, the system then starts having the queries execute on the larger cluster. So, the smaller cluster is available all the time, then the larger clusters available, so from a user's perspective, they see absolutely no downtime. And since there is no data movement happening from the initial four nodes, there is no degradation of the existing queries which will be running on the older cluster.Corey: It's 2022 and you're announcing enhancements to a technology, so of course, it is a given that you are now talking as well about machine learning. Now, in a general sense, whenever someone says that my immediate instinctive reaction is to check my wallet in case someone is in the middle of picking my pocket because it seems like it winds up in some very weird places. What is machine learning and its applicability to HeatWave? Because generally speaking, when I look at things you can use machine learning for the answer is often finding signal from noise in large datasets and, of course, the ever-popular bias laundering. But I get the sense that neither one of those is quite what you're talking about here. What monstrosity have you built?Nipun: With MySQL HeatWave, customers are bringing in more data from either consolidating multiple MySQL databases into one, bringing workloads from other database into MySQL, but the volume of data which now customers are putting into MySQL HeatWave is growing because they want to run transaction processing, analytics all together in one database. Now, as the size of the data is growing, we are finding that many customers want to extract the data or currently need to extract the data out of the MySQL database to run machine-learning processing. So, some of the very large customers of MySQL HeatWave have been using HeatWave very successfully for transaction processing and analytics, but they had to extract the data out to some other ecosystem, to some other service for machine-learning processing. With the announcement we have made, which is HeatWave ML, we are now providing in-database support for machine learning, meaning that customers of MySQL HeatWave can do training, inference, as well as explanations, all inside MySQL HeatWave, without the data or the model ever having to leave MySQL.And this is something which is fairly unique. Apart from the Oracle database, I'm not aware of any other database, which provides in-database machine-learning capabilities, and certainly not as rich, right, which is very efficient training, inference, and explanations. And all models which are created by HeatWave ML inside MySQL HeatWave can be explained, which is a pretty important capability which enterprise customers like to have.Corey: This episode is sponsored in part by our friends at Sysdig. Sysdig is the solution for securing DevOps. They have a blog post that went up recently about how an insecure AWS Lambda function could be used as a pivot point to get access into your environment. They've also gone deep in-depth with a bunch of other approaches to how DevOps and security are inextricably linked. To learn more, visit sysdig.com and tell them I sent you. That's S-Y-S-D-I-G dot com. My thanks to them for their continued support of this ridiculous nonsense.Corey: What does this wind up empowering customers to do? Give an example or two, just because it's easy to talk about this stuff in the abstract as far as, “Oh, it would theoretically let someone do X, Y or Z.” But the problem I found, generally speaking, in the world of machine learning is that it is challenging to articulate it in a way that people hear the story and think, “Hey, that looks like something I might want to do.” As opposed to the common stories are, “Well, if you have a world-spanning data set and want to do this, this, and this”—like, “Well, I don't. And I don't and I don't and I don't, so what value is it to me?” What capabilities does it unlock?Nipun: Right. So, with the introduction of HeatWave, what we had said is that customers don't need multiple databases: One for transaction processing, one for analytics; they can do both transactional processing and analytics with one database, right? That's what we started off with. Now, the same thing holds true for machine learning. Current customers of most databases need to extract data out of the database for doing machine learning.And we are saying, “Hey, that's not [unintelligible 00:19:45], analytics, mixed workloads, or machine learning. Your data can all be inside MySQL, MySQL HeatWave, and you can do all the processing with that service.” Now, the kinds of capabilities customers like to have for machine learning, training as the most important one. And training is a very time-consuming operation. And typically when customers do training and they're using some other service, it's time-consuming and it is very expensive as well.One of the very interesting properties here is that when you're running machine learning inside HeatWave, you don't need to provision any additional cluster, or you don't need to have any custom gear. This machine-learning training is happening on the same cluster which the user has provisioned for analytics or for transaction processing. So, on the same hardware, on the same cluster, now they can run machine-learning processing. So, the kind of use case which you're asking is when customers have this data—and I'll walk you through an example. Take the case of credit card, right?If a bank wants to determine whether they want to, like, deny someone a credit card or approve it, it's based on some characteristics. Many of the times, people use a rule-based mechanism, but now with data-driven approaches, people want to look at a lot of data and the system makes a recommendation that yes, this person is appropriate for, like, you know, granting the loan or not. And this is something for which customers—or, like, the enterprises want to have rich models which accurately provide a characterization of the data so that they can make the right predictions. So, training is very important because you want to get the training be done right on the data because it influences the quality of the predictions which are being made. And once a prediction is made, there may be reasons, like, there could be regulatory compliance reasons because of which the enterprise may need to offer an explanation that why was the credit card denied, just to kind of make sure that there wasn't any bias or unfairness.And that's where machine-learning explanation capabilities are also very helpful. So, this is an example: when someone goes for apply for a credit card, whether it's rejected or approved. Another example is that when someone is making a call, like a marketing team is making a call, and the system want to predict that will a call lead to a successful outcome or not. That's another example. So, machine learning is being used very—now—extensively, and one of the advantages of a database is a database is where there's a lot of data, so it's a very, very good opportunity to harness this data using machine learning. Because machine learning is really tied to the richness of data and to the amount of data someone has.Corey: That makes a lot of sense. So, it's… it definitely shines a light at a, if not the easy answer for a lot of those questions, a directions that are people are going to have a better time of mapping to their specific use cases. One that I think is easier for everyone to map to a specific use case is another component of what you folks are announcing which is cost reduction, which is, to be direct, not something people generally think of Oracle as the first example of. A company that's like, “Ah, that's the thing that's going to cost me less money.” And to be clear, I have no problem with that. I pride myself on absolutely not being the least expensive answer to basically anything. But it is an interesting direction to go in. There are a few ways you can wind up saving folks money. Which path have you folks taken?Nipun: Now, there are multiple ways in which we can reduce the cost for the customer. So, one thing to realize it is MySQL customers are very cost-sensitive. And in the previous benchmarks and results we have shown, we have shown that, you know, compared to other vendors, we are significantly faster—that HeatWave significantly faster and significantly cheaper. So, we have class of customers come to us saying, “Hey, you know what? Can you trade-off some performance for even lower cost?”And the way we have done is the following: We have doubled the amount of data which can be processed on a HeatWave node. So, HeatWave is an in-memory system, so the size of the cluster depends upon the amount of data which is being processed. And it depends upon the amount of data which can be processed per node. So, if you double the amount of data that can be processed per node, it means that now customers need a cluster half the size compared to what they were doing in the past, which reduces their cost by half. Now, please note, when they're running on a cluster half the size, the amount of time it takes to run the same query will double.So, what it means is, the system is providing the same price-performance because half the cost, double the time. But it's a choice that customers have. If they still want to get the same performance [unintelligible 00:24:38] earlier, they can continue to run on the larger cluster, but now they have a choice. So, in a way, we are providing an even lower entry point for customers. That's the first part of cost savings.Corey: And that makes sense because with a lot of the workloads you see where it's nice to be able to run analytics on the same type of data, you don't need the same level of responsiveness on a lot of those queries either, where it's, “So, we're trying to get an answer to this giant analytics query.” “Okay, so great. How quickly do you need it working?” When transactions are measured in fractions of a second, the answer to analytics queries is, “Well, Tuesday would be nice. We'd like it by Tuesday if you can find a way to pull that off.”So, there's no reason to pay for near-line-rate speeds if you don't need it for a lot of those queries, which is absolutely going to be an interesting option for folks. Now, you said there was a second aspect as well.Nipun: Yes. And the second aspect is, again, for analytics, right? Customers want to run the queries, they want to run it occasionally, they don't want to run it all the time, so what we are now introducing is a feature called ‘Pause and Resume.' And what it does is that if you're not using the cluster, you can pause and the system makes a copy of the data and all the metadata associated with the data in a backup, and when the user wants, they can resume and, like, you know, fetch the data, which is still in the in-memory presentation and all the metadata associated with Autopilot. And just resume, right? So, this is another way by which customers when they're not using the cluster for some duration time, they can pause it, and for the duration they pause it, they're not being charged.Corey: I am a big believer of the number one step of cloud economics is like, “Oh, should I buy it some reservations or lock into long-term contract?” “No. You should turn things off when you're not using them.” And people look at you strange, and say, “What? You can turn things off?” And yes, you absolutely can, which makes people feel better about generally not doing it.But again, customer behaviors are usually ones that makes sense in their context. I just look at from a billing perspective, and it seems a little weird. I like the option, particularly for things that are either non-production or only going to be relevant to production during certain time windows, there are a number of areas where that begins to make an awful lot of sense, and people would do it if it didn't require backing up the database, destroying the cluster, then re-provisioning the database restoring the cluster. And, yeah, people don't generally have weeks to spend on spin-up and spin-down.Nipun: Yes, in fact, that's a very, very good observation, Corey. I want to say that many of our customers who are running their production workloads and HeatWave, they also have a test environment. And exactly on the lines of what you said, that they want to have a copy of the data in the test environment, should something bad happen, but they don't want the cluster on all the time. They just wanted for some duration of time and for them, this pause and resume will be a very good idea. And also like, you know, save them money. So, something which we have seen with many of our customers.Corey: The last component of your announcement is one that I approach with a significant amount of skepticism because every time I start drifting in this direction, one thing is for certain: It's that I'm going to get yelled at on the internet. I'm referring, of course, to benchmarking. Now, Oracle historically has been a company that prefers people not benchmark and publish results of those benchmarks, backdating into the mists of history. And the argument has always been that people don't generally tend to benchmark database workloads appropriately, due to a series of misunderstandings, and let's be clear, this stuff is complicated. And a number of companies in the space love to talk about their benchmarks are great, and when you look into it, it's okay, those numbers are great.And you sort of know that the benchmarks that didn't perform so well are not the ones that they're talking about. And then their competitor immediately winds up chiming in, where it's, “Ah, they're doing it wrong because when you do these other benchmarks, our solution winds up being better.” And it winds up in a nerd slap-fight that no one, even the participants, particularly enjoy. What makes your benchmarks interesting is that you talk through not just what the benchmark results are—because, of course, that's the entire point—you're also putting the benchmark methodology and tooling up on GitHub where people can grab it and run it themselves, and see for yourself is the entire approach. That is—how do I put this politely—that is atypical of large companies in general and Oracle in particular. What changed?Nipun: Right. So, there are three things over here, Corey, right? The first thing is, as we talked about, MySQL is the most popular open-source database in the world. Pretty much all cloud vendors, they have some version of MySQL which they're offering as a managed service, and in many cases, they're enhancing MySQL and then offering their service. So, in the context of MySQL, it becomes very important for us to give the opportunity to our customers, for them to compare which service is better for their needs.So, is more important in the context of MySQL, since everyone is offering it and some of them have derivatives, that we provide some mechanism for people to compare. So, that's the task for having a benchmark. That's the first point. Second thing is when you want to compare the performance or the cost of these, like, you know, various flavors, instead of us coming with our own, say, workloads which you see from customers, it's good to have a well-published benchmark, a well-understood benchmark, so that people can say, “Okay, you know what? Based on TPC-H, what is the performance?” Or, “On [TPC DS 00:29:54], what is the performance?”In some cases, when a benchmark isn't available, what we have done is for machine learning, we have used a bunch of open datasets and based on those open datasets, we are publishing the benchmarks to say, “Hey, we are so much faster or so much cheaper.”And then the third aspect is in terms of why we are making them all available in GitHub or open-source. That these benchmarks are a starting point, but customers will have workloads which are different from these benchmarks, so we want to provide the opportunity for the customers to first look at what is our methodology, what have we used to come up with these numbers so they can reproduce them, but, B, if their workloads are different, they can enhance or augment these benchmarks in the way they would like, and then run them to see how they compare, right? So, we want to be fully transparent about what we have done, how we have done, and let customers decide on their own which is going to be the best platform from a cost perspective, from a performance perspective. So, this is the reason why we have chosen to benchmark and GitHub, like, make available all over scripts in the open-source.Corey: One of the things I think I admire the most about that is I've always viewed benchmarks as being borderline worthless because I do not care in the slightest how your system performs on hand-selected ratings on sample data that you provide, whereas I care everything for how the system performs with my workloads and my data sets. So, unless I am talking to someone who is effectively a neutral third-party benchmark source, in which case they are immediately attacked for being shills for one company or another, and sometimes both or neither at the same time because people are terrible, but seeing how it runs on my workloads and with my constraints is the important and valuable thing. And this is the easiest I can ever see it being for getting a good representative feel for exactly how different offerings are going to perform under the specific conditions that my production environment lives within. Because it's me we're talking about the specific conditions of my production environment are, of course, terrifying.Nipun: Right. So, I want to point out, yes, one is the fact that we have made these benchmarks methodology, like, you know, very transparent, but the second aspect of that is what we talked about last time, which is MySQL Autopilot, right? This is machine-learning-based automation, data-driven-based automation. So, we are very actively working on making it easy for customers to not have to do any configuration changes or optimizations; that the system determines, based on the queries, based on the workloads, how to best tune the system, right?So, we are working in both angles: One is to make the system more intelligent, so that based on the workload, the system can optimize for the users workload, and then, B, making our approach very transparent so that customers can compare for themselves. So, we are very, very aware of this, and again, for MySQL customers, for many of these open-source customers, simplicity is very important and we are working hard to make it simpler and transparent to our users.Corey: I really want to thank you for taking me on a tour of what you're announcing today. Now, so let me ask one of the forbidden questions: What's on the roadmap? What's coming that customers can look forward to?Nipun: So, one of the things which we are working on is that there has been a very good reception of the HeatWave capabilities we have introduced, so MySQL HeatWave is one of the fastest-growing services in the Oracle Cloud. But there has been a lot of interest in customers who have been asking us to provide similar capabilities on AWS. So, this is something which we are working on; it's in the roadmap. And please stay tuned for more news on this.Corey: You can bet that I will. I really want to thank you for taking the time out of your day to basically suffer my slings and arrows, and also spend time teaching what amounts to a remedial database course to a moron. But thank you once again for being as generous with your time as you always are.Nipun: Well, thank you, Corey. It's always a pleasure to come and talk to the show. Thank you again, for the opportunity.Corey: Always. Nipun Agarwal, SVP at Oracle in charge of MySQL, YouSQL, and HeatWave. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice and explain how databases always fail your personal benchmark of doing a SELECT on a terabyte of data at once.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

SOC analysts are often overworked and under-appreciated — but that needs to change! How and where do the SOC and the SOC analyst make positive impacts on the business? That's exactly what we explore in this new episode.In this third of three episodes covering the first-ever SOC Analyst Appreciation Day, we get to speak with Nipun Gupta, a security engineer and security operations leader who has held roles at Deloitte and Deutsche Bank. During our conversation, we look at how the business value of the SOC can be much more than just blocking attacks and how business requirements map to SOC objectives and vice versa.ITSPmagazine is proud to partner with Devo to recognize the efforts put in by the practitioners working away in the trenches and on the front lines of cybersecurity. Join us to help us recognize them and their efforts.About the SOC Analyst Appreciation DayJoin us for five hours of live-streamed content — with sessions ranging from what skills are needed to move up in the SOC, to desk decompression from a yoga instructor, to a panel discussion about a day in the life of a SOC, to a "Lunch & Laugh" where a stand-up comedian will provide some much-needed de-stressing entertainment. There's a ton to celebrate — let's do this!Learn more about SOC Analyst Appreciation Day: https://itspm.ag/devoq0zz______________________________GuestNipun GuptaOn Linkedin | https://www.linkedin.com/in/guptanipun/______________________________To see and hear more conversations about and from this event as we explore the personal, technical, operational, and innovative aspects of this role:

Our guest for today's podcast is Pooja Malik, CEO & Founding Partner of Nipun Capital.  Pooja founded Nipun Capital in 2011 after a very successful career at Barclays Global Investors (BGI) where she was promoted quickly to become one of the youngest Managing Directors at the firm after successfully turning around BGI's active small cap equity strategy.   I very much enjoyed interviewing Pooja given she has been a perenial “underdog” all her life but has tackled every conceivable obstacle and overcome them by leaps and bounds.  As the middle child and daughter of a strong Indian mother who raised her family as a single parent after the death of her father when Pooja was 12, Pooja learned a lot about grit and determination from her mother.   As a woman and minority, Pooja is a role model and an inspiration for all of us in the AAAIM community.  I am so happy she believed enough in herself to launch her own hedge fund almost 10 years ago and took the time to share her story with us. 

Jason and Carrie talk to Clayton from Mapleton FC, who somehow manages not to backhand them for joking where A Taproom sits in relation to his neighborhood.  Martindale AFC player and League Director of Soccery Public Health Research Dr. Nipun claims ICF did a better job then the MLS during the global pandemic, and other things which surely prove he was drunk the whole show.  Indy Eleven's Josh Mason asks Carrie about her first professional soccer game on US soil, Luisa Macer from IMS previews next week's baller afterparty, and the Commish randomly sings.   Listen to Indy City Futbol Live Wednesdays at 6:30pm on 99.1 WQRT FM, attend show recordings Mondays at 5:30pm at A Taproom, or listen in large group settings at any gymnasium in Lithuania.

Legendary Nipun Mehta, founder of Karma Kitchen & ServiceSpace, and former member of the distinguished panel for initiating policy recommendations on poverty and inequality in America under President Obama, explains how to thrive in an interconnected world. Learn more about Nipun here: http://nipun.servicespace.org/ Follow Dr. Mayer: - https://linktr.ee/emayer

Legendary Nipun Mehta, founder of Karma Kitchen & ServiceSpace, and former member of the distinguished panel for initiating policy recommendations on poverty and inequality in America under President Obama, explains how to thrive in an interconnected world. Learn more about Nipun here: http://nipun.servicespace.org/ Follow Dr. Mayer: - https://linktr.ee/emayer

Shane talks with Biology professor, Dr. Nipun Chopra, about link between Alzheimer's disease and various environmental factors. Dr. Nipun Chopra is a graduate of DePauw University ('06) and received his PhD training from the Indiana University school of Medicine, with a focus on Medical Neuroscience. During his PhD work, his research focused on identifying microRNA that regulate key proteins involved in Alzheimer's disease. Nipun's Twitter: https://twitter.com/NipunChopra7 Thank you for watching and being an inquisitive being.

As the offseason approaches, it is time to review and overview the American lower division pro soccer landscape with three of the best reporters in the beat: Nipun Chopra, Kartik Krishnaiyer, and Jeff Rueter..

If you don't know what the hell is going on with Promotion & Relegation in US Soccer, this is the episode for you. We talk to journalist Nipun Chopra of Soctakes.com and Fourfourtwo.com. Nipun covers the lower leagues of American soccer. Homey knows his stuff. Laugh and learn as two comedians talk about some real ish of the state of American footy. Segment 1: NY Fest Stories! Trevor Noah! Michael Rappaport! [Your Favorite Celebrity]! Segment 2: Nipun Chopra Interview (@nipunchopra7) Segment 3: MLS Breakdown (TOR v CHI, NYC v ORL, RBNY v CLB, PHI v MTL) TODAY'S EPISODE IS SPONSORED BY HOWLER MAGAZINE subscribe at shop.howlermagazine.com and use promo code "COOLIGANS" FOR 20% OFF **We have a new weekly series on Youtube called "FIFA The News" which you should watch on our channel youtube.com/soccercooligans. New episodes every Friday. @notalexis @chrispolanco @soccercooligans Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode we discuss the increase of foreigners in Bollywood and their links to the fairness industry in India and whether or not their roles are taking jobs away from actual Indians. We are joined by Nipun Chopra from the WTF Bollywood Podcast who can be found at @NipunChopra7, thank you so much Nipun! We hope we don't offend anyone and we are only offering our opinions being non-members of the industry! Thank you for listening and we would love some feedback.