todo-api-microservice-example
logo
todo-api-microservice-example | logo | |
---|---|---|
17 | 24 | |
979 | 5 | |
- | - | |
8.6 | 0.0 | |
7 days ago | almost 3 years ago | |
Go | ||
MIT License | Creative Commons Attribution 4.0 |
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.
todo-api-microservice-example
-
While Learning Haskell Developing Project
Hello guys im a self teach coder. im working with golang atm because this great project speed up my learning curve: https://github.com/MarioCarrion/todo-api-microservice-example
-
Open source projects to look at for best practices?
With that being said, if you're looking for something friendlier, I share my own educational repo, still a WIP but it should help you with the basics.
-
Is there a standard file in Golang from which packages could be installed? Yes, I am aware about go.mod, but hear me out.
internal/tools and
-
Hexagonal architecture and mocking
You are going to need to add a domain package where the Beer type and all the logic associated to that type is defined to avoid the cyclical dependency. I typically follow this approach by using internal as the domain package that then other packages like services, data stores or transport use.
- Working with microservices in a monorepo
-
DDD file structure & cyclic dependencies
Here's my approach; a few worth-mentioning packages in there: * service defines the use cases, it's a glue between the domain model and repositories. * rest defines the http handlers uses the service types via dependency injection (see main.go) * postgresql concrete repository example (there are other implementations for other data stores like kafka, redis, etcetera.
-
Example of a well written and structured RESTful API or web service?
Other redditors mentioned some good resources, I'm going to shamelessly plug mine as well; either way after you are done with whatever tutorial you use I recommend you to look at the Exposure Notifications Server, reading the source code should help you learn other best practices.
-
Golang for backend
One word of advise I can give you is that building a production-grade microservice in Go takes a bit; not because of the language but because you have consider the tradeoffs when choosing different packages to connect everything to make it work (because there's no Django, Ruby on Rails or Spring), I have an educational repository (still work in progress) trying to describe what I've learned from the last 5 years after successfully deploying multiple services to production where multiple engineers contribute and collaborate together; perhaps that could help you.
-
How to avoid "import cycle not allowed" when defining related models in different packages?
With all of that being said I have an educational repository demonstrating this structure, I've been using it in real life for about 5 years already and I've successfully delivered services to production multiple times where multiple engineers contribute and collaborate together.
-
Good example of production grade rest api without an ORM
You may want to checkout the "Exposure Notifications Server" project; I also have a similar (educational) project that uses the Repository Pattern.
logo
-
Ask HN: Good examples of Go back ends?
Most golang backends I've seen meanwhile use or switched to using the "gin" framework to build their APIs.
A lot of them also have conventions for the frontend, where the assets usually are stored in /public, so they can be go:embed later as an embed.FS instance into the binary.
Having said that, there's plenty of examples on github. I'd recommend to take a look at bigger projects or templates and understand how they structured their packages and abstraction levels. E.g. go-admin comes to mind [1]
[1] https://github.com/GoAdminGroup/go-admin
[2] https://github.com/gin-gonic/gin
-
From Laravel to Sponge: How to Easily Develop Web Services with Golang
Excellent Performance: Sponge is built on the gin framework, providing outstanding performance for web service development.
- 6 🔥 Awesome Golang packages (web devs)
-
Generate project code for a general web service(gin) to increase your development efficiency by 10 times
The web framework uses gin. It also includes swagger documents, common service governance function codes, and build and deployment scripts. You can choose which database to use.
-
Gin - HTTP web framework written in GO.
GIN
- How to run background functions in go
-
Fundamentals to Learn
When it comes to Web Development I would recommend taking a closer look at some standard library packages like net and encoding. Looking at some Web Development open-source frameworks / libraries might be helpful as well. Gin is one of them.
-
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
-
Looking to build a small team for a start-up idea
The back-end is going to be written in Golang, using a Gin, Gorm, and a Postgres DB, so bonus points if you are familiar with Go!
-
Can an API be merely a server that has post requests sent to it, rather than something that is installed?
Here's Express for Node.js, Flask for Python, Alfred for Dart, and Gin for Go; that's four different software packages for four completely different programming languages that all do very similar things. Take a look and see which one feels best, and start from there!
What are some alternatives?
fx - A dependency injection based application framework for Go.
recipe-gin-postgres-api - Example of a go HTTP api using gin in zerops.io
svc-fizzbuzz - A simple fizzbuzz microservice
viper - Go configuration with fangs
franz-go - franz-go contains a feature complete, pure Go library for interacting with Kafka from 0.8.0 through 3.6+. Producing, consuming, transacting, administrating, etc.
yaml - YAML support for the Go language.
waypoint - A tool to build, deploy, and release any application on any platform.
Express - Fast, unopinionated, minimalist web framework for node.
exposure-notifications-server - Exposure Notification Reference Server | Covid-19 Exposure Notifications
Squirrel - Fluent SQL generation for golang
explicit-architecture-php - This repository is a demo of Explicit Architecture, using the Symfony Demo Application.
zerolog - Zero Allocation JSON Logger