Page MenuHomePhabricator

Growthbook: Scope work required to get to full producitonized integration
Open, MediumPublic

Description

In order to include the cost on integration in the build or buy decision T368163: [EPIC] FY 24/25 SDS 2.1.1 POC Integration tests of 3rd Party experimentation engine solutions , we need to create and compile the following information:

  • Initial Assessment:
    • Review existing documentation on the third-party system
    • Identify key stakeholders and points of contact
    • Determine the primary goals and requirements of the integration
  • Technical Analysis:
    • Analyze the third-party API or integration methods
    • Identify data exchange formats and protocols
    • Assess security requirements and authentication methods
    • Evaluate potential impact on existing systems and infrastructure
  • Architecture Planning:
    • Design the high-level architecture for the integration
    • Identify necessary components and services
    • Plan for scalability and performance requirements
    • Determine data storage and caching needs
  • Set of diagrams:
    • Architecture diagram of the components and their interfaces, what currently exists, what would need to be built, and the specific touch points with the 3rd party system.
      • Component descriptions of each major component, the role of each component in the system, and the technologies or frameworks used
    • Data flow diagram that describes in detail how data moves through the integrated system.
    • Security architecture overview that describes security measures for data in transit and at rest, authentication and authorization mechanisms, and compliance with security standards
  • Scalability & performance
    • Identify potential bottlenecks
    • Strategy for handling increased load
  • Error handling and resilience strategy
    • Approach for handling failures in the integration
    • Monitoring and logging plan
  • Deployment plan
  • Summary of the tech stack with justification of choices
  • Assumptions and constraints that influence the architecture
  • Development Planning:
    • Break down the integration into manageable tasks
    • Estimate time and resources required for each task
    • Identify potential risks and mitigation strategies
    • Plan for necessary testing at each stage of development
    • Describe a phased approach that includes the dependencies between different components
  • Maintenance plan

Event Timeline

VirginiaPoundstone renamed this task from Scope work required to get Growthbook to full producitonized integration to Growthbook: Scope work required to get to full producitonized integration.Aug 15 2024, 8:06 PM
VirginiaPoundstone created this task.
VirginiaPoundstone raised the priority of this task from Medium to High.Aug 30 2024, 3:47 PM
VirginiaPoundstone lowered the priority of this task from High to Medium.Sep 11 2024, 9:50 PM

Preliminary documentation: https://docs.google.com/document/d/1NorKzBiQyz2nXCUUkGqdFP8SfPD0bzBMdfPO183dqNY/edit

Next steps are to flesh this out as an engineering team into a more complete plan. We have a lot of good information from POC, but we will still need to go through a design phase that will lead us to an implementation plan.

Think more about how instruments are not native to GrowthBook.

TODO
Break this work into separate tasks
Conduct Co-working sessions (Data Products and Data Platform SRE)
Consult with affected teams (MW, Search, traffic)

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy