This article breaks down AgentScope Java's five fundamental components—Message, Agent, Model, Memory, and Tool—explaining their roles, structures, code examples, provider switching, tool definition, and state management, while highlighting concurrency pitfalls and persistence options.
This article explains how Spring AI handles prompts, covering the Prompt and Message APIs, role-based message types, PromptTemplate creation, custom template renderers, tokenization basics, and practical code examples to help developers craft effective AI prompts.
This article walks through Spring AI’s three core classes—Message, Prompt, and ChatModel—explaining their roles, showing concrete code examples for constructing messages, building prompts, and invoking a large language model via a REST controller, and provides a complete demo repository.
This article explains Kafka's core concepts—including messages as byte arrays, optional keys for partition control, topic and partition organization, producer and consumer roles, offsets, consumer groups, and broker clusters—providing a concise technical overview for developers learning Kafka.
Over three years the team built a lightweight, C++‑based cross‑platform messaging SDK for a large e‑commerce group, choosing C++ for performance, creating a custom 43‑KB/116‑KB foundation library, organizing five modular layers, employing a pure‑asynchronous thread model, and automating development with the Eyas scaffolding, language‑binding generation and unified GN builds to simplify multi‑OS deployment and reduce engineering effort.
The article explains the core traits of entities—identity and continuity—through domain‑driven design examples, demonstrates why a Message should be modeled as an entity, and discusses the reasoning behind treating Sender and Recipient as value objects or entities in a messaging domain.
The article explains the core characteristics of entities—identity and continuity—using DDD concepts, demonstrates why a Message in a messaging scenario qualifies as an entity, and argues that senders and recipients (contacts) should also be modeled as entities rather than value objects.
