Potential Article Series - 'Beyond Hello World in Go, by developing Microservices' Any thoughts/appetite ?
-
I had a thought while I'm in business hibernation to creating a series with the working title as per the subject - I have a background in EDI/Integration (etc), and have spent a large amount of time with Microservices, in Ruby, C#, Kotlin, and I'm now studying Go. My writing style I guess would be conversational/tutorial rather than strictly formal, the series would evolve the reader's knowledge as I say, beyond 'Hello World' .. This is not to say 'I know it all', but suggesting practices and things to consider in Go that I've learnt from Microservices in general .. I don't really want to cover MicrosServices 'reasoning'/raison-d'etre, I could cover a whole tome on using Microservices from classically breaking down a monolith to supply a REST API segregated by data-domain for example, but I think the market is flooded with such My Outline would be, at first blush :- 1 : Simple App to get location data - basic json handling - test the Go setup, do something useful 2 : Command-line client to get temperature data from openweathermap maybe based on location from (1) Flags for Command-line, Env for REST API Key, Logging Revisited 3: Upgrade client from (2) to use Resty REST API Client instead of ‘basic’ HTTP 4: json data handling - basic, unmarshalling to ‘struct’ etc 5: ‘Basic’ MicroService To Get Weather data, using knowledge from 1,2,3 to serve the data 6: Using Ocelot as an API Gateway 7: A second Microservice using Go-Kit to get location (re-visting 1) 8: Use Ocelot to aggregate the results of the two Micro Services 9: Re-Write Client using cobra, viper I don't have a blog platform that suits 'code', it's a right PITA to show code on the blog I do have So, is there any appetite do you think, or should I just put up the first article keep in draft etc, and we'll see what we think when I think I'm done, or, you dont think there's a point
-
I had a thought while I'm in business hibernation to creating a series with the working title as per the subject - I have a background in EDI/Integration (etc), and have spent a large amount of time with Microservices, in Ruby, C#, Kotlin, and I'm now studying Go. My writing style I guess would be conversational/tutorial rather than strictly formal, the series would evolve the reader's knowledge as I say, beyond 'Hello World' .. This is not to say 'I know it all', but suggesting practices and things to consider in Go that I've learnt from Microservices in general .. I don't really want to cover MicrosServices 'reasoning'/raison-d'etre, I could cover a whole tome on using Microservices from classically breaking down a monolith to supply a REST API segregated by data-domain for example, but I think the market is flooded with such My Outline would be, at first blush :- 1 : Simple App to get location data - basic json handling - test the Go setup, do something useful 2 : Command-line client to get temperature data from openweathermap maybe based on location from (1) Flags for Command-line, Env for REST API Key, Logging Revisited 3: Upgrade client from (2) to use Resty REST API Client instead of ‘basic’ HTTP 4: json data handling - basic, unmarshalling to ‘struct’ etc 5: ‘Basic’ MicroService To Get Weather data, using knowledge from 1,2,3 to serve the data 6: Using Ocelot as an API Gateway 7: A second Microservice using Go-Kit to get location (re-visting 1) 8: Use Ocelot to aggregate the results of the two Micro Services 9: Re-Write Client using cobra, viper I don't have a blog platform that suits 'code', it's a right PITA to show code on the blog I do have So, is there any appetite do you think, or should I just put up the first article keep in draft etc, and we'll see what we think when I think I'm done, or, you dont think there's a point
-
I had a thought while I'm in business hibernation to creating a series with the working title as per the subject - I have a background in EDI/Integration (etc), and have spent a large amount of time with Microservices, in Ruby, C#, Kotlin, and I'm now studying Go. My writing style I guess would be conversational/tutorial rather than strictly formal, the series would evolve the reader's knowledge as I say, beyond 'Hello World' .. This is not to say 'I know it all', but suggesting practices and things to consider in Go that I've learnt from Microservices in general .. I don't really want to cover MicrosServices 'reasoning'/raison-d'etre, I could cover a whole tome on using Microservices from classically breaking down a monolith to supply a REST API segregated by data-domain for example, but I think the market is flooded with such My Outline would be, at first blush :- 1 : Simple App to get location data - basic json handling - test the Go setup, do something useful 2 : Command-line client to get temperature data from openweathermap maybe based on location from (1) Flags for Command-line, Env for REST API Key, Logging Revisited 3: Upgrade client from (2) to use Resty REST API Client instead of ‘basic’ HTTP 4: json data handling - basic, unmarshalling to ‘struct’ etc 5: ‘Basic’ MicroService To Get Weather data, using knowledge from 1,2,3 to serve the data 6: Using Ocelot as an API Gateway 7: A second Microservice using Go-Kit to get location (re-visting 1) 8: Use Ocelot to aggregate the results of the two Micro Services 9: Re-Write Client using cobra, viper I don't have a blog platform that suits 'code', it's a right PITA to show code on the blog I do have So, is there any appetite do you think, or should I just put up the first article keep in draft etc, and we'll see what we think when I think I'm done, or, you dont think there's a point
I've been meaning to get into Go for a while now. Sounds like an excellent series to me (and I like conversational articles).