This is usually a challenge that any developer has to take care of when building an AI agent. In fact, managing the context is one of the hardest problems when working with AI agents and there are many companies like SuperMemory, Mem0 which have invested both resources and time to solve this problem. - Source: dev.to / about 1 month ago

Memory. I use Supermemory for this. Before, Pipa loaded context files and knew to update them. A memory tool adds teammate-like recall: goals, preferences, latest business state, and small details that should carry across runs. Good memory tools also know how to supersede and delete memories, which matters once the agent has more autonomy. - Source: dev.to / 3 months ago

We wire everything up with Vision Agents as the voice agent framework, Stream for WebRTC audio and video, OpenAI Realtime for speech in and speech out, Anam so the agent shows up as a face on the video, and Supermemory so answers come from search over your uploaded documents instead of guesswork. The code stays small and most of the behavior lives in one registered function that asks the memory store for relevant... - Source: dev.to / 4 months ago

My friends and I are working on https://supermemory.ai, an AI second brain to help you remember content from saved webpages and notes. - Source: Hacker News / about 2 years ago

I once read a paper about Apache/Meta Thrift [1,2]. It allows you to define data types/interfaces in a definition file and generate code for many programming languages. It was specifically designed for RPCs and microservices. [1]: https://thrift.apache.org/. - Source: Hacker News / almost 2 years ago

While gRPC and Apache Thrift have served the microservice architecture well, CloudWeGo's advanced features and performance metrics set it apart as a promising open source solution for the future. - Source: dev.to / over 2 years ago

Services in general communicate via Thrift (and in some cases HTTP). Source: over 3 years ago

Protocol Buffers is the most popular one, but there are many others such as Apache Thrift and my own Typical. Source: over 3 years ago

RPC is not strictly OO, but you can think of RPC calls like method calls. In general it will reflect your interface design and doesn't have to be top-down, although a good project usually will look that way. A good contrast to REST where you use POST/PUT/GET/DELETE pattern on resources where as a procedure call could be a lot more flexible and potentially lighter weight. Think of it like defining methods in code... Source: almost 4 years ago