The first time I actually started using Go was for software on our devices. So on our hotspots we have some custom software running in the firmware. For the first device, that was actually completely built by our manufacturer. But for the second generation most of the parts are built by us in-house and we needed a way to quickly develop software for the device. But we don't have any C programmers in-house, so we were actually looking for something that basically sits in between the friendliness of Ruby, but the performance and the ability to be deployed on an embedded system which you get with C. That's basically what led us to Go and it's been awesome for that. It works so well and so great. Since it works so great, it pushed us into looking into whether we should start using this for some backend services as well.

The following basic API endpoints are implemented on the server written in Go:

• Authorization (Sign Up, Sign In)
• Update user profile
• Community: add post, like post, add comment, delete post, add reply to comment
• Self-diagnosis: send data from the app to the server
• Journal: send user data from the app to the server
• Add groups of community
• Report post, report comment, report reply
• Block user

We wrote our own image processing, resizing, and snapshotting service in Go to allow our clients to send photos and GIFs to each other. Files are stored in S3, resized on the fly using OpenCV, and then cached in GroupCache before being served to clients.

Go allows it all to be quite fast and efficient, and entirely non-blocking on uploads!

Our main web scraping engine is built usign Golang because of the way how efficiently and fast this language is. Also out compilation facility let people who dont know Golang build fast as flash scrapers to run ourside of our platform without any knowledge in programming in Golang.

For some of our more taxing parts of our applications, something able to handle high I/O load quickly and with fast processing is needed. Go has completely filled that gap, allowing us to break down walls that would've been completely impossible with other languages.

Spring-Boot allows us to create stand-alone web servers and helps us configure many of our dependencies with sane default, while maintaining flexibility where we need it.

Probably the best application framework in Java, by far. Time-proven, mature.

light weight server approach for REST-services

All services are spring-boot applications.

Solid base for Java-based web app backend