Ask HN: What's your goto for creating a REST API?

3 points by mdgrech23 ↗ HN
It's 2018, what's your stack look like? Please include language, framework, database/persistence, and how you deploy.

14 comments

[ 3.0 ms ] story [ 41.0 ms ] thread
Java Spring Mongo Proprietary deployment
API Gateway, AWS Lambda (python), Dynamodb, and rolled my own deployment pipeline
Nice, do you have any concerns about vendor lock in?
The thought is there but the functions are implemented with a layer of abstraction that wouldn't make it hard to move to another vendor
Rails, it's easy, always works, takes a couple hours to setup what I need.
Cool, how do you deploy it?
You can use elastic beanstalk (puma + nginx), Heroku, countless other ways. Docker container, nginx, on a server, etc.
ASP.Net Web API with SQL Server, deployed with Visual Studio's one-click publish to Azure, a hosted, Windows Server etc.
Groovy / Grails / JAX-RS + Postgresql, deployed on AWS using Ansible. But I'm working on starting to containerize everything I do, and move to a Docker / Kubernetes centric model.
Jhipster(spring boot) + swagger
Over time I figured its smarter to avoid frameworks whenever possible.

* Backend is nodejs mostly (sometimes extends to express when needed)

* DB is usually SQLlite / hosted mongo

* UI is mostly in HTML/Vue/React in increasing order of complexity (latest stable versions)

Very smooth deploys on Heroku.

My new favorite: Micronaut [1]. It's the first java based framework (though I am using Groovy with it) that just "does what I want" with sensible defaults for a modern REST based API: simple annotation based URI spec on methods with bindings to arguments for parameters, and defaults to JSON responses with encoding etc all built in. You can hook it to hibernate, GORM etc., but I just use Groovy's built in Sql classes which essentially are as good as a minimalistic ORM.

Very simple, no fuss, "just works" as advertised.

[1] http://micronaut.io/