go-sqlite3
jsoniter
Our great sponsors
go-sqlite3 | jsoniter | |
---|---|---|
37 | 12 | |
7,373 | 13,010 | |
- | 1.0% | |
6.3 | 0.0 | |
about 1 month ago | 13 days ago | |
C | Go | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
go-sqlite3
-
What 3rd-party libraries do you use often/all the time?
github.com/mattn/go-sqlite3
-
From Golang Beginner to Building Basic Web Server in 4 Days!
For building my web server, I chose to use the Gin framework as the foundation of my app. It was incredibly easy to understand and work with, and I was pleasantly surprised by how seamlessly it integrated with writing unit tests for the server. To handle the database, I leveraged the power of go-sqlite and migrate for efficient SQL queries and migrations. These libraries proved to be both powerful and user-friendly, making the development process a breeze.
- Zig now has built-in HTTP server and client in std
-
Exciting SQLite Improvements Since 2020
SQLite does have an optional "user authentication" extension, though I've not personally tried it out:
https://www.sqlite.org/src/doc/trunk/ext/userauth/user-auth....
The widely used Go SQLite library by mattn says it supports it, if that's useful:
-
Go port of SQLite without CGo
I have an OSS project, sq which is a data-wrangling swiss-army knife for structured data. Think of it as jq for databases. It supports Postgres, SQLServer, MySQL and - relevantly - SQLite. It embeds SQLite via CGo and the mattn/go-sqlite3 driver.
- In-memory key value store
-
Tools besides Go for a newbie
IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here
- GitHub - elgs/gosqlapi: Turns any SQL database into a RESTful API.
-
The most widely used database in the world
In Go, you need to install the go-sqlite3 package first. After that, it’s pretty straightforward to use as well:
-
Exploring Go bindings to SQLite using Wazero
Performance is below crawshaw.io/sqlite, but close enough that it might be competitive with modernc.org/sqlite. I'd need to build a database/sql driver to make a fair comparison (with modernc.org/sqlite and github.com/mattn/go-sqlite3).
jsoniter
-
Handling high-traffic HTTP requests with JSON payloads
Since most of the time would be spent decoding json, you could try to cut this time using https://github.com/bytedance/sonic or https://github.com/json-iterator/go, both are drop-in replacements for the stdlib, sonic is faster.
-
A Journey building a fast JSON parser and full JSONPath
We all know the builtin golang JSON parser is slow.
How about doing comparisons against other implementations?
Like this one: https://github.com/json-iterator/go
-
Polygon: Json Database System designed to run on small servers (as low as 16MB) and still be fast and flexible.
Json-iterator (https://github.com/json-iterator/go), you can replace all of encoding/json with this. It does the same thing but it's faster.
-
How can we umarshal a Big JSON effectively?
Do you want to look at every field all at the same time? If not, you can pick out individual fields. There's other packages such as https://github.com/tidwall/gjson or https://github.com/json-iterator/go that let you pass in paths such as "a.b.c" to extract single fields.
-
Designing a config API for microservices applications built using Go
For each Go type used within the config, we generate a separate unmarshaller function. The unmarshallers use json-iterator to process the output from CUE, while tracking the path within the config to the unmarshalled value. This path tracking will allow the function to check if live overrides have been provided on that path and return the override instead.
-
What type of software do you write at your workplace?
https://github.com/json-iterator/go an alternative JSON encoding package which allows to stream (flush out) encoded data as soon as it's able to (which is in contrast with the stock package which buffers everything until the encoding is known to be complete and OK).
-
Some Go(lang) tips
What to use Easyjson is about the top of the pack and it's straightforward. The downside of efficient tools is that they use code generation to create the code required to turn your structs into json to minimise allocations. This is a manual build step which is annoying. Interestingly json-iterator also uses reflection but it's significantly faster. I suspect black magic.
-
What are your favorite packages to use?
jsoniter for low level access to JSON encode and decode
-
What is the best solution to unique data in golang
I think you have to parse the json, if you dont know exactly what you are looking for and want some validation und prevent manual parsing errors. For parsing big json files it is recommend to read and decode it as stream. Here is an example. If you have serious performance criteria take a look at jsoniter. It can be used as 1 to 1 replacement for standard library.
Takes like 10 minutes to write and parses very efficiently. https://github.com/json-iterator/go looks like it can provide such simple parsing
What are some alternatives?
go-json - Fast JSON encoder/decoder compatible with encoding/json for Go
mapstructure - Go library for decoding generic map values into native Go structures and vice versa.
easyjson - Fast JSON serializer for golang.
GORM - The fantastic ORM library for Golang, aims to be developer friendly
sqlx - general purpose extensions to golang's database/sql
goprotobuf - Go support for Google's protocol buffers
pgx - PostgreSQL driver and toolkit for Go
go-sqlite - Low-level Go interface to SQLite 3
compare-go-json - A comparison of several go JSON packages.
GJSON - Get JSON values quickly - JSON parser for Go
go-sqlite-lite - SQLite driver for the Go programming language
Sqinn-Go - Golang SQLite without cgo