December 2019 Summaries

Rollbar experienced a transformative year, marked by significant platform modernization and expansion efforts to stay ahead in the competitive Error Monitoring space. The engineering team doubled in size to address the growing demand, focusing on improving real-time error processing and reducing noise through enhanced classification and automatic merging capabilities. A strategic acquisition of SameBug strengthened Rollbar's AI and classification expertise, leading to innovations like the Apache Spark integration, which improved error management. The company transitioned to a microservices architecture, leveraging Kubernetes and Google Cloud for scalability, and revamped its user experience with a focus on multi-project functionality and a single-page app approach. These developments were supported by a new Docker-based development environment, enhancing speed and onboarding efficiency. The shift to distributed service ownership empowered engineers to take full responsibility for platform health, with all teams now on-call. Looking ahead, Rollbar anticipates new challenges and opportunities, driven by a workforce that will predominantly consist of recent hires, reflecting a dynamic phase of growth and innovation.

Encountering JavaScript TypeErrors is a common issue for developers, especially after recent deployments, due to the diversity of situations they encompass and the variety of exception messages across different browsers and languages. These errors often arise when operations are attempted on values of unexpected types and can manifest during code refactoring when a function used elsewhere becomes problematic. Two prevalent cases include trying to access properties of undefined or null references and calling non-existent object methods or properties, with error messages varying by browser and language. In production environments, identifying and resolving these errors can be challenging due to the noise created by diverse visitor browsers. Utilizing tools like Rollbar can help manage this complexity by effectively grouping similar errors across different languages and browsers, reducing noise, and providing a clear, actionable view of errors to facilitate quick resolution.

Effective error handling is crucial for enhancing user experience and application robustness in Angular, with tools like HttpInterceptor and Rollbar offering significant advantages. Traditional methods like using ErrorHandler in Angular can track error logs but are limited, particularly for server and network-related errors. HttpClient allows for handling specific errors within services, but this approach can lead to code redundancy and maintenance challenges. HttpInterceptor, introduced in Angular 4.3.1, provides a centralized solution for intercepting HTTP requests and responses, enabling consistent error handling and retries across all application services. Integrating with Rollbar further enhances error management by offering real-time tracking, detailed analytics, and context through telemetry, which helps developers quickly diagnose and resolve issues. Rollbar's seamless integration with Angular ensures that all errors are tracked globally, providing both developers and users with informative error messages and reducing the likelihood of unresolved issues impacting user experience.

Rollbar has introduced a new user experience tailored to the increasing prevalence of microservice architectures and continuous delivery practices, offering users the ability to monitor errors and debug across multiple projects more efficiently. The new UX includes a unified tool for viewing all microservices, real-time alerts on errors, and a consistent workspace with advanced filtering options for faster debugging. Users can track deployed code versions and correlate data across services using Rollbar Query Language, now enhanced with visual graphs for trend analysis. Feedback from customers like Greenhouse highlights Rollbar's role in smoothing release workflows by catching issues early. The new UX is now accessible to all customers, with additional resources and information available for those migrating to microservices or exploring advanced features.

Transitioning from a monolithic architecture to a microservices architecture is a complex, long-term process requiring careful consideration of an organization's readiness and the potential benefits it can bring. Key aspects to evaluate include team autonomy, time to market, system reliability, team scalability, and technological flexibility. Organizations need to assess their cultural readiness, development and operations maturity, automation practices, and application monitoring capabilities. Challenges such as distributed communication, system latency, distributed transactions, and debugging across multiple services must be addressed. The transition is fundamentally about embracing change and ensuring that the company can sustain focus and resource allocation over the years it may take to complete. Understanding these elements and preparing for them is crucial for a successful transformation to a microservices architecture.