Service Mesh. Simplified.Easily build cloud native workloads securely and reliably with Istio, with or without sidecars. Latest newsFast, secure and simple: Istio's ambient mode is now Generally Available. Read more Join the communityConnect with over 10,000+ of your peers using, testing and innovating with Istio. Connect with us What is Istio?Istio extends Kubernetes to establish a programmable,
Microservices Meetup で話した step by step BFF の話です。
IntroductionI’m fascinated by the lore and mystery behind microservices. As a concept, microservices feels like one of the most interesting folk architectures of the modern era. It’s useful enough to be applied widely across different usage patterns and also vague enough to mean many different things. I’ve been struggling for a while with understanding what people really mean when they discuss “mi
8/9 に FiNC 社で開催された Microservices Meetup vol.2 で、マイクロサービスと SRECon という話をしました。
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
# Start Jaeger locally $ docker run -d -p 6831:6831/udp -p 16686:16686 jaegertracing/all-in-one:latest $ export DOCKER_IP=`docker-machine ip $(docker-machine active)` $ cd $GOPATH/src # Grab a simple, self-contained OpenTracing example $ go get github.com/opentracing-contrib/examples/go $ cd github.com/opentracing-contrib/examples/go $ go run ./trivial.go $DOCKER_IP # Visualize the tracing instrum
Microservices Meetup vol.1 @FiNC
🚀 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
(ARC309) Getting to Microservices: Cloud Architecture Patterns Gilt transitioned from a monolithic Ruby on Rails and Java application architecture to a microservices architecture running on AWS. This allowed teams to work independently and deploy changes more quickly. Key aspects of Gilt's microservices architecture included organizing teams around business capabilities, using service discovery wi
All successful applications grow more complex over time, and that complexity creates challenges in development. There are two essential strategies to manage this problem: a team can keep everything together (create a monolith) or a team can divide a project into smaller pieces (create microservices). The monolith at its most extreme is a single code base that contains all of an application’s logic
Russ Miles is CTO at Simplicity Itself where he works with his clients to help deliver simple and valuable software and change. Russ' experience covers almost every facet of software delivery having worked across many different domains including Financial Services, Publishing, Defence, Insurance and Search. Russ helps to change all facets of the software delivery process in order to remove unneces
原文 SoundCloud がモノリシックな Rails アーキテクチャからマイクロサービスアーキテクチャに如何に移行していったかという話の第 1 弾。何故このアプローチは駄目でこちらのアプローチを採用したのか, ということが書かれていて大変面白い。 Semantic Events のあたりは現職でも自前で実装していた。複雑かつ重厚なドメインモデルが更新された際に MQ を介して通知し, より軽量な表示用モデルに変換するマイクロサービスが動くといった具合だった。 斜め読み SoundCloud の殆どのプロダクトは Scala, Clojure, JRuby で書かれている。 他のスタートアップ同様, 元々は単一のモノリシックなアーキテクチャだった。 MRI + Rails memcached + MySQL このシステムは Mothership と呼ばれる。 2012 年にローンチ。 R
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
