Explore >> Select a destination
|
You are here 
|
www.alexedwards.net | ||
| | | | |
lukasrotermund.de
|
|
| | | | | I/O operations are among the most commonly used tasks in Go. Let's take a look together at the implementation in the Go standard library. | |
| | | | |
benhoyt.com
|
|
| | | | | My re-implementation of the code from the official Go tutorial 'Developing a RESTful API with Go and Gin', using only the standard library, adding tests, and fixing issues. | |
| | | | |
www.integralist.co.uk
|
|
| | | | | Interfaces in Go Name Your Interface Arguments Keep Interfaces Small Accept Interfaces, Return Concrete Types Don't Return Concrete Types Use existing interfaces Don't Force Interfaces Embedding Interfaces Upgrading Interfaces Standard Library Interfaces Tight Coupling Dependency Injection Refactoring Considerations Testing More flexible solutions? Conclusion This post is going to explain the importance of interfaces, and the concept of programming to abstractions (using the Go programming language), by ... | |
| | | | |
www.integralist.co.uk
|
|
| | | Introduction Example Python Origin Code Example Golang Proxy Code Demonstration Explanation NGINX-Lite (not-really) Conclusion Introduction I was struggling to find a good (or just simple) reverse proxy solution written in Go, so I decided to take what I had learnt from a work colleague of mine and put together a simple example for others to build upon if they needed a quick reference point. In this example I have an origin server written in Python (for no other reason than to have a clearer distinction ... | ||
