Do you think about gRPC usage? Here is a great post about step-by-step guide to gRPC framework development. You’ll find here code examples, theory introductions and useful tips. Enjoy learning! 🙂
#manual #development #microservices #examples
https://medium.com/@shijuvar/building-high-performance-apis-in-go-using-grpc-and-protocol-buffers-2eda5b80771b?source=linkShare-b636419a57de-1516656055
#manual #development #microservices #examples
https://medium.com/@shijuvar/building-high-performance-apis-in-go-using-grpc-and-protocol-buffers-2eda5b80771b?source=linkShare-b636419a57de-1516656055
Medium
Building High Performance APIs In Go Using gRPC And Protocol Buffers
APIs are backbone of modern applications. APIs are powering the backend for web client and mobile client applications, and also used for…
❤1👍1
Are you a beginner in GoLang? Then it requires your attention 🙂.
Good and simple for understanding article about microservice-based API development; just simple and work solution with code examples and couple of advices
#development #microservices #architecture #practice
https://medium.com/@thedevsaddam/build-restful-api-service-in-golang-using-gin-gonic-framework-85b1a6e176f3?source=linkShare-b636419a57de-1516910445
Good and simple for understanding article about microservice-based API development; just simple and work solution with code examples and couple of advices
#development #microservices #architecture #practice
https://medium.com/@thedevsaddam/build-restful-api-service-in-golang-using-gin-gonic-framework-85b1a6e176f3?source=linkShare-b636419a57de-1516910445
Top-featured manual about kubernates-services step-by-step development. Code examples, service design, test coverage
#development #microservices #architecture
https://blog.gopheracademy.com/advent-2017/kubernetes-ready-service/
#development #microservices #architecture
https://blog.gopheracademy.com/advent-2017/kubernetes-ready-service/
Gopheracademy
Write a Kubernetes-ready service from zero step-by-step
If you have ever tried Go, you probably know that writing services with Go is an easy thing. Yes, we really need only few lines to be able to run http service.
Interesting step-by-step guide about design and development API with Docker containers, Swarm cluster and Traefik (HTTP reverse proxy and load balancer).
In this article you’ll know how to configure the Traefik in the Docker environment with 3 following nodes: one manager and two workers
#architecture #configuration #docker #microservices
https://hackernoon.com/architecting-a-highly-scalable-golang-api-with-docker-swarm-traefik-875d1871cc1f?source=linkShare-b636419a57de-1517171008
In this article you’ll know how to configure the Traefik in the Docker environment with 3 following nodes: one manager and two workers
#architecture #configuration #docker #microservices
https://hackernoon.com/architecting-a-highly-scalable-golang-api-with-docker-swarm-traefik-875d1871cc1f?source=linkShare-b636419a57de-1517171008
Hackernoon
Architecting a Highly Scalable Golang API with Docker Swarm & Traefik | HackerNoon
This post will show you how to setup a <strong>Swarm Cluster</strong>, deploy a couple of microservices, and create a Reverse Proxy Service (with <a href="https://traefik.io/" target="_blank"><strong>Traefik</strong></a>) in charge of routing requests on…
Great article about the architecture inside of Golang microservice, based on the Bob's Clean Architecture Concept (https://8thlight.com/blog/uncle-bob/2012/08/13/the-clean-architecture.html)
Main points: Your GoLang microservice has 4 layers:
- Models, data structures, and their methods;
- Repository, the provider of DB operations and data management,
- Usecase for business logic implementation;
- Delivery, protocol, and algorithms for message handling (HTTP, gRPC, etc).
Each layer should be independent and be available for mocking, for internal communications between application layers.
An example project here: https://github.com/bxcodec/go-clean-arch
Full article on the Hackernoon website:
https://hackernoon.com/golang-clean-archithecture-efd6d7c43047
#development #microservices #architecture
Main points: Your GoLang microservice has 4 layers:
- Models, data structures, and their methods;
- Repository, the provider of DB operations and data management,
- Usecase for business logic implementation;
- Delivery, protocol, and algorithms for message handling (HTTP, gRPC, etc).
Each layer should be independent and be available for mocking, for internal communications between application layers.
An example project here: https://github.com/bxcodec/go-clean-arch
Full article on the Hackernoon website:
https://hackernoon.com/golang-clean-archithecture-efd6d7c43047
#development #microservices #architecture
How can we track our microservice activity and monitor some processes inside of the service? The Prometheus can helps us in it: the next following article discovers an step-by-step flow for set up, configure and usage this excellent product:
#development #microservices #monitoring
https://www.google.ru/amp/s/blog.alexellis.io/prometheus-monitoring/amp/
#development #microservices #monitoring
https://www.google.ru/amp/s/blog.alexellis.io/prometheus-monitoring/amp/
The article by Paul Dix calls “The Decomposable Monolith: Long Live the Monolith, Long Live Services!”
Code examples are available but without a code highlighting 🙂
#architecture #development #microservices
https://www.influxdata.com/blog/decomposable-monolith-long-live-monolith-long-live-services/
Code examples are available but without a code highlighting 🙂
#architecture #development #microservices
https://www.influxdata.com/blog/decomposable-monolith-long-live-monolith-long-live-services/
InfluxData
Build A Monolithic Application to be Easily Decomposed Later | InfluxData
In this post we explore the advantages of a monolith while proposing a way to structure a new project to being broken out into services later. To help illustrate the idea, well work through an example using Go as the implementation language and a next...
Very interesting article calls “From monoliths to microservices: an architectural strategy.” The structure of this post:
- Adopting Microservices;
- Microservices Architectural Patterns;
- Architectural & Implementation Considerations;
- Developer Productivity During Microservices Adoption;
#architecture #development #microservices
https://thenewstack.io/from-monolith-to-microservices
- Adopting Microservices;
- Microservices Architectural Patterns;
- Architectural & Implementation Considerations;
- Developer Productivity During Microservices Adoption;
#architecture #development #microservices
https://thenewstack.io/from-monolith-to-microservices
The New Stack
From Monoliths to Microservices: An Architectural Strategy
Most people outside of IT just don’t get how difficult it is to manage complex enterprise systems. It is a
Great post about service discovery and load balancing for GoLang microservices. Code examples, theory and step-by-step instructions are here:
#architecture #microservices #development
https://callistaenterprise.se/blogg/teknik/2017/04/24/go-blog-series-part7/
#architecture #microservices #development
https://callistaenterprise.se/blogg/teknik/2017/04/24/go-blog-series-part7/
callistaenterprise.se
Go microservices, part 7 - Service Discovery & Load-balancing. | Callista
Callista Enterprise - seniora IT-arkitekter och systemutvecklare inom Java, öppen källkod, agil utveckling och systemintegration
This is a perfect longread about organization of microservice’s testing.
#microservices #testing #architecture
https://medium.com/@copyconstruct/testing-microservices-the-sane-way-9bb31d158c16?source=linkShare-b636419a57de-1520885775
#microservices #testing #architecture
https://medium.com/@copyconstruct/testing-microservices-the-sane-way-9bb31d158c16?source=linkShare-b636419a57de-1520885775
Medium
Testing Microservices, the sane way
There’s no dearth of information or best-practices or books about how best to test software. This post, however, focuses solely on testing…