https://jsokit.com/blog/tags/database/ Recent content in Database on JsonKit Blog Hugo en © 2025 JsonKit Sun, 10 May 2026 17:07:26 +0000 https://jsokit.com/blog/posts/uuid-generator-algorithms-from-v1-to-v4-implementation/ Sun, 10 May 2026 17:07:26 +0000 https://jsokit.com/blog/posts/uuid-generator-algorithms-from-v1-to-v4-implementation/ UUID Generator Algorithms: From v1 to v4 Implementation Building a distributed system recently, I needed globally unique IDs. Started with auto-increment database IDs, then hit a wall with sharding—different databases would generate conflicting IDs. After some research, I went with UUID. Here’s what I learned. What is UUID? UUID (Universally Unique Identifier) is a 128-bit unique identifier, typically shown as a 36-character string: 550e8400-e29b-41d4-a716-446655440000 The format is 8-4-4-4-12, separated by hyphens. https://jsokit.com/blog/posts/env-file-management-from-manual-editing-to-visual-tools/ Wed, 11 Feb 2026 14:21:58 +0000 https://jsokit.com/blog/posts/env-file-management-from-manual-editing-to-visual-tools/ .env File Management: From Manual Editing to Visual Tools Last week I helped a colleague debug a database connection issue. After hours of troubleshooting, we found an extra space in the .env file’s DATABASE_URL. This kind of silly mistake is all too common - manual config editing is prone to errors. The Nature of .env Files The .env file follows the 12-Factor App methodology, separating config from code: # Database config DATABASE_URL=postgres://user:pass@localhost:5432/mydb # API keys API_KEY=sk-xxxxxxxxxxxxx # Environment identifier NODE_ENV=production Simple format, but plenty of pitfalls. https://jsokit.com/blog/posts/building-a-code-sharing-tool-url-hash-storage-and-base64-encoding-techniques/ Fri, 30 Jan 2026 15:09:21 +0000 https://jsokit.com/blog/posts/building-a-code-sharing-tool-url-hash-storage-and-base64-encoding-techniques/ Building a Code Sharing Tool: URL Hash Storage and Base64 Encoding Techniques Recently, I built a code sharing tool that requires a “no backend, permanent validity” sharing mechanism. After researching several approaches, I chose URL Hash + Base64 encoding - simple and reliable. Why URL Hash Storage? Traditional code sharing tools use two approaches: Backend database storage - Store code in database, generate short links. Pros: short links. Cons: needs backend, storage cost, links can expire.