acshame

acshame

1. 14:51 · Aug 7, 2025 · Thu

   "App port from web tier",
   rule_action: "allow",
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   // Database Security Group Rules
   CREATE (rule5:SecurityRule {
   id: "rule-db-from-app",
   direction: "inbound",
   protocol: "tcp",
   port_range: "3306",
   source_type: "security_group",
   source: "sg-app67890",
   description: "MySQL from app tier",
   rule_action: "allow",
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   // 8.6 VPC Endpoints 建模
   CREATE (endpoint_s3:VPCEndpoint {
   id: "vpce-s3-12345",
   name: "s3-gateway-endpoint",
   associations_vpc: "vpc-12345678",
   associations_subnet: null, // Gateway endpoint不关联subnet
   type: "Gateway",
   service: "com.amazonaws.cn-north-1.s3",
   route_table_ids: ["rtb-private-456"],
   tag: {
   service_type: "storage",
   environment: "production"
   },
   status: "available",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   CREATE (endpoint_ec2:VPCEndpoint {
   id: "vpce-ec2-67890",
   name: "ec2-interface-endpoint",
   associations_vpc: "vpc-12345678",
   associations_subnet: ["subnet-def67890"], // Interface endpoint关联subnet
   type: "Interface",
   service: "com.amazonaws.cn-north-1.ec2",
   network_interface_ids: ["eni-endpoint-123"],
   security_group_ids: ["sg-endpoint-456"],
   tag: {
   service_type: "compute",
   environment: "production"
   },
   status: "available",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   // ==========================================
   // 9. 建立高级网络组件关系
   // ==========================================
   
   // EIP与多资源的多态关联（使用泛型关系）
   MATCH (eip1:EIP {allocation_id: "eipalloc-12345abc"}), (nat1:NatGateway {id: "nat-12345abc"})
   CREATE (eip1)-[:ASSOCIATED_WITH {resource_type: "nat_gateway"}]->(nat1),
   (nat1)-[:USES_EIP]->(eip1);
   
   MATCH (eip1:EIP {allocation_id: "eipalloc-12345abc"}), (eni1:NetworkInterface {id: "eni-12345abc"})
   CREATE (eip1)-[:ATTACHED_TO_ENI]->(eni1),
   (eni1)-[:HAS_EIP]->(eip1);
   
   // 预留EC2与EIP关联（EC2建模完成后）
   // MATCH (eip2:EIP {allocation_id: "eipalloc-67890xyz"}), (ec2:EC2Instance {id: "i-1234567890abcdef0"})
   // CREATE (eip2)-[:ASSOCIATED_WITH {resource_type: "ec2_instance"}]->(ec2);
   
   // NAT Gateway关系
   MATCH (nat1:NatGateway {id: "nat-12345abc"}), (vpc1:VPC {id: "vpc-12345678"})
   CREATE (nat1)-[:BELONGS_TO_VPC]->(vpc1),
   (vpc1)-[:CONTAINS_NAT_GATEWAY]->(nat1);
   
   MATCH (nat1:NatGateway {id: "nat-12345abc"}), (subnet1:Subnet {id: "subnet-abc12345"})
   CREATE (nat1)-[:DEPLOYED_IN_SUBNET]->(subnet1),
   (subnet1)-[:HOSTS_NAT_GATEWAY]->(nat1);
   
   MATCH (nat1:NatGateway {id: "nat-12345abc"}), (eni1:NetworkInterface {id: "eni-12345abc"})
   CREATE (nat1)-[:USES_NETWORK_INTERFACE]->(eni1),
   (eni1)-[:ATTACHED_TO_NAT_GATEWAY]->(nat1);
   
   // Network Interface关系
   MATCH (eni1:NetworkInterface {id: "eni-12345abc"}), (subnet1:Subnet {id: "subnet-abc12345"})
   CREATE (eni1)-[:DEPLOYED_IN_SUBNET]->(subnet1),
   (subnet1)-[:HOSTS_NETWORK_INTERFACE]->(eni1);
   
   MATCH (eni2:NetworkInterface {id: "eni-67890def"}), (subnet1:Subnet {id: "subnet-abc12345"})
   CREATE (eni2)-[:DEPLOYED_IN_SUBNET]->(subnet1),
   (subnet1)-[:HOSTS_NETWORK_INTERFACE]->(eni2);
   
   // Security Group关系
   MATCH (sg_web:SecurityGroup {id: "sg-web12345"}), (vpc1:VPC {id: "vpc-12345678"})
   CREATE (sg_web)-[:BELONGS_TO_VPC]->(vpc1),
   (vpc1)-[:CONTAINS_SECURITY_GROUP]->(sg_web);
   
   MATCH (sg_app:SecurityGroup {id: "sg-app67890"}), (vpc1:VPC {id: "vpc-12345678"})
   CREATE (sg_app)-[:BELONGS_TO_VPC]->(vpc1),
   (vpc1)-[:CONTAINS_SECURITY_GROUP]->(sg_app);
   
   MATCH (sg_db:SecurityGroup {id: "sg-db11111"}), (vpc1:VPC {id: "vpc-12345678"})
   CREATE (sg_db)-[:BELONGS_TO_VPC]->(vpc1),
   (vpc1)-[:CONTAINS_SECURITY_GROUP]->(sg_db);
   
   // Security Group Rules关系
   MATCH (sg_web:SecurityGroup {id: "sg-web12345"}), (rule1:SecurityRule {id: "rule-web-http-in"})
   CREATE (sg_web)-[:HAS_RULE]->(rule1),
   (rule1)-[:APPLIES_TO_SG]->(sg_web);
   
   MATCH (sg_web:SecurityGroup {id: "sg-web12345"}), (rule2:SecurityRule {id: "rule-web-https-in"})
   CREATE (sg

2. 14:51 · Aug 7, 2025 · Thu

   .2 Network Interface (ENI) 建模
   CREATE (eni1:NetworkInterface {
   id: "eni-12345abc",
   name: "nat-gateway-eni-1a",
   type: "nat_gateway",
   private_ip: "10.0.1.100",
   private_dns: "ip-10-0-1-100.ec2.internal",
   subnet_id: "subnet-abc12345",
   vpc_id: "vpc-12345678",
   az: "cn-north-1a",
   security_groups: ["sg-nat12345"],
   source_dest_check: false,
   tag: {
   attached_resource: "nat-gateway",
   environment: "production"
   },
   status: "in-use",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   CREATE (eni2:NetworkInterface {
   id: "eni-67890def",
   name: "web-server-eni",
   type: "instance",
   private_ip: "10.0.1.50",
   private_dns: "ip-10-0-1-50.ec2.internal",
   subnet_id: "subnet-abc12345",
   vpc_id: "vpc-12345678",
   az: "cn-north-1a",
   security_groups: ["sg-web12345"],
   source_dest_check: true,
   tag: {
   attached_resource: "ec2_instance",
   environment: "production"
   },
   status: "in-use",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   // 8.3 NAT Gateway 建模
   CREATE (nat1:NatGateway {
   id: "nat-12345abc",
   name: "production-nat-1a",
   arn: "arn:aws:ec2:cn-north-1:123456789012:natgateway/nat-12345abc",
   public_ip: "54.123.45.67",
   private_ip: "10.0.1.100",
   associated_vpc: "vpc-12345678",
   associated_subnet: "subnet-abc12345",
   network_interface_id: "eni-12345abc",
   eip_allocation_id: "eipalloc-12345abc",
   tag: {
   environment: "production",
   purpose: "private_subnet_internet_access",
   tier: "networking"
   },
   status: "available",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   // 8.4 Security Group 建模
   CREATE (sg_web:SecurityGroup {
   id: "sg-web12345",
   name: "production-web-sg",
   description: "Security group for web servers",
   associated_vpc_id: "vpc-12345678",
   tag: {
   environment: "production",
   tier: "web",
   application: "frontend"
   },
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   CREATE (sg_app:SecurityGroup {
   id: "sg-app67890",
   name: "production-app-sg",
   description: "Security group for application servers",
   associated_vpc_id: "vpc-12345678",
   tag: {
   environment: "production",
   tier: "application",
   application: "backend"
   },
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   CREATE (sg_db:SecurityGroup {
   id: "sg-db11111",
   name: "production-db-sg",
   description: "Security group for database servers",
   associated_vpc_id: "vpc-12345678",
   tag: {
   environment: "production",
   tier: "database",
   application: "mysql"
   },
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   // 8.5 Security Rules 建模（独立节点）
   // Web Security Group Rules
   CREATE (rule1:SecurityRule {
   id: "rule-web-http-in",
   direction: "inbound",
   protocol: "tcp",
   port_range: "80",
   source_type: "cidr",
   source: "0.0.0.0/0",
   description: "HTTP from anywhere",
   rule_action: "allow",
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   CREATE (rule2:SecurityRule {
   id: "rule-web-https-in",
   direction: "inbound",
   protocol: "tcp",
   port_range: "443",
   source_type: "cidr",
   source: "0.0.0.0/0",
   description: "HTTPS from anywhere",
   rule_action: "allow",
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   CREATE (rule3:SecurityRule {
   id: "rule-web-all-out",
   direction: "outbound",
   protocol: "all",
   port_range: "all",
   source_type: "cidr",
   source: "0.0.0.0/0",
   description: "All outbound traffic",
   rule_action: "allow",
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   // App Security Group Rules
   CREATE (rule4:SecurityRule {
   id: "rule-app-from-web",
   direction: "inbound",
   protocol: "tcp",
   port_range: "8080",
   source_type: "security_group",
   source: "sg-web12345",
   description:

3. 14:51 · Aug 7, 2025 · Thu

   Re

4. 14:51 · Aug 7, 2025 · Thu

   cidr: "10.0.1.0/24",
   az: "cn-north-1a",
   arn: "arn:aws:ec2:cn-north-1:123456789012:subnet/subnet-abc12345",
   type: "public",
   available_ipv4_addresses: 248,
   auto_assign_public_ip: true,
   map_public_ip_on_launch: true,
   associated_acl: "acl-default-123",
   associated_route_table: "rtb-public-123",
   subnet_flow_logs: {
   enabled: true,
   log_destination: "s3://subnet-flow-logs-bucket"
   },
   tag: {
   tier: "web",
   environment: "production",
   subnet_type: "public"
   },
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   CREATE (subnet2:Subnet {
   id: "subnet-def67890",
   name: "production-app-subnet-1a",
   cidr: "10.0.2.0/24",
   az: "cn-north-1a",
   arn: "arn:aws:ec2:cn-north-1:123456789012:subnet/subnet-def67890",
   type: "private",
   available_ipv4_addresses: 245,
   auto_assign_public_ip: false,
   map_public_ip_on_launch: false,
   associated_acl: "acl-private-456",
   associated_route_table: "rtb-private-456",
   subnet_flow_logs: {
   enabled: true,
   log_destination: "s3://subnet-flow-logs-bucket"
   },
   tag: {
   tier: "application",
   environment: "production",
   subnet_type: "private"
   },
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   CREATE (subnet3:Subnet {
   id: "subnet-ghi13579",
   name: "production-db-subnet-1a",
   cidr: "10.0.3.0/24",
   az: "cn-north-1a",
   arn: "arn:aws:ec2:cn-north-1:123456789012:subnet/subnet-ghi13579",
   type: "private",
   available_ipv4_addresses: 250,
   auto_assign_public_ip: false,
   map_public_ip_on_launch: false,
   associated_acl: "acl-database-789",
   associated_route_table: "rtb-database-789",
   subnet_flow_logs: {
   enabled: false,
   log_destination: null
   },
   tag: {
   tier: "database",
   environment: "production",
   subnet_type: "private",
   encryption: "required"
   },
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   // 6.3 Internet Gateway 建模
   CREATE (igw1:InternetGateway {
   id: "igw-12345abc",
   name: "production-main-igw",
   associations_vpc: "vpc-12345678",
   tag: {
   environment: "production",
   purpose: "main-internet-gateway"
   },
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   // 6.4 Route Table 建模
   CREATE (rt_public:RouteTable {
   id: "rtb-public-123",
   name: "production-public-rt",
   associations_subnets: ["subnet-abc12345"],
   associations_vpc: "vpc-12345678",
   routes: [
   {
   destination: "10.0.0.0/16",
   target: "local",
   status: "active"
   },
   {
   destination: "0.0.0.0/0",
   target: "igw-12345abc",
   status: "active"
   }
   ],
   tag: {
   type: "public",
   environment: "production"
   },
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   CREATE (rt_private:RouteTable {
   id: "rtb-private-456",
   name: "production-private-rt",
   associations_subnets: ["subnet-def67890"],
   associations_vpc: "vpc-12345678",
   routes: [
   {
   destination: "10.0.0.0/16",
   target: "local",
   status: "active"
   },
   {
   destination: "0.0.0.0/0",
   target: "nat-gateway-123",
   status: "active"
   }
   ],
   tag: {
   type: "private",
   environment: "production"
   },
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   // ==========================================
   // 7. 建立网络资源关系（包含双向关系）
   // ==========================================
   
   // Account <-> VPC 关系
   MATCH (acc:Account {id: "123456789012"}), (vpc1:VPC {id: "vpc-12345678"})
   CREATE (acc)-[:CONTAINS_VPC]->(vpc1),
   (vpc1)-[:BELONGS_TO_ACCOUNT]->(acc);
   
   MATCH (acc:Account {id: "123456789012"}), (vpc2:VPC {id: "vpc-87654321"})
   CREATE (acc)-[:CONTAINS_VPC]->(vpc2),
   (vpc2)-[:BELONGS_TO_ACCOUNT]->(acc);
   
   //

5. 14:51 · Aug 7, 2025 · Thu

   -DC-Beta",
   power_redundancy: "N+1"
   },
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   CREATE (az3:AZ {
   id: "cn-north-1d",
   name: "Beijing Zone D",
   tag: {
   physical_location: "Beijing-DC-Delta",
   power_redundancy: "2N"
   },
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   // Ningxia AZs
   CREATE (az4:AZ {
   id: "cn-northwest-1a",
   name: "Ningxia Zone A",
   tag: {
   physical_location: "Ningxia-DC-Alpha",
   power_redundancy: "N+1"
   },
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   CREATE (az5:AZ {
   id: "cn-northwest-1b",
   name: "Ningxia Zone B",
   tag: {
   physical_location: "Ningxia-DC-Beta",
   power_redundancy: "N+1"
   },
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   CREATE (az6:AZ {
   id: "cn-northwest-1c",
   name: "Ningxia Zone C",
   tag: {
   physical_location: "Ningxia-DC-Gamma",
   power_redundancy: "2N"
   },
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   // ==========================================
   // 5. 建立基础层次关系
   // ==========================================
   
   // Account -> Region 关系
   MATCH (acc:Account {id: "123456789012"}), (r1:Region {id: "cn-north-1"})
   CREATE (acc)-[:CONTAINS_REGION]->(r1);
   
   MATCH (acc:Account {id: "123456789012"}), (r2:Region {id: "cn-northwest-1"})
   CREATE (acc)-[:CONTAINS_REGION]->(r2);
   
   // Region -> AZ 关系
   MATCH (r1:Region {id: "cn-north-1"}), (az1:AZ {id: "cn-north-1a"})
   CREATE (r1)-[:CONTAINS_AZ]->(az1);
   
   MATCH (r1:Region {id: "cn-north-1"}), (az2:AZ {id: "cn-north-1b"})
   CREATE (r1)-[:CONTAINS_AZ]->(az2);
   
   MATCH (r1:Region {id: "cn-north-1"}), (az3:AZ {id: "cn-north-1d"})
   CREATE (r1)-[:CONTAINS_AZ]->(az3);
   
   MATCH (r2:Region {id: "cn-northwest-1"}), (az4:AZ {id: "cn-northwest-1a"})
   CREATE (r2)-[:CONTAINS_AZ]->(az4);
   
   MATCH (r2:Region {id: "cn-northwest-1"}), (az5:AZ {id: "cn-northwest-1b"})
   CREATE (r2)-[:CONTAINS_AZ]->(az5);
   
   MATCH (r2:Region {id: "cn-northwest-1"}), (az6:AZ {id: "cn-northwest-1c"})
   CREATE (r2)-[:CONTAINS_AZ]->(az6);
   
   // ==========================================
   // 6. 网络资源建模 - VPC & Subnet
   // ==========================================
   
   // 创建VPC相关约束
   CREATE CONSTRAINT vpc_id IF NOT EXISTS FOR (v:VPC) REQUIRE v.id IS UNIQUE;
   CREATE CONSTRAINT subnet_id IF NOT EXISTS FOR (s:Subnet) REQUIRE s.id IS UNIQUE;
   CREATE CONSTRAINT route_table_id IF NOT EXISTS FOR (rt:RouteTable) REQUIRE rt.id IS UNIQUE;
   CREATE CONSTRAINT igw_id IF NOT EXISTS FOR (igw:InternetGateway) REQUIRE igw.id IS UNIQUE;
   
   // 6.1 VPC 资源建模
   CREATE (vpc1:VPC {
   id: "vpc-12345678",
   name: "production-main-vpc",
   cidr: "10.0.0.0/16",
   vpc_flow_logs: {
   enabled: true,
   log_destination_type: "s3",
   log_destination: "s3://vpc-flow-logs-prod-bucket",
   log_format: "${srcaddr} ${dstaddr} ${srcport} ${dstport} ${protocol} ${packets} ${bytes} ${start} ${end} ${action}",
   log_status: "ACTIVE",
   delivery_status: "SUCCESS"
   },
   dns_hostnames: true,
   dns_resolution: true,
   tag: {
   environment: "production",
   project: "core-platform",
   team: "platform-engineering",
   backup: "daily"
   },
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   CREATE (vpc2:VPC {
   id: "vpc-87654321",
   name: "staging-vpc",
   cidr: "10.1.0.0/16",
   vpc_flow_logs: {
   enabled: false,
   log_destination_type: null,
   log_destination: null,
   log_format: null,
   log_status: "INACTIVE",
   delivery_status: null
   },
   dns_hostnames: true,
   dns_resolution: true,
   tag: {
   environment: "staging",
   project: "core-platform",
   team: "platform-engineering",
   backup: "none"
   },
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   // 6.2 Subnet 资源建模
   // Production VPC Subnets
   CREATE (subnet1:Subnet {
   id: "subnet-abc12345",
   name: "production-web-subnet-1a",

6. 14:51 · Aug 7, 2025 · Thu

   ",

7. 14:51 · Aug 7, 2025 · Thu

   ,

8. 14:51 · Aug 7, 2025 · Thu

   // ==========================================
   // 云资源可视化地图系统 - Neo4j 图数据库建模
   // 第一阶段：核心基础资源建模
   // ==========================================
   
   // 1. 创建唯一性约束
   CREATE CONSTRAINT account_id IF NOT EXISTS FOR (a:Account) REQUIRE a.id IS UNIQUE;
   CREATE CONSTRAINT region_id IF NOT EXISTS FOR (r:Region) REQUIRE r.id IS UNIQUE;
   CREATE CONSTRAINT az_id IF NOT EXISTS FOR (az:AZ) REQUIRE az.id IS UNIQUE;
   CREATE CONSTRAINT cost_id IF NOT EXISTS FOR (c:Cost) REQUIRE c.id IS UNIQUE;
   
   // ==========================================
   // 1. Account（账号）资源建模 - 完善版
   // ==========================================
   CREATE (acc:Account {
   id: "123456789012",
   name: "production-account",
   projects: ["bdp", "dkms", "dqa", "dir", "analytics", "security"],
   organization: "TechCorp-Platform-Engineering",
   env: "prod",
   owner: "[email protected]",
   status: "active",
   tag: {
   cost_center: "engineering",
   department: "platform",
   business_unit: "core_services",
   compliance: "pci_dss"
   },
   created_at: datetime(),
   updated_at: datetime()
   });
   
   // ==========================================
   // 2. Cost（成本）节点建模 - 支持成本云图
   // ==========================================
   
   // 2.1 月度总成本节点
   CREATE (cost_monthly:Cost {
   id: "cost-123456789012-2024-03",
   resource_id: "123456789012",
   resource_type: "Account",
   cost_type: "monthly_total",
   amount: 25680.50,
   currency: "USD",
   period: "2024-03",
   breakdown: {
   compute: 12500.20,
   storage: 3200.15,
   network: 1800.30,
   database: 4500.80,
   lambda: 680.25,
   other: 2999.80
   },
   tag: {
   forecast: "high_confidence",
   variance: "+15%"
   },
   status: "finalized",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   // 2.2 日度成本节点（用于趋势分析）
   CREATE (cost_daily:Cost {
   id: "cost-123456789012-2024-03-15",
   resource_id: "123456789012",
   resource_type: "Account",
   cost_type: "daily",
   amount: 856.20,
   currency: "USD",
   period: "2024-03-15",
   breakdown: {
   compute: 420.50,
   storage: 105.80,
   network: 58.90,
   database: 150.20,
   lambda: 22.60,
   other: 98.20
   },
   tag: {
   anomaly: "normal",
   trend: "increasing"
   },
   status: "estimated",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   // Account与Cost的关系
   MATCH (acc:Account {id: "123456789012"}), (c1:Cost {id: "cost-123456789012-2024-03"})
   CREATE (acc)-[:HAS_COST]->(c1);
   
   MATCH (acc:Account {id: "123456789012"}), (c2:Cost {id: "cost-123456789012-2024-03-15"})
   CREATE (acc)-[:HAS_COST]->(c2);
   
   // ==========================================
   // 3. Region（区域）资源建模 - 增强版
   // ==========================================
   CREATE (region1:Region {
   id: "cn-north-1",
   name: "Beijing",
   availability_sla: 99.99,
   operational_metrics: {
   avg_response_time: 45.2,
   incident_count_monthly: 2,
   maintenance_window: "Sunday 02:00-04:00 UTC+8"
   },
   tag: {
   country: "China",
   provider: "AWS",
   tier: "production"
   },
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   CREATE (region2:Region {
   id: "cn-northwest-1",
   name: "Ningxia",
   availability_sla: 99.95,
   operational_metrics: {
   avg_response_time: 52.8,
   incident_count_monthly: 1,
   maintenance_window: "Sunday 03:00-05:00 UTC+8"
   },
   tag: {
   country: "China",
   provider: "AWS",
   tier: "disaster_recovery"
   },
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   // ==========================================
   // 4. AZ（可用区）资源建模
   // ==========================================
   CREATE (az1:AZ {
   id: "cn-north-1a",
   name: "Beijing Zone A",
   tag: {
   physical_location: "Beijing-DC-Alpha",
   power_redundancy: "N+1"
   },
   status: "active",
   created_at: datetime(),
   updated_at: datetime()
   });
   
   CREATE (az2:AZ {
   id: "cn-north-1b",
   name: "Beijing Zone B",
   tag: {
   physical_location: "Beijing-DC-Beta",

9. 16:16 · Aug 3, 2025 · Sun

   Claude Code Remote 可以远程发送命令给Claude Code，随时随地让AI 干活。
   
   1. 任务完成时多渠道通知（桌面弹窗+声音+邮件+飞书）
   2. 直接在手机上回复消息，Claude收到命令之后继续干活
   3. 支持多轮对话，让 Claude 持续工作
   
   Repo地址：github.com/JessyTsui/Claude-Code-Remote
   
   4. 谷歌开源 LangExtract 从非结构化信息中提取结构化信息的 Python 库，使用 LLMs 从非结构化文本文档中提取结构化信息。
   Repo地址：github.com/google/langextract

10. 16:16 · Aug 3, 2025 · Sun

    # 2025W31 AI大模型领域精选热点 🔥
    
    ---
    
    ## 1. Google
    
    + NotebookLM 的**视频摘要**功能上线，支持把笔记导出视频了！目前 NotebookLM 的 Studio 栏支持四种输出：音频、视频、思维导图、报告。地址：notebooklm.google.com
    + Google 正式向 Gemini APP Ultra 用户和部分数学家及学者推出了 **Gemini Deep Think**，能够帮助数学家证明猜想。本质上是一种并行推理方法。模型能够仔细推演复杂问题，最终产出更具创造性和深度的答案。尤其在算法设计和代码开发领域，Deep Think 能够综合考量问题的不同解法和复杂度，提升编码的效率和质量。据官方测试，Deep Think 在多项难度极高的基准测试中表现优异，尤其在代码生成和跨学科知识推理方面已经达到行业领先水平。详细介绍：blog.google/products/gemini/gemini-2-5-deep-think
    
    + 谷歌给 Android Studio 增加了免费的 Agent 模式！开发者可以直接跟 Agent 对话开发安卓应用。支持快速选中直接修改 UI 代码，支持自定义规则。地址：android-developers.googleblog.com/2025/07/android-studio-narwhal-feature-drop-stable-agent-mode.html
    
    + 谷歌搜索 AI Mode 更新，基本功能与 Gemini 功能（支持上传图片和 PDF/ Canvas 能力/视频跟 AI 实时对话）拉齐，目前只有美国和印度可以用
    
    + Google 新论文介绍了一种新的 Deep Researcher 思路：TTD-DR框架。人类在写作复杂主题时，通常会先制定计划，然后起草报告，并在多次修订中完善内容。这一过程与扩散模型的采样过程相似，即从噪声草稿开始，逐步去噪生成高质量输出。论文地址：arxiv.org/pdf/2507.16075
    
    ## 2. Ali 一系列模型更新
    
    + Qwen3-30B-A3B-2507 的推理版本，本地部署友好。 模型地址：huggingface.co/Qwen/Qwen3-30B-A3B-Thinking-2507
    + Qwen3-30B-A3B-Instruct-2507的非推理版本，本地部署友好。 模型地址：huggingface.co/Qwen/Qwen3-30B-A3B-Instruct-2507
    + Qwen3-Coder-Flash 发布，模型名称为 Qwen3-Coder-30B-A3B-Instruct。注意这也是个非思考模型。原生 256K 上下文（使用 YaRN 可以扩展高达 1M 个 token）。模型地址：huggingface.co/Qwen/Qwen3-Coder-30B-A3B-Instruct
    + 业界首个使用MoE架构的视频生成基础模型，文生视频Wan2.2-T2V-A14B、图生视频Wan2.2-I2V-A14B、统一视频生成Wan2.2-TI2V-5B。
    
    ## 3. OpenAI
    
    + OAI开源模型疑似漏，代号为 yofo gpt-oss 20b 和 120b，此外 openrouter 上还出现 horzon-beta 模型, 同样是256K上下文。120B 模型是 MoE 架构，激活参数大概是 5B，128 专家每次激活 4 个专家。原生只有 4K 上下文，通过 YaRN 扩展到 128K。
    
    + OpenAI 推出了学习模式（Study Mode）会引导用户一步步解决问题，而不仅仅是直接给出答案。感觉不是一个新模型或者agent，可能是用提示词引导的模式。
    
    + Sam Altman 预告本月新模型、新产品、新功能 即将发布。
    
    ## 4. 智谱发布了 GLM-4.5!
    
    > 突出一个性价比，推出每月50块万亿token包月套餐。性能感觉稍逊于kimi 2
    
    新模型包括 GLM-4.5-355B-A32B 和 **GLM-4.5-Air-106B-A12B**，都是**混合推理模型**，可以开关思切换考或者非思考模式。从跑分上来看，最亮眼的是仅用了大概 DeepSeek-R1 一半左右的参数量达到了一个与DeepSeek-R1 不相上下的水平。
    
    模型地址：huggingface.co/zai-org/GLM-4.5
    技术报告地址：z.ai/blog/glm-4.5
    
    ## 5. 其他动态
    
    1. 中科院发布了首个科学基础大模型 S1-Base 磐石科学基础大模型
    
    目前模型有 S1-Base-8B，S1-Base-32B，S1-Base-671B，其中 S1-Base-8B 和 S1-Base-32B 分别基于 Qwen3-8B 和 Qwen3-32B 训练得到，S1-Base-671B 基于 DeepSeek-R1-671B 训练得到，均支持 32k 上下文。
    
    模型地址：huggingface.co/ScienceOne-AI/S1-Base-671B
    
    2. 字节跳动发布文本 Diffusion 模型，Seed Diffusion Preview！
    
    文本Diffusion 模型则是跟图像Diffusion 模型类似，是一个去噪过程，整段话随机出现文本最后组成所有输出。Diffusion 文本模型的优点是巨快，字节这个有 每秒 2146 个 token 的速度。目前除了eed Diffusion Preview以外，还有最知名的 Mercury Coder 和 Google 的 Gemini Diffusion.
    
    发布blog: seed.bytedance.com/en/seed_diffusion
    在线体验地址：studio.seed.ai/exp/seed_diffusion/
    
    3. 中间思考模型 Dhanishtha，这个模型会想一会，然后输出一会，再想一会，再输出一会。支持工具调用。
    
    模型地址：huggingface.co/HelpingAI/Dhanishtha-2.0-preview-0825
    
    4. FLUX 又发新模型！FLUX.1-Krea-dev 是一个文生图模型，特点是照片级真实感。FLUX 与 Krea 联合开发。
    
    模型地址：huggingface.co/black-forest-labs/FLUX.1-Krea-dev
    
    5. Kimi 上架模型型号 kimi-k2-turbo-preview，猜测是 kimi-k2-0711-preview 的不同部署版本。响应速度从 10 token/s 提升到 40 token/s 。
    
    6. ACL最佳论文 《原生稀疏注意力：硬件对齐和原生可训练的稀疏注意力》（Native Sparse Attention: Hardware-Aligned and Natively Trainable Sparse Attention） ACL 2025 超过一半的论文作者都是华人。论文地址：arxiv.org/abs/2502.11089
    
    7. 用强化学习推动图谱检索生成《Graph-R1: Towards Agentic GraphRAG Framework via End-to-end Reinforcement Learning》，Graph-RAG（图谱增强RAG）用实体-关系图表示知识，提升了信息组织与推理能力。 论文地址：arxiv.org/abs/2507.21892
    
    8. alphaXiv 推出专为科研打造的全新社交平台，内建类似Discord的即时聊天功能，集社区发现、论文讨论与学术交流于一体，助力研究者高效协作。热门communities：Healthcare AI community/AI Security/AI4Science，探索更多 alphaxiv.org/communities
    
    9. 微软研究院公布可能被AI取代的职业: fortune.com/2025/07/31/microsoft-research-generative-ai-occupational-impact-jobs-most-and-least-likely-to-impact-teaching-office-jobs-college-gen-z-grads/
    
    10. Anthropic最新研究Persona vector人格向量，Anthropic 宣布禁止 OpenAI 访问 Claude（是因为OpenAI要发新模型了嘛？）。
    
    11. Manus 超级大更新，发布 Wide Research 功能，支持上百agent独立运行。目前已向 Pro 用户开放，未来将逐步向 Plus 和 Basic 用户开放。
    
    
    
    
    
    ## Github Repos Recommend
    
    1. 开源的知识库 maestro 本地运行 Deep Research ！！！
    
    知识库可以导入文档，执行 RAG，最大的亮点是它内置的 Agent 可以执行 Deep Research 这种任务，并且会给出 Research 的推理过程。支持 OpenAI 风格的 API，搜索使用 SearXNG，并且有 cli 工具支持批量导入和导出。
    
    Repo地址：github.com/murtaza-nasir/maestro
    
    2. 提示词优化器，助力于编写高质量提示词 Prompt Optimizer，支持多种使用方式。
    
    Repo地址：github.com/linshenkx/prompt-optimizer
    
    3.

11. 15:59 · Aug 2, 2025 · Sat

    📖 独立开发穷鬼套餐(Web实践篇) #article
    
    

    很精华，基本上都用过 & 好用！

    
    
    https://guangzhengli.com/blog/zh/indie-hacker-poor-stack

    Guangzhengli

    

    独立开发穷鬼套餐(Web实践篇)

    6000+ 字告诉你如何选择独立开发技术栈和平台，如何开启性价比独立开发之旅

12. 08:33 · Aug 1, 2025 · Fri

    #分布式
    《Debugging incidents in Google's distributed systems》

13. 12:20 · Jul 31, 2025 · Thu

    

    ×

    

14. 02:49 · Jul 30, 2025 · Wed

    

    ×

    

15. 02:35 · Jul 30, 2025 · Wed

    

    ×

    

16. 14:35 · Jul 28, 2025 · Mon

    

    ×

    

    如果让我推荐一个吐字速度最快的平台，那我会毫不犹豫搬出 Cerebras —— Qwen3 32B 模型可以做到 2k+ TPS, 新出的 Qwen3 235B 可以做到 500+ TPS
    
    在线体验: https://inference.cerebras.ai/

17. 12:44 · Jul 27, 2025 · Sun

    1. 2022年10月乡镇医院确诊
    - 3日 胃镜和病理检查
    - 5日 胃镜和病理检测提示食管癌
    2. 2022年10月 青岛大学附属医院
    - 10～11日 增强CT
    3. 2022年10月 广州中山大学肿瘤医院
    - 14日 门诊
    - 一系列检查
    - 21 日门诊
    - 31日 PET CT
    4. 2022年11月 广州中山大学肿瘤医院
    - 2日 白紫 + 洛铂 + 卡瑞利珠
    5. 2022年11月 诸城市人民医院
    - 25 日 白紫 + 顺铂 + 卡瑞利珠
    6. 2022年12月 北京电力医院
    - 20 日 白紫 + 顺铂 + 信迪利单抗
    7. 2022年12月 北京大学肿瘤医院
    - 门诊
    - 定位
    8. 2023年1月 北京大学肿瘤医院
    - 10 日 放疗开始
    - 12 日 白紫 + 顺铂 + 尼妥珠
    - 19 日 尼妥珠
    - 26 日 尼妥珠
    9. 2023年2月 北京大学肿瘤医院
    - 20 日 改野
    - 24 日 放疗33次
    10. 2023年3月 北京大学肿瘤医院
    - 26～29日 检查
    - 尼妥珠
    11. 2023年7月 北京大学肿瘤医院
    - 检查
    - 尼妥珠
    12. 2023年10月 北京大学肿瘤医院
    - 检查
    - 尼妥珠
    13. 2024年2月 北京大学肿瘤医院
    - 检查
    - 尼妥珠
    14. 2024年6月 北京大学肿瘤医院
    - 检查
    - 尼妥珠
    15. 2024年9月 北京大学肿瘤医院
    - 检查
    - 尼妥珠
    - 胃镜检查
    16. 2024年11月 北京大学肿瘤医院
    - 检查
    - 尼妥珠
    17. 2025年3月 北京大学肿瘤医院
    - 检查
    - 尼妥珠
    18. 2025年7月 北京大学肿瘤医院

18. 10:06 · Jul 27, 2025 · Sun

    c语言教程获取

19. 10:06 · Jul 27, 2025 · Sun

    扫第牲的藏经阁

20. 10:05 · Jul 27, 2025 · Sun

    https://hardcore-tech.feishu.cn/wiki/LNm3wyCcSiTtXRk15CecDavunsf

    hardcore-tech.feishu.cn

    Docs