LintCode 176: Route Between Two Nodes in Graph (BFS/DFS经典题)

本文探讨了在有向图中查找两个节点间是否存在路径的问题,提供了三种算法实现方案:广度优先搜索(BFS)、广度优先搜索加已访问标记(BFS+Visited)以及深度优先搜索(DFS),并附带了详细的C++代码示例。
  1. Route Between Two Nodes in Graph
    中文English
    Given a directed graph, design an algorithm to find out whether there is a route between two nodes.

Example
Given graph:

A----->B----->C
 \     |
  \    |
   \   |
    \  v
     ->D----->E

Example 1:
Input:s = B and t = E,
Output:true

Example 2:
Input:s = D and t = C,
Output:false

解法1:BFS
代码如下:

/**
 * Definition for Directed graph.
 * struct DirectedGraphNode {
 *     int label;
 *     vector<DirectedGraphNode *> neighbors;
 *     DirectedGraphNode(int x) : label(x) {};
 * };
 * 
 */


class Solution {
public:
    /*
     * @param graph: A list of Directed graph node
     * @param s: the starting Directed graph node
     * @param t: the terminal Directed graph node
     * @return: a boolean value
     */
    bool hasRoute(vector<DirectedGraphNode*> graph, DirectedGraphNode* s, DirectedGraphNode* t) {
        
        if (s->neighbors.size() == 0) return false;
        if (s == t) return true;
        
        queue<DirectedGraphNode *> q;
        q.push(s);
        
        while(q.size() > 0) {
            DirectedGraphNode * currNode = q.front();
            q.pop();
            for (int i = 0; i < currNode->neighbors.size(); ++i) {
                if (currNode->neighbors[i] == t) {
                    return true;
                } else {
                    q.push(currNode->neighbors[i]);
                }
            }
        }
        return false;
    }
};

解法2:BFS+Visited //memorization版本
代码如下:

/**
 * Definition for Directed graph.
 * struct DirectedGraphNode {
 *     int label;
 *     vector<DirectedGraphNode *> neighbors;
 *     DirectedGraphNode(int x) : label(x) {};
 * };
 * 
 */


class Solution {
public:
    /*
     * @param graph: A list of Directed graph node
     * @param s: the starting Directed graph node
     * @param t: the terminal Directed graph node
     * @return: a boolean value
     */
    bool hasRoute(vector<DirectedGraphNode*> graph, DirectedGraphNode* s, DirectedGraphNode* t) {
        
        if (s->neighbors.size() == 0) return false;
        if (s == t) return true;
        
        queue<DirectedGraphNode *> q;
        unordered_set<DirectedGraphNode *> visited;
        q.push(s);
        visited.insert(s);
        
        while(q.size() > 0) {
            DirectedGraphNode * currNode = q.front();
            q.pop();
            for (int i = 0; i < currNode->neighbors.size(); ++i) {
                if (visited.find(currNode->neighbors[i]) != visited.end()) {
                    continue;
                }
                if (currNode->neighbors[i] == t) {
                    return true;
                } else {
                    q.push(currNode->neighbors[i]);
                    visited.insert(currNode->neighbors[i]);
                }
            }
        }
        return false;
    }
};

解法3:DFS
注意:不用visited也可以,但是速度会慢些。

class Solution {
public:
/*
* @param graph: A list of Directed graph node
* @param s: the starting Directed graph node
* @param t: the terminal Directed graph node
* @return: a boolean value
/
bool hasRoute(vector<DirectedGraphNode
> graph, DirectedGraphNode* s, DirectedGraphNode* t) {
if (graph.size() == 0) return false;
if (s == t) return true;

    int N = graph.size();
    
    for (int i = 0; i < graph.size(); ++i) {
        visited[graph[i]] = 0; 
    }
    
    return dfs(s, t);
}

private:
bool dfs(DirectedGraphNode * source, DirectedGraphNode * target) {
if (source == target) return true;

    if (visited[source] == 1) return false;
    visited[source] = 1;
    for (int i = 0; i < source->neighbors.size(); ++i) {
        if (dfs(source->neighbors[i], target)) return true;
    }
    
    return false;
}

map<DirectedGraphNode *, int> visited;    

};

内容概要:本文详细介绍了“秒杀商城”微服务架构的设计与实战全过程,涵盖系统从需求分析、服务拆分、技术选型到核心功能开发、分布式事务处理、容器化部署及监控链路追踪的完整流程。重点解决了高并发场景下的超卖问,采用Redis预减库存、消息队列削峰、数据库乐观锁等手段保障数据一致性,并通过Nacos实现服务注册发现与配置管理,利用Seata处理跨服务分布式事务,结合RabbitMQ实现异步下单,提升系统吞吐能力。同时,项目支持Docker Compose快速部署和Kubernetes生产级编排,集成Sleuth+Zipkin链路追踪与Prometheus+Grafana监控体系,构建可观测性强的微服务系统。; 适合人群:具备Java基础和Spring Boot开发经验,熟悉微服务基本概念的中高级研发人员,尤其是希望深入理解高并发系统设计、分布式事务、服务治理等核心技术的开发者;适合工作2-5年、有志于转型微服务或提升架构能力的工程师; 使用场景及目标:①学习如何基于Spring Cloud Alibaba构建完整的微服务项目;②掌握秒杀场景下高并发、超卖控制、异步化、削峰填谷等关键技术方案;③实践分布式事务(Seata)、服务熔断降级、链路追踪、统一配置中心等企业级中间件的应用;④完成从本地开发到容器化部署的全流程落地; 阅读建议:建议按照文档提供的七个阶段循序渐进地动手实践,重点关注秒杀流程设计、服务间通信机制、分布式事务实现和系统性能优化部分,结合代码调试与监控工具深入理解各组件协作原理,真正掌握高并发微服务系统的构建能力。
tcw@tcw:~/src$ valgrind --leak-check=full --show-leak-kinds=all --track-origins=yes ./graph_ ==5667== Memcheck, a memory error detector ==5667== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==5667== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==5667== Command: ./graph_ ==5667== Graph (node_count = 5, total_count = 5): 10.0.0.1 10.0.0.2 10.0.0.3 10.0.0.4 10.0.0.6 10.0.0.1 0 5 100 0 0 10.0.0.2 5 0 0 0 0 10.0.0.3 100 0 0 0 0 10.0.0.4 0 0 0 0 0 10.0.0.6 0 0 0 0 0 ==5667== Invalid write of size 8 ==5667== at 0x1092AF: graph_compact (in /home/tcw/src/graph_) ==5667== by 0x1098F5: main (in /home/tcw/src/graph_) ==5667== Address 0x52310d8 is 8 bytes before a block of size 8,192 alloc'd ==5667== at 0x4C33B25: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==5667== by 0x1089DE: graph_init (in /home/tcw/src/graph_) ==5667== by 0x1097B2: main (in /home/tcw/src/graph_) ==5667== ==5667== Invalid read of size 8 ==5667== at 0x109299: graph_compact (in /home/tcw/src/graph_) ==5667== by 0x1098F5: main (in /home/tcw/src/graph_) ==5667== Address 0x522f098 is 8 bytes before a block of size 8,192 alloc'd ==5667== at 0x4C33B25: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==5667== by 0x1089A5: graph_init (in /home/tcw/src/graph_) ==5667== by 0x1097B2: main (in /home/tcw/src/graph_) ==5667== ==5667== ==5667== Process terminating with default action of signal 11 (SIGSEGV) ==5667== Access not within mapped region at address 0x0 ==5667== at 0x1092AF: graph_compact (in /home/tcw/src/graph_) ==5667== by 0x1098F5: main (in /home/tcw/src/graph_) ==5667== If you believe this happened as a result of a stack ==5667== overflow in your program's main thread (unlikely but ==5667== possible), you can try to increase the size of the ==5667== main thread stack using the --main-stacksize= flag. ==5667== The main thread stack size used in this run was 8388608. ==5667== ==5667== HEAP SUMMARY: ==5667== in use at exit: 8,437,784 bytes in 1,027 blocks ==5667== total heap usage: 1,028 allocs, 1 frees, 8,438,808 bytes allocated ==5667== ==5667== 24 bytes in 1 blocks are still reachable in loss record 1 of 4 ==5667== at 0x4C31B0F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==5667== by 0x10896C: graph_init (in /home/tcw/src/graph_) ==5667== by 0x1097B2: main (in /home/tcw/src/graph_) ==5667== ==5667== 8,192 bytes in 1 blocks are still reachable in loss record 2 of 4 ==5667== at 0x4C33B25: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==5667== by 0x1089A5: graph_init (in /home/tcw/src/graph_) ==5667== by 0x1097B2: main (in /home/tcw/src/graph_) ==5667== ==5667== 40,960 bytes in 1 blocks are still reachable in loss record 3 of 4 ==5667== at 0x4C33B25: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==5667== by 0x1089FD: graph_init (in /home/tcw/src/graph_) ==5667== by 0x1097B2: main (in /home/tcw/src/graph_) ==5667== ==5667== 8,388,608 bytes in 1,024 blocks are still reachable in loss record 4 of 4 ==5667== at 0x4C33B25: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==5667== by 0x1089DE: graph_init (in /home/tcw/src/graph_) ==5667== by 0x1097B2: main (in /home/tcw/src/graph_) ==5667== ==5667== LEAK SUMMARY: ==5667== definitely lost: 0 bytes in 0 blocks ==5667== indirectly lost: 0 bytes in 0 blocks ==5667== possibly lost: 0 bytes in 0 blocks ==5667== still reachable: 8,437,784 bytes in 1,027 blocks ==5667== suppressed: 0 bytes in 0 blocks ==5667== ==5667== For counts of detected and suppressed errors, rerun with: -v ==5667== ERROR SUMMARY: 4 errors from 2 contexts (suppressed: 0 from 0) 段错误 (核心已转储)
10-28
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值