Talk at https://mercari.connpass.com/event/92168/
![Terraform Ops for Microservices](https://cdn-ak-scissors.b.st-hatena.com/image/square/66a87b05f2ace6cfd2cc6b39dcb19f9f35885c69/height=288;version=1;width=512/https%3A%2F%2Ffiles.speakerdeck.com%2Fpresentations%2F71ecf5f02c2a4e949ad4b2fd3c56269f%2Fslide_0.jpg%3F10434566)
Which architecture should you choose for an application? Monolithic architecture - architect an application as a single deployable unit Microservice architecture - architect an application as a collection of loosely coupled, services How to decompose an application into services? Decompose by business capability - define services corresponding to business capabilities Decompose by subdomain - defi
Getting Started with Microservices using Go, gRPC and Kubernetes This article aims to provide a simple introduction to building microservices in Go, using gRPC, and deploying them to a Kubernetes cluster. It shows how to set up two containerized, scalable services, talking to each other using request/response mechanism. One microservice will be responsible for calculating the greatest common divis
For all the buzz about microservices and API gateways, finding specifics can prove surprisingly difficult. I am reminded of the cartoon by Sidney Harris where the first step of a complex mathematical formula is presented, then a miracle occurs, and the sudden appearance of the glorious solution prompts an observer to comment that perhaps we should be more explicit in step two. Since these patterns
Enough with the microservicesTl;dr:Don’t even consider microservices unless you have a system that’s too complex to manage as a monolith. The majority of software systems should be built as a single monolithic application. Do pay attention to good modularity within that monolith, but don’t try to separate it into separate services. – Martin Fowler If you can’t build a well-structured monolith, wha
元記事: Varnish and Microservices: Introducing zipnish [update] スライドへのリンクが変わっていたので更新: https://www.slideshare.net/Varnish_software/microservices-20-61197134 Amedia が Microservices パターンを適用した時の事例を元に Zipnish というソフトウェアの紹介記事 元記事には無い前提情報 Microservices アーキテクチャを apply する時に Varnish を活用する手法があるようだ。 今まではそれぞれのサービス間はそれぞれ通信するので、接続先のサービスを探す "Service Discovery" の問題を解決しなければいけなかった。具体的には、各サービスのインスタンス情報の格納のために Service Dir
This document summarizes a microservices meetup hosted by @mosa_siru. Key points include: 1. @mosa_siru is an engineer at DeNA and CTO of Gunosy. 2. The meetup covered Gunosy's architecture with over 45 GitHub repositories, 30 stacks, 10 Go APIs, and 10 Python batch processes using AWS services like Kinesis, Lambda, SQS and API Gateway. 3. Challenges discussed were managing 30 microservices, ensur
🚀 Adopt Go in your organization. Go is a lovely little language that's perfectly suited to writing microservices. Go kit fills in the gaps left by the otherwise excellent standard library, giving your team the confidence to adopt Go throughout your stack. 🔍 Focus on your business logic. Adopting microservices means building a distributed system, and that comes with a lot of challenges. Go kit
TOPICS Web 発行年月日 2016年02月 PRINT LENGTH 344 ISBN 978-4-87311-760-7 原書 Building Microservices FORMAT PDF EPUB マイクロサービスとは、ThoughtWorks社のマーチン・ファウラーとジェームス・ルイスが最初に提唱したソフトウェアアーキテクチャです。モノリシック(一枚岩)なアーキテクチャを、ビジネス機能に沿って複数の小さい「マイクロサービス」に分割し、それらを連携させるアーキテクチャにすることで、迅速なデプロイ、優れた回復性やスケーラビリティといった利点を実現しようとするものです。本書は、マイクロサービスとは何か、その長所と短所、定義と概念、設計思想、アーキテクトの役割から、分割、デプロイ、テスト、監視、セキュリティといった個別の技術までを、マイクロサービスを採用しているNetflixや
Nic Jackson Geek, Ultrarunner and in my spare time software engineering manager for notonthehighstreet.com. Twitter Google+ LinkedIn Github Introduction I went to a conference a few weeks ago which was angled at technology in the retail environment, by lunchtime nobody had mentioned the words “Docker” or “Microservices”, I made my excuses and got the hell out of there. Everyone is talking about Mi
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く