Recently, I was responsible for engineering of a microservice to generate dynamic legal PDF documents in huge volume. By design the interconnected platforms send requests along the data to generate the requested document, store it in S3 like buckets, and return the download link.
Considering the number of pages it will grow quickly. Since the legal PDF document are not longer than 5 pages (in our case) so the risk of the memory overhead is acceptable.
Any best practice for: You’ve got 10K+ (id, name) records in PostgreSQL, and need real-time autocomplete in a Laravel + Vue app. User types 3+ characters, and you must return fast, approximate-matching suggestions (10–15 results). #code
🧵
First, I exposed the @typesense as a sub domain sth search.domain.com but the DNS, TLS ... resulted to increase the latency. While it was in the same server, removed the those extra stuff and backed directly connected to search search. Amazing so far.
Any best practice for: You’ve got 10K+ (id, name) records in PostgreSQL, and need real-time autocomplete in a Laravel + Vue app.
User types 3+ characters, and you must return fast, approximate-matching suggestions (10–15 results). #code
🧵
Introducing VS Code Remote Tunnels: Connect to Remote Machines with Ease! dev.to/burkeholland/introduc… #code
Onboarding a new teammate?
First, ask them to follow existing patterns — don’t try to change things right away. Once they understand the flow, then they can suggest improvements. Stability first, innovation second. #DevWisdom #Teamwork