text stringlengths 0 1.17k |
|---|
[2817.66 --> 2822.58] see where it goes um you you mentioned this before but what is the twitter for mean js that people can |
[2822.58 --> 2830.74] follow uh it's mean js org the website is mean js dot org um we're mean js on facebook and github |
[2830.74 --> 2836.02] um we hope twitter would give us the mean js name because it's abandoned for some reason |
[2836.02 --> 2844.94] uh but for now it's mean js org um awesome yeah well we'll be back next week with another show uh sorry |
[2844.94 --> 2851.26] that we have been absent a little bit i've been starting a new uh a new job and so it's been kind |
[2851.26 --> 2856.50] hectic so uh for our listeners we will be back next week and we'll be uh weekly from here on out so |
[2856.50 --> 2861.46] until next week let's say goodbye goodbye thank you guys thanks a lot guys |
[2881.26 --> 2888.64] uh |
• Introduction to the Changelog podcast and its hosts |
• Digital Ocean announces milestone of 1 millionth droplet, with a $10,000 hosting credit giveaway |
• Aaron Hammer, Node.js lead architect at Walmart, joins the show to discuss Walmart's adoption of Node.js for its mobile services |
• Walmart's decision to switch to Node.js was made to modernize its infrastructure and build a new orchestration layer |
• Node.js was chosen for its ability to abstract complex backend systems and provide a uniform API to mobile clients |
• Challenges and resistance encountered while introducing a new technology in a large organization like Walmart |
• Issues with running Node on Walmart's Solaris operating system |
• Obtaining Linux boxes or SmartOS to run Node |
• Challenges with change control in Walmart's large data centers |
• Deploying Node as a proxy strategy to handle mobile traffic |
• Experiencing a memory leak issue with Node |
• The Node process being idle during Black Friday with low CPU usage |
• The team's relief and boredom with the uneventful performance of Node |
• The company was concerned about the scalability of Node.js, fearing it would become a bottleneck |
• They performed tests and added extra capacity, resulting in a major success and proving the stack |
• The team was aware of the potential for a "Twitter-like" situation, where Node.js would be blamed for not scaling |
• The community rallied around the project, with many following the situation in real-time on Twitter |
• The incident was seen as a major milestone for the Node.js community, demonstrating its ability to handle large traffic and scaling issues |
• The team was able to address a memory leak issue, but only after releasing a daily update, making it difficult to verify the fix |
• The company was expecting up to 10x traffic increase, which would have required frequent server restarts if the memory leak was not fixed. |
• Memory leak in Node.js, first noticed in April, took 3 months to identify and solve |
• Initially, the team was dismissive and thought it was a different issue |
• A configuration change was made to double the number of HTTP client calls, which helped isolate the issue |
• The bug was found to be a missing handle scope in the C++ side of Node, causing a 4-byte leak per HTTP request |
• The issue was fixed 2 weeks before the problem was actually solved, but a build issue delayed the update |
• Stress testing the issue proved difficult, requiring a specific script to reproduce it |
• The origin of Happy, a web framework, started as a collaborative list-making tool at Yahoo, built using Express, Node.js, and Connect. |
• Express was deemed insufficient for large-scale development, leading to the creation of Happy as an Express layer with additional functionality. |
• Happy's development was influenced by PayPal's Kraken framework, which also built upon Express. |
• The team faced limitations with Express and later Director, leading to the decision to develop their own internal router. |
• As Happy grew, the team shifted from relying on public open-source modules to forking and modifying them to meet their needs. |
• The team feels more confident in their ability to develop and maintain their own internal solutions. |
• Plug-in architecture for large teams to avoid routing table coordination |
• Spunko, a modular approach to dealing with Happy, inspired by Ren & Stimpy |
• Spunko, a new organization name to reorganize GitHub projects |
• Happy, a heavy framework with an opinionated, hands-on approach to HTTP/ web servers |
• Modular approach, allowing users to mix and match modules for different configurations |
• Expansion/contraction pattern of development, adding features to the core and then abstracting them out |
• Avoiding middleware hell with a plugin system, describing relationships between plugins |
• Discouraging new Happy-specific plugins, encouraging users to use existing plugins instead |
• Difference between a regular node module and a plugin for a specific framework |
• Importance of a plugin's interaction with the framework and its functionality |
• When to use a plugin vs a regular module |
• Fragmentation in the community due to creating multiple plugins for similar functionality |
• Node and npm's ease of use for managing modules |
• Requirements for creating a happy plugin (exporting a single function called register) |
• Discussion about breaking changes in a software project, specifically Happy, a web framework. |
• Explanation of how the project uses GitHub for issue tracking and project management. |
• Description of how breaking changes are communicated and handled in the project. |
• Mention of several companies using Happy in production, including Mozilla, Mastercard, and Walmart. |
• Discussion of the adoption and usage of Happy in various industries and applications. |
• The challenges of adopting Express.js and the tendency to add layers on top of it |
• Using Happy as a proxy strategy for migration to a new stack |
• Walmart's use of Happy in various teams and its scalability |
• Expanding Happy's use beyond mobile apps to other areas of the company |
• Walmart's e-commerce platform's adoption of new APIs and technologies |
• The company's expansion to other countries and the need to scale engineering processes |
• A sponsor, Top Towel, offering a platform to connect freelance developers with companies |
• The host mentions a technical interview process with top engineers and a test project to screen candidates. |
• The conversation shifts to the open-source community and deployment tools, with the host commending Happy for not competing with Express by saying it's better. |
• The guest discusses the advantages and disadvantages of Happy compared to Express, highlighting Happy's revenue and use cases, but also expressing a desire to compete fairly. |
• The guest emphasizes the importance of not speaking negatively about competitors and instead focusing on the strengths of Happy. |
• The host asks the guest to recommend a project or module that needs contributions from the open-source community. |
• The guest encourages listeners to try Happy, report any issues, and contribute to the project. |
• The guest reveals that if not working on Happy, they would be a full-time farmer. |
• Farmer wins jackpot and discusses potential plans, including continuing to farm for another five years |
• Interviewee prefers farming to tech industry, also enjoys woodworking and beekeeping |
• Discusses a previous talk about food for engineers, which had an "insane" production budget |
• Childhood engineering hero is Roberta Williams, creator of King's Quest games |
• Observations on the tech industry, including the rarity of developers who played old school games as kids |
• Conversation about the importance of developers having a personal interest outside of work, such as gaming or craftsmanship |
• No conversation or information is provided. |
[0.00 --> 14.40] welcome back everyone this is the changelog and i'm your host adam stekowiak we're a member |
[14.40 --> 21.94] supportive blog podcast and weekly email covering what's fresh and what's new in open source check |
[21.94 --> 28.58] out the blog at the changelog.com our past shows at 5by5.tv slash changelog and subscribe to our |
[28.58 --> 33.22] weekly email it's called the changelog weekly we ship it on saturdays you don't want to miss it |
[33.22 --> 39.80] and you can subscribe at the changelog.com slash weekly this show is hosted by myself adam |
[39.80 --> 46.22] stekowiak and andrew thorpe now we recorded this show in particular before the new year didn't have |
[46.22 --> 50.82] time to publish it before the new year but at the tail end you'll hear andrew mention taking some |
[50.82 --> 57.54] time off that's already happened we missed you we're back we're excited it's 2014 and this is |
[57.54 --> 65.42] episode 116 and it's sponsored by digital ocean fresh books and top tile we'll tell you a bit |
[65.42 --> 69.72] more about fresh books and top tile later on the show but our our good friends over digital ocean |
[69.72 --> 75.10] have some cool stuff happening they're nearing their millionth droplet and to celebrate they're |
[75.10 --> 81.30] giving away ten thousand dollars in hosting credit ten thousand dollars in hosting credit you heard it |
[81.30 --> 88.82] right to a lucky user who hits this milestone and there are three ways you can qualify number one |
[88.82 --> 94.38] you got to be the user who spins up the millionth droplet so that's that's number one number two you've |
[94.38 --> 100.88] got to include your twitter handle in the droplets host name so when you create the droplet you got to |
[100.88 --> 107.42] put your twitter handle in that host name and number three you have to tweet the digital ocean with the |
[107.42 --> 115.10] hashtag millionth droplet for example i'm going to be the millionth droplet on digital ocean that would |
[115.10 --> 121.58] qualify you if you do all three things you're in it so try the ocean today for free using our promo |
[121.58 --> 129.26] code changelog sent me that's changelog sent me that'll get you a ten dollar hosting credit as well as |
[129.26 --> 135.54] as well as a chance i guess to potentially be the moon's droplet so good luck to you but head to |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.