Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
By, Will Leinweber Heroku started out as single, large Rails app. Over the years it split into countless (really ... I have no idea how many) smaller services. Some of these splits were very successful, and others not so much. Pliny—an API framework built on Sinatra—distills everything we've learned the hard way about building production APIs in Ruby. Pliny takes care of mundane, mechanical decisions like logging and configuration, but also service problems including API versioning and json schemas. Most importantly, it comes with patterns to manage complexity as the service grows. It also shares its name with fantastic beer from Russian River. In this session, we'll explore what's important as you split into services, but also what can go terribly wrong. You'll learn everything you need to get started yourself with Pliny by looking at an open-source microservice built with it. Help us caption & translate this video! http://amara.org/v/GUQJ/
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
The video titled 'Better APIs with Pliny' features Will Leinweber discussing the development of APIs through the lens of the Pliny framework, which is built on Sinatra and beneficial for Ruby developers. The presentation is structured to first clarify the significance of splitting applications into services and the considerations that come with it, followed by a deep dive into the features and advantages of using Pliny. Key points discussed include: - **Importance of Services**: Pliny allows teams to focus on specific functionalities, improving maintainability and enabling independent scaling. It addresses challenges that arise as teams grow, reflecting Conway's Law which states systems mirror organizational structures. - **Caution Against Microservices**: Although microservices have their benefits, Leinweber highlights the potential costs and complexity they introduce, such as the loss of shared databases, increased overhead in API interactions, and disparate deployment processes. - **API Design Principles**: The presentation introduces the HTTP API Design Guide, emphasizing best practices like using e-tags, consistent date formatting, and minimizing path nesting. These principles aim to enhance the efficiency and usability of APIs. - **Introduction to Pliny**: Pliny is outlined as a solution to manage API complexity, enabling better logging, configuration management, and effective serialization. Features like support for JSON schemas and elegant versioning make it particularly suitable for dynamic applications. - **Use Cases**: Leinweber references practical examples such as 'Telex', an open-source project that centralizes notifications, showcasing how Pliny facilitates simpler code management and application interaction. - **Encapsulation and Mediators**: He stresses the importance of keeping controllers clean through mediators, simplifying testing and understanding of the application structure. - **Community and Collaboration**: The speaker encourages developers to engage with the open-source community surrounding Pliny, promoting collaborative improvement of the tools. Overall, attendees are encouraged to leverage Pliny for their API projects, emphasizing its philosophy of reducing complexity and enhancing team collaboration, thus leading to better API development.
Suggest modifications
Cancel
