DOCSEARCHbyAlgolia
Submit Docs

Hackney Council Product and Technical Playbook

website·Indexed 39 days ago

https://playbook.hackney.gov.uk

A comprehensive guide for developers and product managers at Hackney Council. It covers the product development lifecycle, including product strategy, roadmaps, and backlogs, as well as technical standards for hosting, API development, Micro Frontends, Event Driven Architecture, and GitHub workflows.

Tokens
70.2K
Snippets
164
Records
538
Agent score
62%

What's inside Hackney Playbook

  1. Overview of the Organisations API

    The Organisations API provides a centralized data source for managing corporate accounts and organization data. Its primary purpose is to distinguish corporate accounts from individual person records, ensuring data consistency across services and eliminating silos in asset information collection. It is used to determine if a tenancy is person-based or business-based and to manage details such as Certificates of Incorporation, directors, and registered office locations.

  2. Overview of the Notes Microservice

    The Notes microservice provides a centralized, reusable API for creating and retrieving activities (notes) against various entities. It aims to eliminate data silos and duplication by serving as a single source of truth for note-related information across different domains such as Housing, Finance, and Repairs. The service supports a classification of 'public' notes for resident transparency and 'private' notes for restricted officer access.

  3. Overview of the Core-Asset API

    The Core-Asset API provides a single, centralized data source for all core asset data across the council, including properties and facilities (e.g., lifts, booster pumps). It is designed as a reusable microservice to eliminate data silos and provide a normalized view of assets across different domains such as Housing, Finance, and Repairs. While based on HACT standards, the API employs a flexible approach to better meet specific user needs.

  5. Overview of the Processes API workflow engine

    The Processes API is designed to manage housing workflows, enabling staff to initiate new processes, upload documents, capture form data, and assign tasks. The engine tracks the current state of a process, maintains a history of previous states, and defines permitted triggers for progressing the workflow to the next step.

  6. Overview of the Notifications API

    The Notifications API is a centralized microservice designed to manage and send notifications to users (tenants, officers, etc.) when relevant events occur. It provides a unified data source to avoid duplication and reduce development costs across different service domains. Supported channels include email, text messages (SMS), on-screen notifications (e.g., badges, pop-ups), and physical letters.

  7. Overview of the API authenticator

    The API authenticator is a centralized Lambda function deployed once per environment that serves as a cross-account Lambda authorizer for multiple APIs. It validates access by decoding Hackney Google tokens and checking if the user belongs to a Google group authorized for the specific API and environment. The mapping between APIs and authorized Google groups is stored in a DynamoDB table.

  8. Overview of the Hackney Product Playbook

    The Hackney Product Playbook provides guidance, examples, and templates for Product Management at Hackney. Its primary goal is to develop digital products that reduce the time and effort residents spend accessing services and to increase confidence in the council. It is intended for product managers, product teams, and Hackney colleagues seeking transparency regarding product development and strategic goals.

  9. Overview of the Hackney Council Micro Frontend Playbook

    The Micro Frontend Playbook provides repeatable guidelines for teams at Hackney Council to implement and contribute to when building web interfaces. The primary goal is to establish consistent frontend standards across the platform to avoid duplicating effort across different programs and streams. To solve existing frontend challenges, the council advocates for the use of Micro Frontends for building modern web interfaces.

  10. Overview of the Hackney API Playbook

    The Hackney API Playbook serves as a standardized governance framework for the development, support, and maintenance of APIs within Hackney's cloud-based architecture. It is designed to ensure consistency across internal and external development teams, simplify the onboarding of new developers and agency partners, and provide a set of adopted best practices to reduce maintenance challenges associated with inconsistent implementations.

  11. Overview of the Accounts API

    The Accounts API provides a centralized, decoupled microservice for managing account-related data. In this context, an 'account' is defined as a financial record that links a user (person or organization) to a specific service. It is designed to support housing streams and other council projects to enable citizen-centric self-service capabilities and consistent data management across services.

  12. Overview of AWS X-Ray for distributed application debugging

    AWS X-Ray is a managed service used to debug and analyze distributed applications. It provides an end-to-end request view, allowing developers to identify root causes of issues, discover performance bottlenecks, and analyze high-latency requests in real-time. It uses a Service Map to visualize dependencies and calls between services.

    Key visualization types include:

    • Service Maps: An end-to-end visual representation of all dependencies for an application serving requests.
    • Trace Maps: An end-to-end visual representation for a single specific request.