In this article, we are going to build a NodeJS service and a Golang client using the gRPC framework and Protobuf.
In this article we are going to take a look at Protocol Buffers. Some of its advantages how it fits into gRPC for a MicroService architecture and then we are going to create an example using Golang.
In this article we are going to create a new data repository in our Golang application in order to use Amazon DynamoDB as the database.
In this article we are going to setup a caching layer in our Golang application by using Redis. REDIS is REmote DIctionary Server which is why we called Redis. Redis is an in-memory, key-value data store.
In this article we are going to build a docker container for our Golang application and before doing that we are going to quickly setup Go Modules that will allow us to manage the application dependencies efficiently and also will help us to down load those libraries to build and run the application using docker containers.
In this article, we are going to test our REST API by using the HTTP test library and we are going to use SQLite 3 as the database.
In this article we are going to use goroutines and channels to build an API mashup pulling data from two different APIs… This is going to be the result after the mashup of the two APIs that we are going to integrate using goroutines and channels.
In this article, we are going to unit test our application by mocking some components in order to isolate the modules that we want to test. In the previous article we refactored our API implement a Clean Architecture approach so we created all these interfaces. We are going to use Testify to create the mock repository that is going to be an implementation of the post repository interface.
In this article, we are going to apply the principles of the clean architecture by (Uncle) Bob Martin in our Golang API: Independent of frameworks, Testable, Independent of UI, Independent of Database, Independent of any external agency.