Podcast appearances and mentions of jay kreps

(0:00) Intro(1:26) How being a writer benefited Jay as a CEO(3:05) Building a management team(13:28) The Role of Titles in a Company(17:54) Only Going To One Year of High School(23:02) The Decision to Pursue Computer Science(31:05) The Birth of Project Kafka(34:32) Reflections on the Success of Kafka(36:47) Launching an Open Source Project(37:43) The Power of Product Marketing(39:35) Should You Be A Founder?(42:00) The Transition from Individual Contributor to CEO(47:51) Navigating the Public Markets(1:09:46) What's Wrong With Hybrid Work(1:14:27) Navigating Politics in the Workplace(1:17:36) Why Fairness Matters(1:26:51) The Evolution of Open Source(1:35:22) The Future of Artificial Intelligence(1:43:41) The Shift from Using Software to Becoming Software Produced: Rashad Assir & Leah ClapperMixed and edited: Justin HrabovskyExecutive Producer: Josh Machiz 

Neha Narkhede is a co-founder at Confluent, a data streaming software that raised at a $9.1b valuation in 2021. Neha later co-founded Oscilar, a no-code platform that helps companies detect and manage fraud. Before building these two companies, Neha was a Principal Software Engineer at LinkedIn where she co-created Apache Kafka. Neha is ranked #50 on Forbes' list of “America's Richest Self-Made Women 2023” with an estimated net worth of $520m. — In today's episode we discuss: The origins of Confluent, Kafka, and Oscilar How to become a successful second-time founder Advice for monetizing open source product Neha's unique GTM strategies How Confluent ran two businesses within one company Neha's path to founder market fit — Referenced: Apache Kafka: https://kafka.apache.org/ Confluent: https://www.confluent.io/ Confluent Cloud: https://www.confluent.io/confluent-cloud/ Jay Kreps, co-founder at Confluent: https://www.linkedin.com/in/jaykreps/ Jun Rao, co-founder at Confluent: https://www.linkedin.com/in/junrao/ MongoDB: https://www.mongodb.com/ Oscilar: https://oscilar.com/ — Where to find Neha: LinkedIn: https://www.linkedin.com/in/nehanarkhede/ Twitter/X: https://twitter.com/nehanarkhede Website: https://www.nehanarkhede.com/ — Where to find Brett: LinkedIn: https://www.linkedin.com/in/brett-berson-9986094/ Twitter/X: https://twitter.com/brettberson — Where to find First Round Capital: Website: https://firstround.com/ First Round Review: https://review.firstround.com/ Twitter: https://twitter.com/firstround Youtube: https://www.youtube.com/@FirstRoundCapital This podcast on all platforms: https://review.firstround.com/podcast — Timestamps: (00:00) Introduction (02:14)The origin story of Kafka (05:24) Co-creating Kafka at LinkedIn (07:31) Why open sourcing Kafka was a masterstroke (11:04) The unique nature of Confluent's Zero to One phase (16:35) Building for a specific customer early on (18:42) Inside Confluent's successful launch (20:12) Establishing Confluent as an enterprise company (22:00) The role of developer evangelism in Confluent's success (23:49) Using developer evangelism in category creation (26:41) Navigating early co-founder dynamics (30:06) Leveraging complementary founder skills (31:56) Advice for future founders (32:45) Building Confluent with monetization in mind (34:38) Monetizing open source products (36:05) GTM for subscription Saas versus consumption SaaS (39:48) The importance of founder-led GTM sales (40:58) Neha's order of operations for GTM sales (42:33) When to build out outbound sales (44:34) Adding SaaS to a software business (48:54) Choosing what to license and what to open source (52:38) How Confluent's co-founders decided on SaaS offering (56:04) Neha's journey as a second-time founder (58:54) Building Oscilar differently to Confluent (63:21) Going from speculation to product realization (69:06) Solving problems people are willing to pay for (71:13) Neha's “proactive research sprint” tactic (72:54) How Neha has applied this tactic

Confluent's platform provides infrastructure for enterprises to connect, stream and process data across applications and systems in real time. In this episode of the Tech Disruptors podcast, Confluent's cofounder and CEO Jay Kreps joins Bloomberg Intelligence senior software analyst Sunil Rajgopal to discuss the origins of Apache Kafka and Confluent, the flow of enterprise data and future of software architecture. The two also talk about the opportunity arising from the shift toward real-time data streaming from batch processing, budding artificial intelligence workloads and the company's new products such as Confluent Cloud for Apache Flink, Kora Engine and KSQL database.

"Designing Data-Intensive Applications"、通称 ”DDIA" 本について熱く語りました。 Amazon.co.jp (英語版) Amazon.co.jp (日本語版) Designing Data-Intensive Applications Martin Kleppmann Lambda Architecture Apache Samza Apache Avro Apache Kafka Apache Hadoop "Moving faster with data streams: The rise of Samza at LinkedIn" "Samza 1.0: Stream Processing at Massive Scale" Jay Kreps

The Dow fell, snapping a 6-day win streak, while the S&P and Nasdaq rose, and Jim Cramer is breaking down all the action - first, he's taking a closer look at how today's pause from the Federal Reserve shifted the market and how investors should approach it. Then, Cramer dove into Confluent last week and wanted more on the story - CEO Jay Kreps sits down with Cramer to share more about what the data company does and its applications. Plus, Cramer's exclusive with Bowlero CEO Tom Shannon. Mad Money Disclaimer

Our anchors begin today's show with Wells Fargo Chairman of Global Internet Investment Banking Bob Peck sharing his outlook for tech on the heels of yesterday's Fed rate hike. Then, our Julia Boorstin breaks down Roku's latest results sending shares lower, and Confluent Co-Founder and CEO Jay Kreps discusses the data management firm beating the Street in Q3. Next, CNBC's Dom Chu covers tech names that could be at risk from more rate hikes moving forward, and CNBC's Kate Rooney reports on trading platform Robinhood's quarterly figures. Later, CNBC's Ylan Mui takes a deep dive into PayPal Co-Founder Peter Thiel's multimillion-dollar investment in the campaign of Republican Arizona Senate candidate Blake Masters, and Equinix CEO Charles Meyers joins as shares soar on the data center company's results.

Our anchors begin today's show with CNBC's Steve Liesman reporting on the New York Fed's Survey of Consumer Expectations showing falling one- and three-year inflation expectations. Then, CNBC's Dom Chu breaks down last week's tech bounce, and Goldman Sachs Managing Director Eric Sheridan offers his take on the volatility plaguing e-commerce. Next, data management firm Confluent Co-Founder and CEO Jay Kreps shares his outlook for enterprise software, and our Julia Boorstin covers the latest from Disney's D23 fan event. CNBC's Hugh Son also discusses mounting threats to Goldman Sachs' Apple card business, and Morgan Stanley Managing Director Brian Nowak makes the case for Amazon as his top internet pick. Later, CNBC's Kate Rooney joins for a deep dive into Ethereum getting an upgrade projected to make the network more energy efficient.

Our anchors begin today's show covering crypto exchange Coinbase's partnership with asset management firm BlackRock, featuring insight from CNBC's Kate Rooney and MoffettNathanson Partner Lisa Ellis. Then, CNBC's Mike Santoli breaks down the Nasdaq's rally over the past month, and our Jon Fortt shares highlights from his Fortt Knox interview with software company ServiceNow CEO Bill McDermott. Next, Confluent Co-Founder and CEO Jay Kreps joins after the enterprise stock beat expectations in Q2, and CNBC's Phil LeBeau reports on results from EV makers Lucid and Tesla. Evercore ISI Head of Internet Research Mark Mahaney also shares his insight on online travel platform Booking Holdings' recent quarterly numbers, and our Julia Boorstin analyzes the latest wave of media earnings. Later, data center company Equinix CEO Charles Meyers discusses investor Jim Chanos' short on the space.

In 2011, Jay Kreps was an engineer at LinkedIn, leading the platform's search, recommendation engine, and social graph. In an effort to figure out how to make real-time streams of data useful to organizations, he started an open-source project called Kafka, and it took off. Realizing a major business opportunity, Jay took the leap into entrepreneurship and started Confluent in 2014. Today, over 70% of Fortune 500 companies use Kafka, and he took Confluent public in 2021. Jay shares what it means to process "data in motion," why it's daunting to go from being a software engineer to CEO, and why he only spent one year in a traditional high school before deciding to teach himself. 

When Confluent's President of Field Ops Erica Schultz was 23, she was working at Oracle and cold-emailed the manager of the Argentina office, asking to work for him. This experience would open the door to opportunities in Beunos Aires and Miami, a time in Erica's life she does not take for granted. As a leader today, she hopes to pass on this sentiment, constantly looking for individuals worth taking a chance on: “As I look around my organization, I think, OK, who's the undiscovered not-yet-fully-realized talent that we should think about for this role?”In this episode, Erica and Joubin talk about why Buenos Aires, Argentina is the best city in the world; the lessons she learned from her father and what changed for her after he died of a rare form of cancer at age 54; her stints at Oracle, LivePerson, and New Relic; the importance of earning responsibility as you advance in your career; staying both humble and paranoid; and the importance of what Confluent is doing in the ever-changing digital infrastructure business.In this episode, we cover: The incredible influence of Erica's namesake, her father, who passed away as her career was taking off (09:28) “The impact we leave is the impact we have on people” (15:21) How Erica became the captain of the Dartmouth rowing team after being cut from the swim team (18:03) Developing leaders from within a high-growth organization, and earning responsibility (31:36) Why Erica left a CRO role at LivePerson to work for the CRO of New Relic (37:03) Why she had her team at New Relic read “The Boys in the Boat” by Daniel James Brown, and loves the story of runner Roger Bannister (41:34) Being humbled by a changing competitive landscape, and the transformation of the digital infrastructure world (44:17) Real-time data and why both businesses and consumers increasingly need companies like Confluent (49:19) What Erica thought when she first met Confluent's founder CEO Jay Kreps (56:03) How to transition from operator to executive to board member (59:14) Links: Connect with EricaLinkedIn Connect with Joubin Twitter LinkedIn Email: grit@kleinerperkins.com  Learn more about Kleiner Perkins

When it comes to Apache Kafka®, there's no one better to tell the story than Jay Kreps (Co-Founder and CEO, Confluent), one of the original creators of Kafka. In this episode, he talks about the evolution of Kafka from in-house infrastructure to a managed cloud service and discusses what's next for infrastructure engineers who used to self-manage the workload. Kafka started out at LinkedIn as a distributed stream processing framework and was core to their central data pipeline. At the time, the challenge was to address scalability for real-time data feeds. The social media platform's initial data system was built on Apache™Hadoop®, but the team later realized that operationalizing and scaling the system required a considerable amount of work. When they started re-engineering the infrastructure, Jay observed a big gap in data streaming—on one end, data was being looked at constantly for analytics, while on the other end, data was being looked at once a day—missing real-time data interconnection. This ushered in efforts to build a distributed system that connects applications, data systems, and organizations for real-time data. That goal led to the birth of Kafka and eventually a company around it—Confluent.Over time, Confluent progressed from focussing solely on Kafka as a software product to a more holistic view—Kafka as a complete central nervous system for data, integrating connectors and stream processing with a fully-managed cloud service.Now as organizations make a similar shift from in-house infrastructure to fully-managed services, Jay outlines five guiding points to keep in mind: Cloud-native systems abstract away operational efforts for you without infrastructure concernsIt's important to have a complete ecosystem for Kafka, including connectors, a SQL layer, and data governanceA distributed system should allow data to be accessible everywhere and across organizationsIdentifying a reliable storage infrastructure layer that is dependable, such as Amazon S3 is criticalCost-effective models mean sustainability and systems that are easy to build aroundEPISODE LINKSBuilding Real-Time Data Systems the Hard WayKris Jenkins TwitterThe Hitchhiker's Guide to the GalaxyHedonic treadmillWatch the video version of this podcastJoin the Confluent CommunityLearn more with Kafka tutorials, resources, and guides at Confluent DeveloperLive demo: Intro to Event-Driven Microservices with ConfluentUse PODCAST100 to get an additional $100 of free Confluent Cloud usage (details)

Not too long ago, open-source technology projects were pursued in large part for altruistic reasons—they were “almost religious,” and not viewed as businesslike or potentially profitable, says Jay Kreps, the founder and CEO of newly public data company Confluent*.Today, companies like Confluent have changed that perception. Confluent—which commercializes the Apache Kafka open-source project and specializes in continuous, real-time data processing—went public this past June and just reported its first financial quarter with more than $100 million in revenue. On this episode of the Billion-Dollar B2B podcast, Battery General Partner Dharmesh Thakker talks with Kreps about the company's journey from a small project developed inside business-networking site LinkedIn into a large, public technology company.Jump straight into:00:00 - Creating Apache Kafka and Jay's start at LinkedIn - “The idea behind Kafka LinkedIn was that it could be like the central nervous system that would have those real-time impulses of what's happening.”05:03 - How to monetize an open-source company? - “You try and build a successful open source product and then build something that is unique to the company and completes the picture.”12:17 - Partnering with cloud providers and handling competitors - “When we do something it's accessible to everybody in the world, and that just makes it easier to build that community, and that kind of takes on a life of its own.”16:27 - Enterprise sales: Upgrading to bigger customers - “If you're able to do cloud only, which is easier, then I think it is better to start with self-service and get that going.”20:07 - Best practices for cloud or on-premise enterprise setting - “You need this very low friction self-service usage, which is how you can attach to developers. And then you turn it into part of the architecture that's used across the company.”26:19 - Confluent's visionary consumption model - “Customers can decide to do more at any time, they can spin up the next application. It's very low friction and I think it's a really powerful thing.” 31:17 - Successfully managing your roadmap and going public as a company - “The key thing for us was less about the scale of the business. It was just about getting to a point where we felt we could operate predictively.”36:16 - Confluent's major inflection points and Jay's final words of wisdom - “We felt very strongly that over time the bulk of the business was going to be in the cloud and if we could master that it would be a huge competitive move.”The views expressed here are solely those of podcast guests, not Battery.The information provided in this podcast is solely intended for the use of entrepreneurs, corporate CEOs and founders regarding Battery Ventures' potential financing capabilities for prospective portfolio companies. The information is current as of the date it was published. The contents are not intended to be used in the investment decision making process related to any product or fund managed by Battery Ventures. Battery Ventures provides investment advisory services solely to privately offered funds. Battery Ventures neither solicits nor makes its services available to the public or other advisory clients.Investments identified above are for illustrative purposes only. No

Our anchors kick off the morning with some of this year's tech winners and losers. Then, CNBC's Robert Frank joins to cover Elon Musk, Tesla, taxes and a Twitter poll. Next, we bring in Canaccord Analyst Jed Dorsheimer for more on Tesla with the stock moving lower this morning. Then, Confluent Co-Founder and CEO Jay Kreps joins as the company's shares get a boost off of strong earnings. Later, CNBC's Mike Santoli is here on how long this rally in tech stocks can continue. Plus, Bernstein Research's Stacy Rasgon joins on breaking news that AMD is partnering with Meta Platforms on data center chips. And later, Substack CEO Chris Best is here on his latest op-ed where he says Facebook is “captive to that original sin of the internet, the ad-based business model.”

Confluent Inc. raised $828 million in its initial public offering in the United States, pricing its shares above a marketed range. On Wednesday, the company sold 23 million shares for $36 each after marketing them for $29 to $33. Confluent was recently valued at $4.5 billion in a funding round. Confluent, founded in 2014 by Jay Kreps, Jun Rao, and Neha Narkede, has over 2,500 customers who use its platform to organize and manage data.

Our anchors kick off today's packed show with CNBC's Ylan Mui covering the latest on antitrust bills aimed at curbing big tech. Then, Index Ventures Partner Mike Volpi joins us to discuss top tech names following a second Nasdaq record close yesterday. Next, CNBC's Kate Rooney is live from Rockdale, Texas with the story on Bitcoin mining migrating to the state. Also, CNBC's Julia Boorstin is here to interview BuzzFeed CEO Jonah Peretti after the company officially announced a SPAC deal to take the media company public. We also have the reporter behind the ProPublica story detailing how Peter Thiel racked up billions using a Roth IRA loophole. Later, Confluent Co-Founder and CEO Jay Kreps joins us live from the Nasdaq as his company goes public via traditional IPO. Plus, we have Microsoft Corporate Vice President Yusuf Mehdi to break down the Windows 11 debut today.

Jay Kreps, CEO and Co-founder of Confluent discusses ksqlDB which is a database built specifically for stream processing applications to query streaming events in Kafka with SQL like interface.

Jay Kreps, CEO of Confluent discusses an enterprise integration architecture organized around an event log. Robert Blumen spoke with Jay about the N-squared problem of data integration; how LinkedIn tried and failed to solve the integration problem;  the nature of events; the enterprise event schema; schema definition languages; the use of an event log in […]

Jay Kreps, CEO of Confluent, talks with Robert Blumen about how an enterprise integration architecture organized around a Kafka event log simplifies integration and enables rich forms of data sharing. #podcast #seradio #ieeecs #ComputerSociety

Jay Kreps (Co-creator of Apache Kafka® and CEO, Confluent) introduces ksqlDB, an event streaming database. As the successor to KSQL, ksqlDB seeks to unify the multiple systems involved in stream processing into a single, easy-to-use solution for building event streaming applications.ksqlDB offers support for running connectors in an embedded mode, in addition to support for both push and pull queries. Push queries allow you to subscribe to changing query results as new events occur, while pull queries allow you to look up a particular value at a single point in time. To use a ride-sharing app as an example, there is both a continuous feed of the current position of the driver (a push query) and the ability to look up current values such as the price of the ride (a pull query). Databases are still effective in their own realms, and ksqlDB is not intended as a replacement. Rather, ksqlDB enables you to build event streaming applications with the same ease and familiarity of building traditional applications on a relational database. It simplifies the underlying architecture for these applications so you can build powerful, real-time systems with just a few SQL statements.EPISODE LINKSLearn about ksqlDB on the blogWatch the demo to see ksqlDB in actionGet started with ksqlDBFollow ksqlDB on TwitterWhy Kafka Connect? ft. Robin MoffattContributing to Open Source with the Kafka Connect MongoDB Sink ft. Hans-Peter GrahslConnecting to Apache Kafka with Neo4jJoin the Confluent Community SlackFully managed Apache Kafka as a service! Try free.

As Confluent turns five years old, special guest Jay Kreps (Co-founder and CEO, Confluent) brings us back to his early development days of coding Apache Kafka® over a Christmas holiday while working at LinkedIn. Kafka has become a breakthrough open source distributed streaming platform based on an abstraction of the distributed commit log, and his involvement in the project eventually led him to start Confluent with Jun Rao and Neha Narkhede. In this episode, Jay shares about all the highs and lows along the way, including some of his favorite customer success stories with companies like Lyft and Euronext, which empower their real-time businesses through event streaming with Confluent Cloud.Starting a company certainly comes with more than the technology, and Jay also reflects on some of the challenges around funding, support, and introducing Confluent to the rest of the world. How they have brought us from the beginning to now yields some wise words from Jay to any developer who is interested in establishing their own startup. EPISODE LINKSLyft on Production-Ready Kafka on KubernetesEuronext Stock Exchange Relies on Confluent for Event-Driven Trading PlatformJoin the Confluent Community SlackGet 30% off Kafka Summit registration using the code audio19

The post E921: Confluent Co-Founder & CEO Jay Kreps shares insights from building his data streaming cloud platform unicorn, new partnership with Google Cloud, learnings as lead engineer at LinkedIn, & the future of innovation in enterprise appeared first on This Week In Startups.

The post E921: Confluent Co-Founder & CEO Jay Kreps shares insights from building his data streaming cloud platform unicorn, new partnership with Google Cloud, learnings as lead engineer at LinkedIn, & the future of innovation in enterprise appeared first on This Week In Startups.

A EULA in FOSS clothing, NetBSD with more LLVM support, Thoughts on FreeBSD 12.0, FreeBSD Performance against Windows and Linux on Xeon, Microsoft shipping NetBSD, and more. Headlines A EULA in FOSS clothing? There was a tremendous amount of reaction to and discussion about my blog entry on the midlife crisis in open source. As part of this discussion on HN, Jay Kreps of Confluent took the time to write a detailed response — which he shortly thereafter elevated into a blog entry. Let me be clear that I hold Jay in high regard, as both a software engineer and an entrepreneur — and I appreciate the time he took to write a thoughtful response. That said, there are aspects of his response that I found troubling enough to closely re-read the Confluent Community License — and that in turn has led me to a deeply disturbing realization about what is potentially going on here. To GitHub: Assuming that this is in fact a EULA, I think it is perilous to allow EULAs to sit in public repositories. It’s one thing to have one click through to accept a license (though again, that itself is dubious), but to say that a git clone is an implicit acceptance of a contract that happens to be sitting somewhere in the repository beggars belief. With efforts like choosealicense.com, GitHub has been a model in guiding projects with respect to licensing; it would be helpful for GitHub’s counsel to weigh in on their view of this new strain of source-available proprietary software and the degree to which it comes into conflict with GitHub’s own terms of service. To foundations concerned with software liberties, including the Apache Foundation, the Linux Foundation, the Free Software Foundation, the Electronic Frontier Foundation, the Open Source Initiative, and the Software Freedom Conservancy: the open source community needs your legal review on this! I don’t think I’m being too alarmist when I say that this is potentially a dangerous new precedent being set; it would be very helpful to have your lawyers offer their perspectives on this, even if they disagree with one another. We seem to be in some terrible new era of frankenlicenses, where the worst of proprietary licenses are bolted on to the goodwill created by open source licenses; we need your legal voices before these creatures destroy the village! NetBSD and LLVM NetBSD entering 2019 with more complete LLVM support I’m recently helping the NetBSD developers to improve the support for this operating system in various LLVM components. As you can read in my previous report, I’ve been focusing on fixing build and test failures for the purpose of improving the buildbot coverage. Previously, I’ve resolved test failures in LLVM, Clang, LLD, libunwind, openmp and partially libc++. During the remainder of the month, I’ve been working on the remaining libc++ test failures, improving the NetBSD clang driver and helping Kamil Rytarowski with compiler-rt. The process of upstreaming support to LLVM sanitizers has been finalized I’ve finished the process of upstreaming patches to LLVM sanitizers (almost 2000LOC of local code) and submitted to upstream new improvements for the NetBSD support. Today out of the box (in unpatched version) we have support for a variety of compiler-rt LLVM features: ASan (finds unauthorized memory access), UBSan (finds unspecified code semantics), TSan (finds threading bugs), MSan (finds uninitialized memory use), SafeStack (double stack hardening), Profile (code coverage), XRay (dynamic code tracing); while other ones such as Scudo (hardened allocator) or DFSan (generic data flow sanitizer) are not far away from completeness. The NetBSD support is no longer visibly lacking behind Linux in sanitizers, although there are still failing tests on NetBSD that are not observed on Linux. On the other hand there are features working on NetBSD that are not functional on Linux, like sanitizing programs during early initialization process of OS (this is caused by /proc dependency on Linux that is mounted by startup programs, while NetBSD relies on sysctl(3) interfaces that is always available). News Roundup Thoughts on FreeBSD 12.0 Playing with FreeBSD with past week I don’t feel as though there were any big surprises or changes in this release compared to FreeBSD 11. In typical FreeBSD fashion, progress tends to be evolutionary rather than revolutionary, and this release feels like a polished and improved incremental step forward. I like that the installer handles both UFS and ZFS guided partitioning now and in a friendly manner. In the past I had trouble getting FreeBSD’s boot menu to work with boot environments, but that has been fixed for this release. I like the security options in the installer too. These are not new, but I think worth mentioning. FreeBSD, unlike most Linux distributions, offers several low-level security options (like hiding other users’ processes and randomizing PIDs) and I like having these presented at install time. It’s harder for people to attack what they cannot see, or predict, and FreeBSD optionally makes these little adjustment for us. Something which stands out about FreeBSD, compared to most Linux distributions I run, is that FreeBSD rarely holds the user’s hand, but also rarely surprises the user. This means there is more reading to do up front and new users may struggle to get used to editing configuration files in a text editor. But FreeBSD rarely does anything unless told to do it. Updates rarely change the system’s behaviour, working technology rarely gets swapped out for something new, the system and its applications never crashed during my trial. Everything was rock solid. The operating system may seem like a minimal, blank slate to new users, but it’s wonderfully dependable and predictable in my experience. I probably wouldn’t recommend FreeBSD for desktop use. It’s close relative, GhostBSD, ships with a friendly desktop and does special work to make end user applications run smoothly. But for people who want to run servers, possible for years without change or issues, FreeBSD is a great option. It’s also an attractive choice, in my opinion, for people who like to build their system from the ground up, like you would with Debian’s server install or Arch Linux. Apart from the base tools and documentation, there is nothing on a FreeBSD system apart from what we put on it. FreeBSD 12.0 Performance Against Windows & Linux On An Intel Xeon Server Last week I posted benchmarks of Windows Server 2019 against various Linux distributions using a Tyan dual socket Intel Xeon server. In this article are some complementary results when adding in the performance of FreeBSD 11.2 against the new FreeBSD 12.0 stable release for this leading BSD operating system. As some fun benchmarks to end out 2018, here are the results of FreeBSD 11.2/12.0 (including an additional run when using GCC rather than Clang) up against Windows Server and several enterprise-ready Linux distributions. While FreeBSD 12.0 had picked up just one win of the Windows/Linux comparisons run, the FreeBSD performance is moving in the right direction. FreeBSD 12.0 was certainly faster than FreeBSD 11.2 on this dual Intel Xeon Scalable server based on a Tyan 1U platform. Meanwhile, to no surprise given the data last week, Clear Linux was by far the fastest out-of-the-box operating system tested. I did run some extra benchmarks on FreeBSD 11.2/12.0 with this hardware: in total I ran 120 benchmarks for these BSD tests. Of the 120 tests, there were just 15 cases where FreeBSD 11.2 was faster than 12.0. Seeing FreeBSD 12.0 faster than 11.2 nearly 90% of the time is an accomplishment and usually with other operating systems we see more of a mixed bag on new releases with not such solidly better performance. It was also great seeing the competitive performance out of FreeBSD when using the Clang compiler for the source-based tests compared to the GCC8 performance. Additional data available via this OpenBenchmarking.org result file. How NetBSD came to be shipped by Microsoft Google cache in case the site is down In 2000, Joe Britt, Matt Hershenson and Andy Rubin formed Danger Incorporated. Danger developed the world’s first recognizable smartphone, the Danger HipTop. T-Mobile sold the first HipTop under the brand name Sidekick in October of 2002. Danger had a well developed kernel that had been designed and built in house. The kernel came to be viewed as not a core intellectual property and Danger started a search for a replacement. For business reasons, mostly to do with legal concerns over the Gnu Public License, Danger rejected Linux and began to consider BSD Unix as a replacement for the kernel. In 2006 I was hired by Mike Chen, the manager of the kernel development group to investigate the feasibility of replacing the Danger kernel with a BSD kernel, to select the version of BSD to use, to develop a prototype and to develop the plan for adapting BSD to Danger’s requirements. NetBSD was easily the best choice among the BSD variations at the time because it had well developed cross development tools. It was easy to use a NetBSD desktop running an Intel release to cross compile a NetBSD kernel and runtime for a device running an ARM processor. (Those interested in mailing list archaeology might be amused to investigate NetBSD technical mailing list for mail from picovex, particularly from Bucky Katz at picovex.) We began product development on the specific prototype of the phone that would become the Sidekick LX2009 in 2007 and contracts for the phone were written with T-Mobile. We were about half way through the two year development cycle when Microsoft purchased Danger in 2008. Microsoft would have preferred to ship the Sidekick running Windows/CE rather than NetBSD, but a schedule analysis performed by me, and another by an independent outside contractor, indicated that doing so would result in unacceptable delay. Beastie Bits Unleashed 1.2 Released 35th CCC - Taming the Chaos: Can we build systems that actually work? Potholes to avoid when migrating to IPv6 XScreenSaver 5.42 SSH Examples and Tunnels Help request - mbuf(9) - request for comment NSA to release free Reverse Engineering Tool Running FreeBSD on a Raspberry Pi3 using a custom image created with crochet and poudriere Feedback/Questions Dries - Lets talk a bit about VIMAGE jails ohb - Question About ZFS Root Dataset Micah - Active-Active NAS Sync recommendations Send questions, comments, show ideas/topics, or stories you want mentioned on the show to feedback@bsdnow.tv

In this episode of the ARCHITECHT Show, Apache Kafka co-creator (and Confluent co-founder) Jay Kreps returns to talk about a wide range of topics, including an uptick in Kafka alternatives both open source and commercial. Among a range of other things, Kreps also shares his thoughts on "big data" IPOs, what type of open source project makes a good business, and why enterprise IT is becoming a driving force in software innovation. This episode is sponsored by Datadog and MongoDB.

The Intelligent Edge is where the next revolution in innovation will happen, and it’s key to note that this is a data-driven trend. This week on STACK That, Jay Kreps, CEO & Co-Founder of Confluent, joins us to talk about autonomous driving, how data is changing IT and the security implications that come with Intelligent Edge computing.

So, after far too long a hiatus, we’re back on the Magpie Talkshow for a one-off episode where I interview Kafka creator and Confluent CEO Jay Kreps. I’ve been doing a small amount of work with Confluent recently, and through this I got the chance to meet Jay, and I thought he’d make a great guest for the show. So in this episode we’re going to learn about Jay’s own journey in the tech industry, as well as diving into the mindset behind Kafka and where you might want to use it. There are a couple of firsts in this episode. Firstly, it was recorded remotely via video conferencing - I think the audio quality is pretty good, largely thanks to the use of zencaster. I did however have to do more editing than usual but I’m pretty happy with how it turned out. Secondly We’re also going to be sharing a video of our chat over on confluent's website, and I’ll update this post with a link once it’s available. I do have to apologise for the sporadic nature of the episodes I’m putting out but as is often the case, life get’s in the way. In between our last episode and this one I setup my own company, and left australia for London, where I am currently based. I still plan to publish the occasional episode from time to time, so please do stay subscribed to the feed. Hopefully if things settle down a bit I may get back to a more regular posting schedule! Jay and I talked about a number of things on the podcast, but the main one I wanted to highlight is previous guest Ben Stopford’s really interesting posts on using Kafka for sharing data between microservices. There are some fascinating ideas there which I think can solve problems many of us face when creating finer-grained distributed systems. You can find Ben's posts here: https://www.confluent.io/blog/author/ben/. Anyway, I hope you enjoy the show!

308: This is the first episode of our “What is?” series, where we tackle topics of rising importance in technology and business, more generally speaking. We will tackle, “What is artificial intelligence?,” “What is Blockchain?,” “What is robotics?,” “What is 3d printing?,” and the like. Today, my question is: “What is microservices?” To answer that question, I speak with a Matt Miller, a Partner at Sequoia Capital and Jay Kreps, the CEO of Confluent.

In this episode of the ARCHITECHT Show, Derrick Harris speaks with Apache Kafka creator and Confluent co-founder Jay Kreps about a wide range of topics including, obviously, Kafka and Confluent. Kreps also tackles digital transformation and real-time data in enterprises; Microsoft's LinkedIn acquisition; the importance of network infrastructure in microservices and data-centric environments; the limitations of big data frameworks; and more. In the news segment, Harris and co-host Barb Darrow (Fortune) cover VMware selling its cloud business, Cloudera going public, and the promise and potential perils of AI in medicine. Also, the Boston Red Sox being on pace to go 162-0.  

Kafka Streams is a library for building streaming applications that transform input Kafka topics into output Kafka topics. In a time when there are numerous streaming frameworks already out there, why do we need yet another? To quote today’s guest Jay Kreps “the gap we see Kafka Streams filling is less the analytics-focused domain these The post Kafka Streams with Jay Kreps appeared first on Software Engineering Daily.

Jay Kreps talks about the open source data store Project Voldemort. Voldemort is a distributed key-value store used by LinkedIn and other high-traffic web sites to overcome the inherent scalability limitations of a relational database. The conversation delves into the workings of a Voldemort cluster, the type of consistency guarantees that can be made in a distributed database, and the tradeoff between client and the server.

Jay Kreps talks about the open source data store Project Voldemort. Voldemort is a distributed key-value store used by LinkedIn and other high-traffic web sites to overcome the inherent scalability limitations of a relational database. The conversation delves into the workings of a Voldemort cluster, the type of consistency guarantees that can be made in a distributed database, and the tradeoff between client and the server.

Jay Kreps talks about the open source data store Project Voldemort. Voldemort is a distributed key-value store used by LinkedIn and other high-traffic web sites to overcome the inherent scalability limitations of a relational database. The conversation delves into the workings of a Voldemort cluster, the type of consistency guarantees that can be made in a distributed database, and the tradeoff between client and the server.