/explore
|
You are here 
|
rmoff.net | ||
| | | | |
kubamartin.com
Practical Golang: Getting started with NATS and related patterns Introduction Microservices... the never disappearing buzzword of our times. They promise a lot, but can be slow or complicated if not implemented correctly. One of the main challenges when developing and using a microservice-based architecture is getting the communication right. Many will ask, why not REST? As I did at some point. Many will actually use it. But the truth is that it leads to tighter coupling, and is synchronous. |
|
| | | | | ||
| | | | |
hjr265.me
Yes, I know there are paid and free tools for doing this. And yes, I know there are tools for this that I can run locally. But this exercise allowed me to try out the well-designed Go package github.com/gocolly/colly. Colly is a web scraping framework for Go. Here is how I used it to quickly scan my website (the one you are on right now) for broken links. First I defined a type for links to check and the URL of the page they appear on: |
|
| | | | | ||
| | | | |
damienradtke.com
|
|
| | | | | ||
| | | | |
boats.gitlab.io
In the previous post I said that in the second post in the series we'd talk about how rooting works. However, as I sat down to write that post, I realized that it would be a good idea to back up and give an initial overview of how a tracing garbage collector works - and in particular, how the underlying garbage collector in shifgrethor is implemented. In the abstract, we can think of the memory of a Rust program with garbage collection as being divided into three sections: the stack, the "unmanaged" heap... |
|
| | | |||
