Alibaba Cloud Software / SaaS Hong Kong (China)

DINQ

Marketing Personalization · Risk Management · System Migration

As global AI talent communities are growing rapidly, DINQ needed to support increasing real-time collaboration and high engagement while delivering a consistent user experience across international markets. From a technology standpoint, the platform had to handle traffic fluctuations caused by community activities and launches, while maintaining low-latency AI-driven matching at scale. Also, stable WebSocket connections across regions were essential to ensure fast iteration with reliable CI/CD pipelines.

API response latency < 200ms (P95)
CI/CD deployment time under 10 minutes

Reported impact

Business outcome

As DINQ continues its global expansion, the platform is focused on optimizing latency for users across China, the Asia-Pacific region, North America, and Europe. It aims to enable global acceleration for both static assets and dynamic APIs, as well as build multi-region disaster recovery to enhance platform availability. Alibaba Cloud will continue to support DINQ’s next phase of growth through scalable infrastructure, cloud-native services, and AI-ready solutions, enabling global expansion, performance optimization, and accelerated innovation.

  • Revenue Growth
  • Risk Reduction
  • Scalability
  • Speed to Market

Solution

DINQ used Alibaba Cloud to address As global AI talent communities are growing rapidly, DINQ needed to support increasing real-time collaboration and high engagement while delivering a consistent user experience across international markets. From a technology standpoint, the platform had to handle traffic fluctuations caused by community activities and launches, while maintaining low-latency AI-driven matching at scale. Also, stable WebSocket connections across regions were essential to ensure fast iteration with reliable CI/CD pipelines. DINQ is a next-generation career platform designed for the AI era. It serves AI researchers, engineers, founders, and creators by providing dynamic professional identity pages, precise talent matching, and collaboration-first networking. DINQ differentiates itself through AI-driven insights, real-time interaction, and a cloud-native architecture optimized for global scale.

Data flow

DINQ's workloads and source data are processed on Qwen, Container Service for Kubernetes (ACK) persist to ApsaraDB RDS for PostgreSQL and are delivered through Server Load Balancer (SLB), CDN.

Solution architecture

6 components · 5 layers
  1. Compute
    • Qwen Qwen LLM provides the core orchestration and analysis for the advisor matching and recommendation
  2. Storage
    • ApsaraDB RDS for PostgreSQL ApsaraDB RDS for PostgreSQL with the pgvector extension to support AI vector similarity search with millisecond-level response
  3. Serving
    • Server Load Balancer (SLB) Server Load Balancer (SLB) ensures high-availability entry points for API gateways and WebSocket
    • CDN Object Storage Service (OSS) with CDN for storing and globally distributing static assets such as avatars and
  4. Orchestration
    • Container Service for Kubernetes (ACK) Container Service for Kubernetes (ACK) hosting five core microservices, including Gateway, Server, Message, Discover, and Tool, with HPA scaling pods from 2 to 10 based on traffic
  5. Uncategorized
    • Object Storage Service (OSS) Object Storage Service (OSS) with CDN for storing and globally distributing static assets such as avatars and

Architecture clues

  • Cloud-native Kubernetes support
  • Container Service for Kubernetes (ACK) hosting five core microservices, including Gateway, Server, Message, Discover, and Tool, with HPA scaling pods from 2 to 10 based on traffic demand
  • Global infrastructure and CDN coverage
  • It aims to enable global acceleration for both static assets and dynamic APIs, as well as build multi-region disaster recovery to enhance platform availability
  • Primary customer region: Hong Kong (China)
  • Qwen LLM provides the core orchestration and analysis for the advisor matching and recommendation scenario

Evidence from the source

API response latency < 200ms (P95)
Also, stable WebSocket connections across regions were essential to ensure fast iteration with reliable CI/CD pipelines.
As global AI talent communities are growing rapidly, DINQ needed to support increasing real-time collaboration and high engagement while delivering a consistent user experience across international markets.
DINQ set clear objectives to achieve:
From a technology standpoint, the platform had to handle traffic fluctuations caused by community activities and launches, while maintaining low-latency AI-driven matching at scale.
Transparency Evidence & methodology 95/100 reference value · 79% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value95/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth20/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence79%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Alibaba Cloud

    DINQ customer story

    First-party
    https://www.alibabacloud.com/customers/dinq
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived Jan 15, 2026 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.

Related

Similar use cases

See all like this