yb172 / experiments Goto Github PK

load-generator sends request to gen-gateway which talks to either gen-number, gen-word, or gen-internets. However that's what topology shows:

Even though linkerd is very nice lightweight solution it looks like istio as of today is more feature-rich and is even tested as part of kubernetes project.

So let's setup istio

It is rare case that services don't require persistence. Most often service stores some info in database, postgres often being popular choice.

However adding persistence is not just creating instance somewhere and plugging in credentials. Properly configured DB requires:

• Migration scripts (golang-migrate)
• Separate docker image to run migration script
• Init container that runs migration script
  And, importantly:
• DB configured in kubernetes for local development

Make comment in PR (e.g. /run test) run prow job that prints hello world

Right now it sometimes happens that empty page is shown. Since there are no errors reported most likely it is just an empty response: random number was generated and it was 0 - exit immediately.

It's better to actually generate something.

And this looks like a great use case for end-to-end test

In order to explore how good linkerd dashboard is there should be a constant load on the service (or not constant).

It would be nice to have a util that is able to generate load on a service. Ideally: front-end service that could be opened and where load could be configured.

There are two great libraries: Immutables and Typesafe config which have an issue working together: typesafe requires auto-populated class to be a JavaBean...