Introducing Doc explain
Doc Explain is a RAG-as-a-Service backend(Go lang) that lets users upload documents, processes them asynchronously, and enables document-aware Q&A with persistent chat context.
Take a look at https://t.co/pc7nkJiiTL
#golang#backend#ai#aiengineering
document chunks are now encrypted before being stored in the database and decrypted only when needed for retrieval/LLM responses, reducing exposure of raw document text.
Update on RaaS:
Iโve added document-level conversation persistence, so users can ask natural follow-up questions without repeating context. The system remembers recent chat history while still grounding every answer in the document.
Update on RaaS:
Iโve added document-level conversation persistence, so users can ask natural follow-up questions without repeating context. The system remembers recent chat history while still grounding every answer in the document.
Update on RaaS:
Iโve added document-level conversation persistence, so users can ask natural follow-up questions without repeating context. The system remembers recent chat history while still grounding every answer in the document.
Raggo Embedding service, still experimenting tho, chunk size of 250 seems to be big, when i implement the retrival flow, it would hlep me decide better if answers are accurate
Using raggo built in document parser but itโs choking a even pdf files, now all pdf files are being parsed successfully. Since I use open ai models for embeddings, I would implement parser with their SDK. Make sense to just use one provider #golang#openai#ai
Using raggo built in document parser but itโs choking a even pdf files, now all pdf files are being parsed successfully. Since I use open ai models for embeddings, I would implement parser with their SDK. Make sense to just use one provider #golang#openai#ai
Been working RAG-powered Housing-Agent for Lagos tenancy questions.
Itโs based on the Lagos Tenancy Law, 2011, and answers user questions with supporting excerpts from the source document, so you get clarity plus receipts.
Still in the kitchen cooking tho๐งโ๐ณ
#golang#go#ai
Been working RAG-powered Housing-Agent for Lagos tenancy questions.
Itโs based on the Lagos Tenancy Law, 2011, and answers user questions with supporting excerpts from the source document, so you get clarity plus receipts.
Still in the kitchen cooking tho๐งโ๐ณ
#golang#go#ai
@abolorreeeee It wonโt be a general thing or wrapper, say you have two endpoints, one might need it, one wonโt. Scenarios where you might need it would be like if you have to update multiple records at the same time, user a worker pool of like 10 and retry logic and should be good.
Before the hybrid search, the distance I was getting for the answer were between 0.78-0.93, after implementing, same question, I am now getting between 0.3 -0.5
Implemented a Hybrid search in a RAG system I am working and the answer seems more accurate and faster. Will study this and see if a I need a re ranker or not
Implemented a Hybrid search in a RAG system I am working and the answer seems more accurate and faster. Will study this and see if a I need a re ranker or not
Completed the Takeout Order refund system for my restaurant management system in Golang
Here's what makes it production grade:
๐๐ฑ๐ฒ๐บ๐ฝ๐ผ๐๐ฒ๐ป๐ฐ๐
โ check refund table before calling Paystack
โ same order refunded twice = rejected immediately
โ uniqueIndex on order_id enforces this at DB level
๐๐๐ผ๐บ๐ถ๐ฐ ๐ง๐ฟ๐ฎ๐ป๐๐ฎ๐ฐ๐๐ถ๐ผ๐ป
โ refund record created
โ order status โ cancelled
โ payment status โ refunded
โ outbox event written
โ all in ONE transaction, all succeed or all fail
๐ข๐๐๐ฏ๐ผ๐ ๐ฃ๐ฎ๐๐๐ฒ๐ฟ๐ป
โ refund email event written to outbox inside transaction
โ if Redis is down โ outbox worker retries
โ customer always gets refund notification
โ no event lost
๐๐๐ฑ๐ถ๐ ๐ง๐ฟ๐ฎ๐ถ๐น
โ dedicated refunds table
โ own idempotency key
โ reason stored
โ processed_at timestamp
โ every refund traceable forever
Stack: Go, PostgreSQL, Paystack, Redis Streams
GitHub โ https://t.co/aY2N7Rc2dW
Working on the Table reservation refund system