text stringlengths 0 2.02k |
|---|
[4487.88 --> 4488.84] Still early days. |
[4488.94 --> 4490.90] I mean, people are playing around with stuff. |
[4491.22 --> 4495.10] And, you know, generally, this is the same, very similar system to Node. |
[4495.10 --> 4500.08] And so if you make a chat server, I wouldn't call that out as particularly interesting, necessarily. |
[4500.46 --> 4508.06] I think the interesting bits are kind of around the tooling and how we can make these workflows much faster for people and simpler. |
[4508.50 --> 4512.50] But the actual applications built on top are very similar in the end. |
[4512.74 --> 4516.36] Let's say I'm sitting on an existing Node app, which is medium-sized. |
[4516.90 --> 4520.50] And it's running a business, but it's not like 50 million lines of code. |
[4520.88 --> 4521.94] What would a port take? |
[4522.00 --> 4523.04] Or what would a port look like? |
[4523.04 --> 4526.44] Relatively straightforward, or are there serious dragons there? |
[4527.04 --> 4532.46] If it's already using ES modules and TypeScript, it should be relatively straightforward. |
[4533.06 --> 4538.54] If it's common JS and kind of old-school-style Node stuff, it'll be a bigger undertaking. |
[4539.00 --> 4540.38] Thanks for sharing so much, man. |
[4540.40 --> 4541.86] This has been very enlightening. |
[4542.10 --> 4542.26] Yeah. |
[4542.38 --> 4544.74] I really enjoyed it, and I appreciate you coming on. |
[4545.02 --> 4545.20] Yeah. |
[4545.60 --> 4550.72] I appreciate you making time in your schedule to finally do the podcast with us after so many years. |
[4550.72 --> 4554.12] And I guess we've never really invited you either, but sorry. |
[4554.12 --> 4554.98] No wonder you ever came on. |
[4554.98 --> 4556.66] It's been hard to get a hold of for the last 11 years. |
[4557.20 --> 4559.98] But I'm glad you made time to show up here at the ChangeLog. |
[4560.02 --> 4560.72] We appreciate that. |
[4560.80 --> 4561.52] So thank you, Ryan. |
[4561.86 --> 4562.04] Yeah. |
[4562.10 --> 4562.76] Thanks for having me. |
[4565.14 --> 4565.74] All right. |
[4565.78 --> 4567.44] That's it for this episode of the ChangeLog. |
[4567.52 --> 4568.60] Thank you for tuning in. |
[4569.00 --> 4572.66] We have a bunch of podcasts for you at changelog.com. |
[4572.70 --> 4573.32] You should check out. |
[4573.56 --> 4574.58] Subscribe to the Master Feed. |
[4574.58 --> 4577.24] Get them all at changelog.com slash master. |
[4577.36 --> 4579.72] Get everything we ship in a single feed. |
[4580.12 --> 4584.10] And I want to personally invite you to join the community at changelog.com slash community. |
[4584.32 --> 4585.20] It's free to join. |
[4585.44 --> 4586.54] Come hang with us in Slack. |
[4586.76 --> 4588.94] There are no imposters, and everyone is welcome. |
[4589.36 --> 4592.40] Huge thanks again to our partners, Linode, Fastly, and LaunchDarkly. |
[4592.76 --> 4596.24] Also, thanks to Breakmaster Cylinder for making all of our awesome beats. |
[4596.62 --> 4597.74] That's it for this week. |
[4597.92 --> 4598.88] We'll see you next week. |
[4598.88 --> 4598.90] We'll see you next week. |
[4604.58 --> 4634.56] We'll see you next week. |
[4634.58 --> 4664.56] We'll see you next week. |
• Computing on the edge and the benefits of running logic close to users |
• Edge databases and the problem of centralized data storage |
• Fauna's solution to edge database latency and imperfections in operational databases |
• The goal of removing the concept of a database and making data access seamless and transparent |
• Fauna's approach to global and regional deployments, and ensuring data consistency and availability across regions |
• The technical implementation of Fauna's transactional algorithm and its use of the Calvin algorithm for multi-region strict serializability. |
• Calvin algorithm for distributed transactional consistency |
• Comparison to Spanner and other systems |
• Challenges to implementing Calvin, including marketing and industry skepticism |
• Fauna's approach to handling network partitions and achieving CAP compliance |
• Temporal database capabilities and versioned timestamping |
• The importance of data freshness and availability in real-time systems |
• The CAP theorem and its implications for distributed databases |
• The challenges of adapting legacy database systems to modern, cloud-based infrastructure |
• The need for operational transparency and resource management in cloud-based databases |
• The concept of databases as APIs and the benefits of web-like interfaces for accessing data |
• Challenges of trusting a cloud-based database service |
• Transparency and trust as a high burden for cloud operators |
• Differences between managed cloud solutions and self-operated infrastructure |
• Need for transparency in operations and maintenance |
• Transition from on-prem to API-driven infrastructure solutions |
• Technical challenges in implementing a novel database solution |
• Trust as a key factor in adopting a new database technology |
• Fauna's unique features and architecture |
• GraphQL and FQL query languages |
• Perfect use cases for Fauna's database solution |
• Fauna is designed for modern web applications, particularly SaaS, consumer-oriented apps, and blockchain-adjacent applications. |
• Fauna is not an analytics database, data warehouse, or cache, but rather a transactional database that prioritizes consistency. |
• Fauna aims to be a general-purpose operational data platform, similar to MySQL's role in the web 1.0 era. |
• The company's founders drew from their experiences at Twitter and other companies to create Fauna, which addresses common problems in data systems. |
• Fauna has a unique approach to database architecture, focusing on simplicity and ease of use, rather than trying to tackle every possible query pattern. |
• The company has received funding, including a series A and series B round, and has brought on a chairman, Bob Muglia. |
• Fauna's founders believe that the company's timing is fortunate, as the market is now more receptive to deep tech infrastructure software. |
• Eric Berg was brought on as the new CEO, allowing the co-founder to focus on technical problems. |
• Fauna's approach is to build a new interface for the "new stack" of applications, rather than replicating old interfaces. |
• Fauna is designed for new workloads and augmenting existing systems, not replacing them. |
• The company's model is to offer a "green field" approach, allowing customers to start fresh with Fauna, rather than trying to migrate from existing databases. |
• Fauna offers a free plan, with no fixed costs for new users and only paying for resources consumed. |
• The company prioritizes the interface over open-sourcing the codebase, as most customers don't want to modify the database implementation. |
• Fauna is designed for the typical company, not large enterprises that can build custom databases in-house. |
• Evaluating the benefits of open source vs. proprietary systems for business success |
• Replicating open source benefits with free trial, local development, and interface standardization |
• Shift in market trend from open source to proprietary systems with unique benefits |
• Prioritizing business goals over open source requirements for database development |
• Addressing customer needs and requirements for database growth and adoption |
• Accelerating execution to keep up with customer growth and expectations |
• Roadmap for future development, including maturity and resiliency features and query language standards |
• Encouraging developers to try Fauna with a free trial and local development options |
• Discussion of Fauna and its technical aspects |
• Mention of Dr. Abadi as a board member of Fauna |
• Linking to the show's blog post and Trust page |
• Wrapping up the conversation and thanking Evan for his time |
**Jerod Santo:** So we've had a lot of conversations recently around computing on the edge. I'm not talking about IoT or smartphones necessarily, but smart CDNs...? I don't know, you have your Lambda, you have your Netlify and Fastly functions, you have your Cloudflare workers... We have a lot of people trying to push ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.