当前位置: 首页 > article >正文

服务通信模式选择完全指南

服务通信模式选择完全指南前言在微服务架构中服务间通信是核心基础设施之一。选择合适的通信模式直接影响系统的性能、可靠性和可维护性。本文将详细介绍同步通信和异步通信的各种模式以及如何根据业务场景做出最佳选择。一、服务通信概述1.1 通信模式分类┌─────────────────────────────────────────────────────┐ │ 微服务通信模式 │ │ │ │ ┌──────────────────┐ ┌──────────────────┐ │ │ │ 同步通信 │ │ 异步通信 │ │ │ │ │ │ │ │ │ │ ┌────────────┐ │ │ ┌────────────┐ │ │ │ │ │ REST API │ │ │ │ 消息队列 │ │ │ │ │ └────────────┘ │ │ └────────────┘ │ │ │ │ ┌────────────┐ │ │ ┌────────────┐ │ │ │ │ │ gRPC │ │ │ │ 事件驱动 │ │ │ │ │ └────────────┘ │ │ └────────────┘ │ │ │ │ ┌────────────┐ │ │ ┌────────────┐ │ │ │ │ │ GraphQL │ │ │ │ 发布/订阅 │ │ │ │ │ └────────────┘ │ │ └────────────┘ │ │ │ └──────────────────┘ └──────────────────┘ │ └─────────────────────────────────────────────────────┘二、同步通信模式2.1 REST APISpring Boot REST API实现RestController RequestMapping(/api/products) Slf4j public class ProductController { Autowired private ProductService productService; Autowired private ProductMapper productMapper; GetMapping(/{id}) public ResponseEntityProductDTO getProduct( PathVariable Long id, RequestHeader(value X-Request-Id, required false) String requestId) { log.info(Getting product with id: {}, requestId: {}, id, requestId); Product product productService.findById(id) .orElseThrow(() - new ProductNotFoundException(id)); return ResponseEntity.ok(productMapper.toDTO(product)); } PostMapping public ResponseEntityProductDTO createProduct( Valid RequestBody CreateProductRequest request, RequestHeader(Authorization) String token) { log.info(Creating product: {}, request.getName()); Product product productService.createProduct(request); return ResponseEntity .created(URI.create(/api/products/ product.getId())) .body(productMapper.toDTO(product)); } PutMapping(/{id}) public ResponseEntityProductDTO updateProduct( PathVariable Long id, Valid RequestBody UpdateProductRequest request) { Product product productService.updateProduct(id, request); return ResponseEntity.ok(productMapper.toDTO(product)); } DeleteMapping(/{id}) public ResponseEntityVoid deleteProduct(PathVariable Long id) { productService.deleteById(id); return ResponseEntity.noContent().build(); } GetMapping public ResponseEntityPageProductDTO listProducts( RequestParam(defaultValue 0) int page, RequestParam(defaultValue 20) int size, RequestParam(required false) String category, RequestParam(defaultValue id) String sortBy, RequestParam(defaultValue desc) String sortDir) { Pageable pageable PageRequest.of(page, size, Sort.by(Sort.Direction.fromString(sortDir), sortBy)); PageProduct products productService.findAll(category, pageable); PageProductDTO dtoPage products.map(productMapper::toDTO); return ResponseEntity.ok(dtoPage); } }2.2 OpenFeign客户端// 启用OpenFeign SpringBootApplication EnableFeignClients(basePackages com.example.clients) public class OrderServiceApplication { public static void main(String[] args) { SpringApplication.run(OrderServiceApplication.class, args); } } // 定义Feign客户端 FeignClient( name product-service, url ${services.product-service.url}, fallbackFactory ProductServiceFallbackFactory.class, configuration FeignConfig.class ) public interface ProductServiceClient { GetMapping(/api/products/{id}) ProductDTO getProduct(PathVariable(id) Long id); PostMapping(/api/products) ProductDTO createProduct(RequestBody CreateProductRequest request); GetMapping(/api/products) PageProductDTO listProducts( RequestParam int page, RequestParam int size ); } // Feign配置 Configuration public class FeignConfig { Bean public Logger.Level feignLoggerLevel() { return Logger.Level.FULL; } Bean public Retryer feignRetryer() { return new Retryer.Default(100, 1000, 3); } Bean public RequestInterceptor requestInterceptor() { return new RequestInterceptor() { Override public void apply(RequestTemplate template) { // 添加认证信息 SecurityContext context SecurityContextHolder.getContext(); if (context.getAuthentication() ! null) { template.header(Authorization, context.getAuthentication().getCredentials().toString()); } // 添加追踪信息 template.header(X-Request-Id, UUID.randomUUID().toString()); } }; } } // Fallback实现 Component Slf4j public class ProductServiceFallbackFactory implements FallbackFactoryProductServiceClient { Override public ProductServiceClient create(Throwable cause) { log.error(Product service call failed, cause); return new ProductServiceClient() { Override public ProductDTO getProduct(Long id) { throw new ServiceUnavailableException(Product service is temporarily unavailable); } Override public ProductDTO createProduct(CreateProductRequest request) { throw new ServiceUnavailableException(Product service is temporarily unavailable); } Override public PageProductDTO listProducts(int page, int size) { return Page.empty(); } }; } }2.3 gRPC通信// product.proto syntax proto3; package product; option java_multiple_files true; option java_package com.example.product.grpc; option java_outer_classname ProductProto; service ProductService { rpc GetProduct(GetProductRequest) returns (ProductResponse); rpc CreateProduct(CreateProductRequest) returns (ProductResponse); rpc ListProducts(ListProductsRequest) returns (ListProductsResponse); rpc StreamProductUpdates(StreamProductUpdatesRequest) returns (stream ProductUpdate); } message GetProductRequest { int64 id 1; } message ProductResponse { int64 id 1; string name 2; string description 3; double price 4; int32 stock_quantity 5; } message CreateProductRequest { string name 1; string description 2; double price 3; } message ListProductsRequest { int32 page 1; int32 size 2; } message ListProductsResponse { repeated ProductResponse products 1; int32 total_count 2; } message StreamProductUpdatesRequest { repeated int64 product_ids 1; } message ProductUpdate { int64 product_id 1; UpdateType type 2; ProductResponse product 3; enum UpdateType { CREATED 0; UPDATED 1; DELETED 2; STOCK_CHANGED 3; } }// gRPC服务端实现 GrpcService Slf4j public class ProductGrpcService extends ProductServiceGrpc.ProductServiceImplBase { Autowired private ProductService productService; Autowired private ProductMapper productMapper; Override public void getProduct(GetProductRequest request, StreamObserverProductResponse responseObserver) { log.info(gRPC getProduct request: {}, request.getId()); try { Product product productService.findById(request.getId()) .orElseThrow(() - new ProductNotFoundException(request.getId())); ProductResponse response ProductResponse.newBuilder() .setId(product.getId()) .setName(product.getName()) .setDescription(product.getDescription()) .setPrice(product.getPrice().doubleValue()) .setStockQuantity(product.getStockQuantity()) .build(); responseObserver.onNext(response); responseObserver.onCompleted(); } catch (Exception e) { log.error(Error getting product, e); responseObserver.onError(Status.INTERNAL .withDescription(e.getMessage()) .asRuntimeException()); } } Override public void listProducts(ListProductsRequest request, StreamObserverListProductsResponse responseObserver) { Pageable pageable PageRequest.of(request.getPage(), request.getSize()); PageProduct products productService.findAll(pageable); ListProductResponse responses products.stream() .map(p - ProductResponse.newBuilder() .setId(p.getId()) .setName(p.getName()) .setDescription(p.getDescription()) .setPrice(p.getPrice().doubleValue()) .setStockQuantity(p.getStockQuantity()) .build()) .collect(Collectors.toList()); ListProductsResponse response ListProductsResponse.newBuilder() .addAllProducts(responses) .setTotalCount((int) products.getTotalElements()) .build(); responseObserver.onNext(response); responseObserver.onCompleted(); } }三、异步通信模式3.1 RabbitMQ消息队列// RabbitMQ配置 Configuration public class RabbitMQConfig { public static final String ORDER_EXCHANGE order.exchange; public static final String ORDER_QUEUE order.queue; public static final String ORDER_ROUTING_KEY order.created; public static final String INVENTORY_EXCHANGE inventory.exchange; public static final String INVENTORY_QUEUE inventory.queue; public static final String INVENTORY_ROUTING_KEY order.created; public static final String DEAD_LETTER_EXCHANGE dlx.exchange; public static final String DEAD_LETTER_QUEUE dlx.queue; Bean public DirectExchange orderExchange() { return ExchangeBuilder.directExchange(ORDER_EXCHANGE) .durable(true) .build(); } Bean public Queue orderQueue() { return QueueBuilder.durable(ORDER_QUEUE) .withArgument(x-dead-letter-exchange, DEAD_LETTER_EXCHANGE) .withArgument(x-dead-letter-routing-key, order.dead) .withArgument(x-message-ttl, 30000) .build(); } Bean public Binding orderBinding() { return BindingBuilder.bind(orderQueue()) .to(orderExchange()) .with(ORDER_ROUTING_KEY); } Bean public DirectExchange deadLetterExchange() { return ExchangeBuilder.directExchange(DEAD_LETTER_EXCHANGE) .durable(true) .build(); } Bean public Queue deadLetterQueue() { return QueueBuilder.durable(DEAD_LETTER_QUEUE).build(); } Bean public Binding deadLetterBinding() { return BindingBuilder.bind(deadLetterQueue()) .to(deadLetterExchange()) .with(order.dead); } } // 消息发送 Service RequiredArgsConstructor public class OrderMessageProducer { private final RabbitTemplate rabbitTemplate; public void sendOrderCreatedEvent(OrderCreatedEvent event) { log.info(Sending order created event: {}, event.getOrderId()); rabbitTemplate.convertAndSend( RabbitMQConfig.ORDER_EXCHANGE, RabbitMQConfig.ORDER_ROUTING_KEY, event, message - { message.getMessageProperties().setContentType(application/json); message.getMessageProperties().setMessageId(event.getEventId()); message.getMessageProperties().setTimestamp(new Date()); message.getMessageProperties().setHeader(x-order-id, event.getOrderId()); return message; } ); } public void sendOrderPaidEvent(OrderPaidEvent event) { rabbitTemplate.convertAndSend( RabbitMQConfig.ORDER_EXCHANGE, order.paid, event ); } } // 消息消费 Component Slf4j public class InventoryMessageConsumer { Autowired private InventoryService inventoryService; RabbitListener(queues RabbitMQConfig.INVENTORY_QUEUE) RabbitHandler public void handleOrderCreated(OrderCreatedEvent event) { log.info(Received order created event: {}, event.getOrderId()); try { // 扣减库存 for (OrderItemDTO item : event.getItems()) { inventoryService.reserveStock( event.getOrderId(), item.getProductId(), item.getQuantity() ); } log.info(Inventory reserved successfully for order: {}, event.getOrderId()); } catch (InsufficientStockException e) { log.error(Insufficient stock for order: {}, event.getOrderId()); // 发布库存不足事件 throw e; // 将触发消息重试或进入死信队列 } } RabbitListener(queues RabbitMQConfig.DEAD_LETTER_QUEUE) public void handleDeadLetter(Message message) { log.error(Received dead letter message: {}, new String(message.getBody())); // 处理死信消息通常是记录日志或发送告警 } }3.2 Kafka消息队列// Kafka配置 Configuration public class KafkaConfig { Bean public NewTopic orderTopic() { return TopicBuilder.name(order-events) .partitions(6) .replicas(3) .config(TopicConfig.RETENTION_MS_CONFIG, 604800000) // 7天 .config(TopicConfig.MIN_IN_SYNC_REPLICAS_CONFIG, 2) .build(); } Bean public NewTopic productTopic() { return TopicBuilder.name(product-events) .partitions(6) .replicas(3) .build(); } Bean public KafkaTemplateString, Object kafkaTemplate( ProducerFactoryString, Object producerFactory) { return new KafkaTemplate(producerFactory); } } // Kafka生产者 Service RequiredArgsConstructor public class OrderEventProducer { private final KafkaTemplateString, Object kafkaTemplate; public void sendOrderCreated(Order order) { OrderCreatedEvent event OrderCreatedEvent.builder() .eventId(UUID.randomUUID().toString()) .orderId(order.getId()) .customerId(order.getCustomerId()) .totalAmount(order.getTotalAmount()) .items(order.getItems().stream() .map(this::toItemDTO) .collect(Collectors.toList())) .occurredAt(Instant.now()) .build(); kafkaTemplate.send(order-events, order.getId().toString(), // 使用订单ID作为key保证相同订单的消息在同一分区 event) .whenComplete((result, ex) - { if (ex ! null) { log.error(Failed to send order created event, ex); } else { log.info(Order created event sent successfully, offset: {}, result.getRecordMetadata().offset()); } }); } private OrderItemDTO toItemDTO(OrderItem item) { return OrderItemDTO.builder() .productId(item.getProductId()) .quantity(item.getQuantity()) .price(item.getPrice()) .build(); } } // Kafka消费者 Service Slf4j public class InventoryEventConsumer { Autowired private InventoryService inventoryService; KafkaListener( topics order-events, groupId inventory-service, containerFactory kafkaListenerContainerFactory ) public void consumeOrderEvent(ConsumerRecordString, OrderCreatedEvent record) { log.info(Received order event from partition {} offset {}, record.partition(), record.offset()); OrderCreatedEvent event record.value(); try { // 使用事务保证消息处理原子性 processOrderEvent(event); log.info(Order event processed successfully: {}, event.getOrderId()); } catch (Exception e) { log.error(Failed to process order event, e); // 可以选择抛出异常触发重试或发送到DLQ } } Transactional public void processOrderEvent(OrderCreatedEvent event) { event.getItems().forEach(item - { inventoryService.reserveStock( event.getOrderId(), item.getProductId(), item.getQuantity() ); }); } }3.3 事件驱动架构// 领域事件定义 public interface DomainEvent extends Serializable { String getEventId(); Instant getOccurredAt(); } Data Builder public class OrderCreatedEvent implements DomainEvent { private final String eventId; private final String orderId; private final String customerId; private final ListOrderItemEvent items; private final Money totalAmount; private final Instant occurredAt; Override public String getEventId() { return eventId; } Override public Instant getOccurredAt() { return occurredAt; } } // 事件发布器 Service public class DomainEventPublisher { private final ApplicationEventPublisher applicationEventPublisher; private final ObjectMapper objectMapper; public void publish(DomainEvent event) { log.info(Publishing domain event: {} - {}, event.getClass().getSimpleName(), event.getEventId()); // 发布Spring事件 applicationEventPublisher.publishEvent(event); // 发布到消息队列 publishToMessageBus(event); } private void publishToMessageBus(DomainEvent event) { try { String topic getTopicForEvent(event); kafkaTemplate.send(topic, event.getEventId(), event); } catch (Exception e) { log.error(Failed to publish event to message bus, e); // 考虑重试或告警 } } private String getTopicForEvent(DomainEvent event) { return switch (event) { case OrderCreatedEvent _ - order-events; case OrderPaidEvent _ - payment-events; case ProductUpdatedEvent _ - product-events; default - domain-events; }; } } // 事件订阅 Service Slf4j public class InventoryEventHandler { KafkaListener(topics order-events, groupId inventory-handler) public void handleOrderCreated(OrderCreatedEvent event) { log.info(Handling order created event: {}, event.getOrderId()); event.getItems().forEach(item - { inventoryService.reserveStock( event.getOrderId(), item.getProductId(), item.getQuantity() ); }); } }四、通信模式选择4.1 同步vs异步选择// 选择决策树 public class CommunicationPatternSelector { public CommunicationPattern selectPattern( BusinessScenario scenario) { // 场景1需要立即返回结果 if (scenario.isRequiresResponse()) { // HTTP/gRPC同步调用 if (scenario.isHighThroughput()) { return CommunicationPattern.GRPC; } else { return CommunicationPattern.REST; } } // 场景2不需要立即返回结果 if (scenario.isRequiresReliability()) { return CommunicationPattern.MESSAGE_QUEUE; } // 场景3事件驱动 if (scenario.isEventDriven()) { return CommunicationPattern.EVENT_DRIVEN; } return CommunicationPattern.REST; } } // 业务场景分类 public enum BusinessScenario { // 同步场景 USER_LOGIN(true, false, false), PRODUCT_QUERY(true, false, false), PRICE_CALCULATION(true, false, false), // 异步场景 ORDER_CREATION(false, true, true), EMAIL_SENDING(false, true, false), PAYMENT_PROCESSING(false, true, true), // 事件场景 INVENTORY_UPDATE(false, true, true), NOTIFICATION_PUSH(false, false, true), AUDIT_LOG(false, false, true); }4.2 混合架构实践// 混合通信架构 RestController RequestMapping(/api/orders) RequiredArgsConstructor public class OrderController { private final OrderService orderService; private final OrderEventProducer eventProducer; // 同步创建订单并返回订单ID PostMapping public ResponseEntityCreateOrderResponse createOrder( Valid RequestBody CreateOrderRequest request) { Order order orderService.createOrder(request); // 异步发布订单创建事件 eventProducer.sendOrderCreated(order); return ResponseEntity.accepted() .body(CreateOrderResponse.builder() .orderId(order.getId()) .status(order.getStatus()) .createdAt(order.getCreatedAt()) .message(Order created successfully, processing in background) .build()); } // 同步查询订单状态 GetMapping(/{id}) public ResponseEntityOrderDTO getOrder(PathVariable Long id) { Order order orderService.findById(id); return ResponseEntity.ok(orderMapper.toDTO(order)); } }五、最佳实践5.1 熔断降级// Resilience4j配置 Configuration public class Resilience4jConfig { Bean public CircuitBreakerRegistry circuitBreakerRegistry() { CircuitBreakerConfig defaultConfig CircuitBreakerConfig.custom() .failureRateThreshold(50) .waitDurationInOpenState(Duration.ofSeconds(30)) .slidingWindowSize(10) .minimumNumberOfCalls(5) .permittedNumberOfCallsInHalfOpenState(3) .automaticTransitionFromOpenToHalfOpenEnabled(true) .build(); return CircuitBreakerRegistry.of(defaultConfig); } Bean public CircuitBreaker productCircuitBreaker( CircuitBreakerRegistry registry) { return registry.circuitBreaker(productService); } } // 使用熔断 Service RequiredArgsConstructor public class OrderService { private final ProductServiceClient productClient; private final CircuitBreaker productCircuitBreaker; public OrderDTO createOrder(CreateOrderRequest request) { // 使用熔断器包装外部服务调用 ProductDTO product productCircuitBreaker.executeSupplier( () - productClient.getProduct(request.getProductId()) ); // ... 创建订单逻辑 } }5.2 重试机制Configuration public class RetryConfig { Bean public RetryRegistry retryRegistry() { RetryConfig defaultConfig RetryConfig.custom() .maxAttempts(3) .waitDuration(Duration.ofMillis(500)) .retryExceptions(Exception.class) .failAfterMaxAttempts(true) .build(); return RetryRegistry.of(defaultConfig); } } Service RequiredArgsConstructor public class PaymentService { private final RetryRegistry retryRegistry; public PaymentResult processPayment(PaymentRequest request) { Retry retry retryRegistry.retry(paymentRetry); retry.executeRunnable(() - { // 支付逻辑 paymentGateway.charge(request); }); return new PaymentResult(); } }总结微服务通信模式的选择需要综合考虑业务场景、性能要求、可信赖性需求等多个因素。在实际应用中很多系统会采用混合架构同步和异步通信并存以满足不同业务需求。关键是要理解各种通信模式的特点根据具体场景做出合理的选择。

相关文章:

服务通信模式选择完全指南

服务通信模式选择完全指南 前言 在微服务架构中,服务间通信是核心基础设施之一。选择合适的通信模式直接影响系统的性能、可靠性和可维护性。本文将详细介绍同步通信和异步通信的各种模式,以及如何根据业务场景做出最佳选择。 一、服务通信概述 1.1 通信…...

Bazzite 42.20250417深度解析:云原生游戏操作系统的技术革命

Bazzite 42.20250417深度解析:云原生游戏操作系统的技术革命 【免费下载链接】bazzite Bazzite makes gaming and everyday use smoother and simpler across desktop PCs, handhelds, tablets, and home theater PCs. 项目地址: https://gitcode.com/gh_mirrors/…...

C++ 重载与重写的区别与实现

1 . 前言在面向对象语言中,经常提到重载与重写,以下内容直观描述两者差异成员函数被重载的特征: (1)相同的范围(在同一个类中); (2)函数名字相同;…...

3分钟完成缠论分析:ChanlunX通达信插件实现自动画中枢

3分钟完成缠论分析:ChanlunX通达信插件实现自动画中枢 【免费下载链接】ChanlunX 缠中说禅炒股缠论可视化插件 项目地址: https://gitcode.com/gh_mirrors/ch/ChanlunX 还在为缠论分析的手动画线而烦恼吗?ChanlunX缠论插件为你带来终极解决方案&a…...

QtScrcpy键鼠映射实战指南:5分钟打造专业级手机游戏控制体验

QtScrcpy键鼠映射实战指南:5分钟打造专业级手机游戏控制体验 【免费下载链接】QtScrcpy Android实时投屏软件,此应用程序提供USB(或通过TCP/IP)连接的Android设备的显示和控制。它不需要任何root访问权限 项目地址: https://gitcode.com/barry-ran/QtS…...

10分钟搭建个人游戏云:Sunshine开源游戏串流服务器完全指南

10分钟搭建个人游戏云:Sunshine开源游戏串流服务器完全指南 【免费下载链接】Sunshine Self-hosted game stream host for Moonlight. 项目地址: https://gitcode.com/GitHub_Trending/su/Sunshine 你是否梦想过在任何设备上畅玩PC游戏?想要在客厅…...

微软逐步淘汰 SMS 身份验证,通行密钥带来更强安全保障!

ZDNET 要点总结微软正在逐步淘汰将 SMS 作为身份验证方式,因为 SMS 消息未加密,易受黑客攻击。微软账户所有者将被提示设置通行密钥。通常登录或找回在线账户时会收到 SMS 验证短信,但这并非安全的身份验证方式,如今微软对使用微软…...

用Excel手搓反向传播神经网络:零代码理解梯度下降

1. 项目概述:用Excel手搓一个能反向传播的神经网络,真不用写一行代码你有没有过这种感觉:想搞懂神经网络到底是怎么“学”会识别猫狗、预测房价的,可一翻开教材就是矩阵求导、链式法则、张量运算,还没开始就卡在了数学…...

震惊!数十万家企业用软件监控员工,数据竟流向广告平台和经纪商!

官宣惊人内幕数十万家企业使用软件监控员工,新研究发现,许多职场监控工具不仅与雇主共享数据,还与数字广告平台和数据经纪商共享。研究详情这项研究由哥伦比亚法学院法律与经济中心高级研究员、前联邦贸易委员会首席技术专家斯蒂芬妮阮&#…...

轻量级本地OCR工具SmolDocling实战指南

1. 项目概述:为什么需要一个本地运行的轻量级OCR应用?SmolDocling这个名字本身就带着点工程师式的幽默感——“smol”是“small”的网络变体,强调体积小、依赖少;“Docling”则暗指文档(document)处理的小精…...

AI 时代软件股反弹:行业分化,谁能成为新的基础设施巨头?

【美股软件股“集体误杀”】去年 10 月底开始,美股软件股经历了一场罕见的“集体误杀”。以软件 ETF——IGV 为代表,整个软件板块一度从高位显著回撤,跌幅接近 40%。曾经被视为高质量成长资产的软件公司,突然变成了 AI 浪潮下的“…...

乐聚智能拟募资26亿冲击创业板,人形机器人商业化初期盈利难题待解

乐聚智能冲击创业板,投后估值43.27亿近日,乐聚智能(深圳)股份有限公司向深交所递交招股书,拟在创业板上市,保荐人为东方证券。乐聚智能是首家选择使用创业板第四套标准申请上市的企业,该标准要求…...

公共卫生响应系统:交互式仪表盘+医疗聊天机器人+时序预测

1. 项目概述:这不是一个“疫情看板”,而是一套可落地的公共卫生响应辅助工具“Interactive COVID-19 Dashboard With Chatbot and Prediction Capabilities”——这个标题里藏着三个被很多人忽略的关键动词:Interactive(交互式&am…...

华硕笔记本性能控制新选择:G-Helper轻量化控制中心完全指南

华硕笔记本性能控制新选择:G-Helper轻量化控制中心完全指南 【免费下载链接】g-helper Lightweight Armoury Crate alternative for Asus laptops with nearly the same functionality. Works with ROG Zephyrus, Flow, TUF, Strix, Scar, ProArt, Vivobook, Zenboo…...

AI成为核心经济驱动力的四大标志与落地路径

1. 这不是技术升级,而是一场经济结构的静默重置“AI’s Next Strategic Phase: From Lab Curiosity to Core Economy Driver”——这个标题里没有一行代码,没提一个模型参数,却比任何benchmark跑分都更刺眼。它说的不是“大模型又涨了几个点”…...

单北斗GNSS变形监测系统在地质灾害监测中的应用与维护

北斗 GNSS 变形监测系统在地质灾害监测中发挥着重要作用。它通过高精度定位,实时捕捉地面形变,为防灾减灾提供精准数据支持。系统的定制化设计能适应不同环境,同时具备稳定性与可靠性。随着技术发展,监测和维护也变得更高效。这种…...

5分钟快速获取微信数据库密钥:Sharp-dumpkey完整使用指南

5分钟快速获取微信数据库密钥:Sharp-dumpkey完整使用指南 【免费下载链接】Sharp-dumpkey 基于C#实现的获取微信数据库密钥的小工具 项目地址: https://gitcode.com/gh_mirrors/sh/Sharp-dumpkey 你是否曾因为无法访问自己的微信聊天记录而感到困扰&#xff…...

CVPR 2023五大技术断层:泛化性、实时性与边缘部署的工程真相

1. 这不是会议速记,而是一份“CVPR 2023技术脉络手绘地图”如果你在搜索引擎里输入“CVPR 2023 summary”,大概率会看到一堆标题党文章:什么“十大突破”、什么“最火模型TOP5”、什么“必看论文清单”。我翻过不下二十篇,结果发现…...

LoRA参数高效微调:低秩适配原理与可视化实战

1. 项目概述:这不是调参,是给大模型“打补丁”的手艺活LoRA(Low-Rank Adaptation)不是什么新潮概念,它本质上是一种参数高效微调(PEFT)的工程实践智慧——当你要让一个百亿参数的GPT或BERT模型去…...

软件许可优化选到头大?八家公司直接给你答案

上周一个做采购的朋友打电话来,声音都哑了。说他们公司被Adobe审计盯上了,对方要他们在两周内提交过去三年的部署报告。他们IT就两个人,连公司有多少台电脑装了Photoshop都说不清。我问她你现在打算怎么办,她说正在看各种软件许可…...

华为OD机试真题 新系统 2026-05-20 JavaGoC语言 实现【多模型版本的最优调度】

目录 题目 思路 Code 题目 在大语言模型推理服务中,有多个不同大小的模型版本可供选择。每个模型版本有不同的准确率和推理延迟。给定查询次数 N 和总时间预算 T,为每个查询选择一个模型版本,使得在不超过时间预算的前提下,总准…...

通过curl命令快速测试Taotoken接口连通性与模型响应效果

🚀 告别海外账号与网络限制!稳定直连全球优质大模型,限时半价接入中。 👉 点击领取海量免费额度 通过curl命令快速测试Taotoken接口连通性与模型响应效果 对于开发者而言,在集成大模型服务时,快速验证接口…...

Local AI Needs to Be the Norm — A Beginner’s Guide for Developers

Local AI Needs to Be the Norm — A Beginner’s Guide for Developers You’ve probably noticed it: more and more developers are running large language models on their laptops—not as a curiosity, but as part of daily workflow. Not just toy experiments, but …...

Ollama迁移到vLLM:本地大模型服务生产化实战指南

1. 项目概述:为什么一个本地大模型服务迁移指南值得写满5000字?“From Local to Production: The Ultimate Ollama to vLLM Migration Guide”——这个标题里藏着三重现实张力:本地开发的便利性、生产环境的严苛性,以及大模型推理…...

魔兽争霸III终极优化指南:5大功能彻底解决现代系统兼容性问题

魔兽争霸III终极优化指南:5大功能彻底解决现代系统兼容性问题 【免费下载链接】WarcraftHelper Warcraft III Helper , support 1.20e, 1.24e, 1.26a, 1.27a, 1.27b 项目地址: https://gitcode.com/gh_mirrors/wa/WarcraftHelper 还在为魔兽争霸III在现代电脑…...

基准测试结果刚出炉,DeepSeek在医疗/法律/金融三大垂直领域事实准确率对比,谁在说真话?

更多请点击: https://intelliparadigm.com 第一章:基准测试结果刚出炉,DeepSeek在医疗/法律/金融三大垂直领域事实准确率对比,谁在说真话? 我们基于权威垂直领域评测集——MedMCQA(医疗)、Case…...

Triton+KServe构建高稳定性AI模型服务架构

1. 项目概述:当模型走出Jupyter,真正开始呼吸真实世界空气“From Notebook to Production: Running ML in the Real World (Part 4)”——这个标题本身就像一句暗号,专为那些在Jupyter里调通了模型、画出了漂亮ROC曲线、却在把模型推上服务器…...

RTB点击率预估中的长尾失衡与价值重标定

1. 项目概述:当广告竞价遇上“长尾陷阱”——为什么实时竞价系统里99%的流量不说话,却决定着100%的效果你有没有遇到过这样的情况:训练了一个看起来AUC高达0.92的点击率预估模型,上线后CTR却比老模型还低0.3个百分点?或…...

告别代码阅读障碍:MultiHighlight智能高亮插件提升3倍开发效率

告别代码阅读障碍:MultiHighlight智能高亮插件提升3倍开发效率 【免费下载链接】MultiHighlight Jetbrains IDE plugin: highlight identifiers with custom colors 🎨💡 项目地址: https://gitcode.com/gh_mirrors/mu/MultiHighlight …...

Udemy课程下载器:如何高效离线学习Udemy课程内容?

Udemy课程下载器:如何高效离线学习Udemy课程内容? 【免费下载链接】udemy-downloader-gui A desktop application for downloading Udemy Courses 项目地址: https://gitcode.com/gh_mirrors/ud/udemy-downloader-gui 想要随时随地学习Udemy课程却…...