goa VS KintoHub

goa Reviews

KintoHub Reviews

1. Blake    

   Designer at Happyer | over 3 years ago
   It's like the modern heroku!

   It's very easy to deploy anything on KintoHub. It's really a full-stack solution, unlike many others that have obstacles when deploying a database or aggressive pricing. The free tier is very generous to get started with a hobby app and try it out first. If you add your card you can get more flexibility as well with the advanced customizations on the resources.

   🏁 Competitors: Heroku, Netlify, Firebase, Okteto, Vercel

   👍 Pros:    Super simple|Language agnostic|You're not locked in. it's easy to move here.|Fully customized cloud resources|Generouous free plan|Very responsive support on discord

   👎 Cons:    It's a new platform so it's really great for hobby projects at the moment|No teams yet

goa mentions (27)

• IBM to Acquire HashiCorp, Inc

  My experience of Golang is that dependency injection doesn't really have much benefit. It felt like a square peg in a round hole exercise when my team considered it. The team was almost exclusively Java/Typescript Devs so it was something that we thought we needed but I don't believe we actually missed once we decided to not pursue it. If you are looking at OpenAPI in Golang I can recommend having a look at... - Source: Hacker News / 4 days ago

• Microservices communication

  See https://goa.design/. It automates all the comms stuff, so you just write: 1) a design file showing your functions, 2) an implantation of those functions, and 3) a very generic "main.go" (basically the same for all your services) that decides "how is this exposed over gRPC or REST or other comms?". The rest of the code is generated. Source: 5 months ago

• Which is the best framework to create web apps with go?

  If you really need a framework, you can take a look at Echo or, for a contract-first approach, https://goa.design/. Source: 10 months ago

• OpenAPI v4 Proposal

  Few folks in here are (rightly) frustrated with the code generation story and broader tooling support around the OpenAPI standard. I've found a few alternative approaches quite nice to work with: - Use a DSL to describe your service and have it spit out the OpenAPI spec as well as server stubs. In other words, I wouldn't bother writing OpenAPI directly - it's an artifact that is generated at build time. As a Go... - Source: Hacker News / 11 months ago

• Beginner-friendly API made with Go following hexagonal architecture.

  One of the biggest issues I see is that you are using the same models for API as you are for the database. That wouldn’t fly in a real work system. And even though your doing simple CRUD I would introduce another layer for business logic. You should never have the Controller calling you database code directly. It never “stays” that simplistic. One of the easiest ways to deal with this is to use... Source: 11 months ago

KintoHub mentions (0)