paint-brush
The Microservice Weekly #135 — June 7, 2018by@RisingStack
105 reads

The Microservice Weekly #135 — June 7, 2018

by RisingStackJune 8th, 2018
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

Via: GUILHERME CAMINHA

Companies Mentioned

Mention Thumbnail
Mention Thumbnail
featured image - The Microservice Weekly #135 — June 7, 2018
RisingStack HackerNoon profile picture

Introduction to Python Microservices with Nameko

Via: GUILHERME CAMINHA

In this article — after clarifying the conceptions — you willl learn how to build a proof of concept Microservices application using Python.

Training: Designing Microservice Architectures — Berlin

Via: RISINGSTACK

Last chance to apply! We are hosting a training called ‘Designing Microservice Architectures’ in Berlin, on June 14th-15th. If you’d like to learn how to break down a monolith into microservices properly, join us!

Why you should never build Microservices — and why we do it anyway

Via: MARTIN LARSEN

This talk is based on the path towards a Microservice architecture at Queue-it, and will explore the pros and cons of Microservices. It discusses when to apply the architecture and what alternatives there might be.

Ballerina Tutorial: A Programming Language for Integration

Via: TYLER JEWELL

What is it like to author integration flows in Ballerina that are deployable as scalable microservices on Kubernetes? Check it out via creating a service that asynchronously publishes Homer Simpson quotes published from a hosted REST service to your Twitter account.

ServiceFabric: a distributed platform for building microservices in the cloud

Via: THE MORNING PAPER

Microsoft’s Service Fabric powers many of Azure’s critical services. It’s been in development for around 15 years, in production for 10, and was made available for external use in 2015. Let’s get to know it a little bit better…

Connecting Competing Microservices using RabbitMQ

Via: DAVE SAG

If multiple, identical, services are competing to consume an event, once the event is consumed by one service, how do you ensure that the other non-competing services still get invoked? Learn how to do this with a simple hypothetical example, written in NodeJS, using RabbitMQ as the message bus.

Microservices in Go

Via: ANTON KLIMENKO

In this post, you will read a comparison of the frameworks Go Micro, Go Kit, Gizmo, Kite, for creating Microservices in Go.

In brief

What I have learned Architecting Microservices

Via: ASHAN FERNANDO

Comcast’s monolith to microservices shift spotlights pains, gains

Via: FRED CHURCHVILLE

Become an Expert on DevOps and Microservices with These 7 Articles

Via: DANIELLE GOODMAN

Cloud Microservices Market Worth 1,880.0 Million USD by 2023

Via: MARKETSANDMARKETS