REST API structure that can scale, your recommendations?

• pocketbase

  177 33,430 9.7 Go

  Open Source realtime backend in 1 file

  

Every api (sub-router) has a reference to the base instance, the application. The application holds database connections. And if say the admin api has to access the database it would access it by api.app.Database. I think it's easy to understand but at the same time it doesn't really make sense, because of the way you access the database. You go from your api up to the base and then down to the api. It would make more sense to start at the app, and then go down to the database.Pocketbase: https://github.com/pocketbase/pocketbaseHere's is an example how a sub-router to the admin service has a reference to the app: https://github.com/pocketbase/pocketbase/blob/e4a90f6605d8a8ab24544ac0a89639532b97afc2/apis/admin.go#L33

• Public-Library

  2 86 7.3 Go

  Clean Code & Hexagonal Architecture API in Go - a beginner-friendly example.

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project