February 2020 Summaries

Rollbar has introduced a new Notifications API to facilitate the automation of custom notification rules for projects, especially benefiting customers transitioning to microservices. This API allows users to set up notification rules for multiple projects quickly, with integrations available for Slack and PagerDuty. For Slack, users need to create or select a channel and obtain a service account ID, linking it through API calls to receive notifications about new errors in production environments. Similarly, PagerDuty integration enables notifications for new incidents, with users needing to configure service integration keys. The API supports various triggers and filters to tailor notifications according to specific needs, such as alerting when new errors occur or monitoring error trends. Rollbar aims to expand its integration capabilities beyond Slack and PagerDuty, with email notifications as the next target, and invites user feedback to extend support to additional services.

Rollbar has strengthened its integration with GitHub to enhance error resolution by introducing features that provide more context around errors, thereby reducing the mean time to resolve them (MTTR). The integration includes the ability to view the exact line of code causing an error and the GitHub user avatar of the last person to edit it directly within the Rollbar UI, eliminating the need to switch between Rollbar and GitHub. This is facilitated by the new support for 'git blame', which allows developers to assign errors more effectively by understanding who last modified the code and accessing related pull requests and commits with ease. The tool encourages using 'git blame' for context and informed assignment rather than fault-finding, exemplified by a scenario where an error was traced back to receiving incorrect values from another part of the code rather than the line itself. This update aims to streamline debugging processes and is available to all users with the GitHub integration.

To effectively transition from a monolithic architecture to a microservices architecture, organizations must implement strategic changes at both the organizational and application levels. This includes establishing clear, measurable goals and fostering cross-functional teams that can independently design, build, and support services. The adoption of metrics-based performance tracking, such as KPIs, is crucial for managing microservices, as is the practice of starting small to minimize risks. Application-level changes involve optimizing the build process, detangling dependencies, and ensuring local development environments are efficient. Important practices include using trunk-based development for version control, implementing an anti-corruption layer to manage interactions between microservices and the monolith, and adopting infrastructure as code for consistent and scalable environments. Additionally, organizations should focus on observability to maintain insight into service performance and leverage tools like application performance monitoring and distributed tracing to troubleshoot issues effectively. By following these guidelines, organizations can create a robust framework for developing and deploying microservices, paving the way for a successful transformation from monolithic systems.