June 2023 Summaries

Billing systems play a crucial role at the core of businesses, managing customer payments by calculating due amounts based on various factors such as usage, selected plans, and discounts. These systems must be versatile enough to handle diverse business models, from subscription-based services to transaction-based billing. When choosing a billing system, businesses should consider their current and future pricing structures, ensuring the system can scale and adapt to complex pricing models. Real-time capabilities are essential for certain industries, particularly those offering compute or storage services, as they require precise and immediate usage measurement. Companies must also assess whether their billing solution can support both self-serve and sales-led customer approaches, ensuring flexibility in billing plans. Industry-specific features, transparency, security, and the potential for vendor lock-in are critical considerations when selecting a billing system, especially for companies operating in regulated sectors. Understanding the long-term financial implications of vendor pricing models is essential to avoid significant impacts on profit margins as the company grows.

Object-Relational Mappings (ORMs) are often criticized for being inefficient and breaking software design principles like the Single Responsibility Principle (SRP) and Separation of Concerns (SOC), yet these criticisms are considered exaggerated by the author. ORMs are not inherently bad; they are simply abstractions that can lead to performance hits and decreased visibility if misused. The primary issues with ORMs include the N+1 query problem, where multiple roundtrips to the database occur, and challenges with visibility and error translation, especially when unexpected results require inspection of the SQL queries generated. Despite these drawbacks, ORMs can be nearly as efficient as raw SQL when used correctly and offer features that can mitigate common issues like N+1 scenarios. The author's experience with Active Record prompted a reevaluation of ORM usage, noting that developers often rely too heavily on host language logic instead of utilizing ORM features to optimize queries, and suggesting that executing raw SQL queries within an ORM can sometimes be beneficial for debugging or improving performance.