profile
viewpoint
Eberhard Wolff ewolff Fellow at @innoq Berlin, Germany http://ewolff.com

ewolff/microservice 535

Sample of a Microservice setup for my book. Based on Spring Cloud / Netflix / Java / Docker / Docker Compose / Docker Machine / Vagrant

ewolff/microservice-kafka 378

Demo to show how Apache Kafka can be used for communication between microservices

ewolff/microservice-kubernetes 112

Microservices example using Kubernetes

ewolff/microservice-istio 89

Example for a microservices system based in Kubernetes and the service mesh Istio

ewolff/microservice-consul 88

Sample of a Microservice setup for my book ported to Consul / Apache httpd. Based on Spring Cloud / Netflix / Java / Docker / Docker Compose / Docker Machine

ewolff/InformatikFAQ 45

Informatik als Beruf FAQ

ewolff/microservice-atom 24

Demo to show how Atom can be used for communication between microservices

ewolff/cheatsheets-DE 10

Kurze Übersichten / Cheatsheets zu Maven und Docker

ewolff/microservice-consul-dns 9

Microservices Demo. Uses Consul as DNS server, registration is automated using Registrator

ewolff/crimson-assurance-demo 8

Demo for frontend integration

issue commentewolff/microservice-kafka

I want to change db from postgresql to mysql.

You will need to do the following:

  • Add a MySQL Docker image to docker-compose.yml
  • Replace the Postgres driver in the pom.xml files
  • Replace the Postgres configuration with a MySQL configuration in the application.propertiesfiles
isushilksharma

comment created time in 2 days

issue closedewolff/microservice-kafka

I want to change db from postgresql to mysql.

Is there any way to change postgres db to mysql. I was trying to do so but it's not working, can you help me out for this.

closed time in 2 days

isushilksharma

push eventISA-Principles/isa-principles.org

dependabot[bot]

commit sha 90380ab70e2514b648c4a25cda20f0596213bd1f

Bump nokogiri from 1.10.4 to 1.10.8 Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.10.4 to 1.10.8. - [Release notes](https://github.com/sparklemotion/nokogiri/releases) - [Changelog](https://github.com/sparklemotion/nokogiri/blob/master/CHANGELOG.md) - [Commits](https://github.com/sparklemotion/nokogiri/compare/v1.10.4...v1.10.8) Signed-off-by: dependabot[bot] <support@github.com>

view details

Eberhard Wolff

commit sha 7a0957d23f07d4054946b34907aa3f9040c1738a

Merge pull request #29 from ISA-Principles/dependabot/bundler/nokogiri-1.10.8 Bump nokogiri from 1.10.4 to 1.10.8

view details

push time in 3 days

PR merged ISA-Principles/isa-principles.org

Bump nokogiri from 1.10.4 to 1.10.8 dependencies

Bumps nokogiri from 1.10.4 to 1.10.8. <details> <summary>Release notes</summary>

Sourced from nokogiri's releases.

1.10.8 / 2020-02-10

Security

[MRI] Pulled in upstream patch from libxml that addresses CVE-2020-7595. Full details are available in #1992. Note that this patch is not yet (as of 2020-02-10) in an upstream release of libxml.

1.10.7 / 2019-12-03

Bug

  • [MRI] Ensure the patch applied in v1.10.6 works with GNU patch. #1954

1.10.6 / 2019-12-03

Bug

  • [MRI] Fix FreeBSD installation of vendored libxml2. [#1941, #1953] (Thanks, @​nurse!)

1.10.5 / 2019-10-31

Dependencies

  • [MRI] vendored libxml2 is updated from 2.9.9 to 2.9.10
  • [MRI] vendored libxslt is updated from 1.1.33 to 1.1.34

</details> <details> <summary>Changelog</summary>

Sourced from nokogiri's changelog.

1.10.8 / 2020-02-10

Security

[MRI] Pulled in upstream patch from libxml that addresses CVE-2020-7595. Full details are available in #1992. Note that this patch is not yet (as of 2020-02-10) in an upstream release of libxml.

1.10.7 / 2019-12-03

Fixed

  • [MRI] Ensure the patch applied in v1.10.6 works with GNU patch. [#1954]

1.10.6 / 2019-12-03

Fixed

1.10.5 / 2019-10-31

Security

[MRI] Vendored libxslt upgraded to v1.1.34 which addresses three CVEs for libxslt:

  • CVE-2019-13117
  • CVE-2019-13118
  • CVE-2019-18197
  • CVE-2019-19956

More details are available at #1943.

Dependencies

  • [MRI] vendored libxml2 is updated from 2.9.9 to 2.9.10
  • [MRI] vendored libxslt is updated from 1.1.33 to 1.1.34 </details> <details> <summary>Commits</summary>
  • 6ce10d1 version bump to v1.10.8
  • 2320f5b update CHANGELOG for v1.10.8
  • 4a77fdb remove patches from the hoe Manifest
  • 570b6cb update to use rake-compiler ~1.1.0
  • 2cdb68e backport libxml2 patch for CVE-2020-7595
  • e6b3229 version bump to v1.10.7
  • 4f9d443 update CHANGELOG
  • 80e67ef Fix the patch from #1953 to work with both git and patch
  • 7cf1b85 Fix typo in generated metadata
  • d76180d add gem metadata
  • Additional commits viewable in compare view </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+1 -1

0 comment

1 changed file

dependabot[bot]

pr closed time in 3 days

pull request commentservicemesh-es/servicemesh.es

Remove Consul drawback

The factual statement (requires Consul) is correct and not debated, it seems. Whether it is a drawback is of course a different issue and I can see why it would be considered. Of course, we could clarify ("relies on Consul control plane") or change the drawback for other service meshes - but that would be a different PR.

blake

comment created time in 16 days

push eventewolff/microservice-istio

Eberhard Wolff

commit sha f6e8cf91501e10758b10cdf2414fbf174195c122

Update to Spring Cloud Hoxton SR1 and Spring Boot 2.2.4

view details

push time in 21 days

issue commentewolff/microservice-kafka

Proxy error

Thanks for reaching out and reporting the problem - glad it works!

marcbuchser

comment created time in a month

push eventewolff/ewolff.com

Eberhard Wolff

commit sha 17281f549d7d989b88c4958740f19a2fd5e7a4d2

Fixes

view details

push time in a month

push eventewolff/ewolff.com

Eberhard Wolff

commit sha 6f4a04c72e75a66bc0be7ac5e0b86a92e41975a9

Fixes

view details

push time in a month

push eventewolff/ewolff.com

Eberhard Wolff

commit sha 364dda836c7bd398c0509679324b4685745c79c0

Add new books

view details

push time in a month

push eventewolff/microservice-kubernetes

Eberhard Wolff

commit sha 36fa80f52b7e447e210a26b06a016522e3265af7

Update API version to apps/v1 . Fixes #8

view details

push time in 2 months

issue closedewolff/microservice-kubernetes

changes in microservices.yaml file

update api version in defination file (microsevices.yaml) from "apps/v1beta1" to "apps/v1". mentioned version is showing issue. Also, add instruction in READ.ME file to update docker username in microservices.yaml file so it will fetch images from resprective user docker account.

closed time in 2 months

sunilmbhoi

issue commentewolff/microservice-kubernetes

changes in microservices.yaml file

Thanks for submitting the issue! The instructions to change the Docker account is at https://github.com/ewolff/microservice-kubernetes/blob/master/HOW-TO-RUN.md#build-the-docker-images-optional .

sunilmbhoi

comment created time in 2 months

push eventewolff/microservice-istio

Eberhard Wolff

commit sha 4a644c251d771965158906044d9ff09edb6323f3

Update Elastic 7.5.0

view details

push time in 3 months

push eventewolff/microservice-istio

Eberhard Wolff

commit sha 0fbca6e03c3f1075ed26ec7925701e43f0a92a83

Actually use JUnit 5 for the tests

view details

Eberhard Wolff

commit sha 85ae1a76661695969d14bf1bd58e3f8299680ec5

Update to Spring Boot 2.2.1 and Spring Cloud Hoxton

view details

Eberhard Wolff

commit sha ac6b67eaa555ee64060a2569f434c28e471fb07d

All services now on port 80

view details

push time in 3 months

PR opened drop-ice/dear-github-2.0

Reviewers
Signature
+1 -0

0 comment

1 changed file

pr created time in 3 months

push eventewolff/dear-github-2.0

Eberhard Wolff

commit sha 7c1018e36f7742673eae073ab603fddff50c7ab2

Signature

view details

push time in 3 months

fork ewolff/dear-github-2.0

📨 An open letter to GitHub from the maintainers of open source projects

fork in 3 months

push eventewolff/ewolff.com

Eberhard Wolff

commit sha 50f2cc8212a2ff76d9f16e7b1c3d4e050ce0e088

Add *~ to .gitignore

view details

Eberhard Wolff

commit sha eba112769d947c0f72dabb5b9c675ba12b29fb4b

Add my metrics

view details

push time in 3 months

push eventewolff/microservice-istio

Eberhard Wolff

commit sha 5b1fe09c182f99b2f78ddc0a6f99f4d6e0ddb6df

Fix link to Istio install guide

view details

Eberhard Wolff

commit sha 20a1ab33bf029c1f10dc2fba93077a5339d03c8c

Update to Elastic stack 7.4.2

view details

push time in 3 months

pull request commentservicemesh-es/servicemesh.es

Update the link to fortio.org

Great, thanks a lot for spotting! 👍

leamsigc

comment created time in 3 months

push eventservicemesh-es/servicemesh.es

ismael garcia

commit sha 67dbcb673f34162d0dabe9c4d314d2e9280b9c64

Update the link to fortio.org The link to fortio.org was directing to https://https//fortio.org

view details

Eberhard Wolff

commit sha f6b40deb39eb73d97fb810dac3a9f4843172ce2d

Merge pull request #14 from leamsigc/patch-1 Update the link to fortio.org

view details

push time in 3 months

PR merged servicemesh-es/servicemesh.es

Update the link to fortio.org

The link to fortio.org was directing to https://https//fortio.org

+1 -1

0 comment

1 changed file

leamsigc

pr closed time in 3 months

startedservicemesh-es/servicemesh.es

started time in 3 months

Pull request review commentservicemesh-es/servicemesh.es

Added "How to Choose" section and "Choose if..." row

+<div class="page-layout-xl--default">+  <h2 class="section-heading--primary">Alternatives to Service Meshes</h2>+  +  <p>+  Undoubtedly, Service Meshes are promising technologies that deserve the hype. But they also go along with challenges such as cognitive and technical complexity. +  Like any tool, they are not useful in every situation. Sometimes it might be a wise to keep existing boring technologies or to go with alternative solutions.+</p>++  <div class="blocks">++    <div class="list-teaser list-teaser__body">+      <h2 class="list-teaser__headline">Libraries</h2>+      <p class="list-teaser__text">+        Libraries are included in the Microservices. +        The drawbacks are dependencies on specific technologies/languages, +        potential inconsistency in implementations and +        missing separation of service infrastructure and business logic. +        <br>+        <br>+        However, the developer productivity can (at least in the short term) be better through the familiar use of libraries. +        Also, sometimes domain knowledge is needed, for example to configure the fallback for a circuit breaker or to define business metrics. +        In these cases, a Service Mesh is of no use. +      </p>+    </div>++    <div class="list-teaser list-teaser__body">+      <h2 class="list-teaser__headline">No (synchronous) Microservices</h2>+      <p class="list-teaser__text">+        Synchronously integrated microservices are a popular architecture, despite several drawbacks such as latency and operational complexity. +        One of the reasons is that no other architecture facilitate faster delivery of software.+        <br>+        <br>+        What is often overseen is that there are more approaches to microservices than integrating them synchronously. +        Patterns like SCS and asynchronous communication aim to mitigate many problems of classic mircoservices.

I see. I thought you meant to say that service meshes are useless for async microservices. Maybe you want to add a paragraph that explains how service meshes might help for async?

HPrinz

comment created time in 3 months

Pull request review commentservicemesh-es/servicemesh.es

Added "How to Choose" section and "Choose if..." row

+<div class="page-layout-xl--default">+  <h2 class="section-heading--primary">Alternatives to Service Meshes</h2>+  +  <p>+  Undoubtedly, Service Meshes are promising technologies that deserve the hype. But they also go along with challenges such as cognitive and technical complexity. +  Like any tool, they are not useful in every situation. Sometimes it might be a wise to keep existing boring technologies or to go with alternative solutions.+</p>++  <div class="blocks">++    <div class="list-teaser list-teaser__body">+      <h2 class="list-teaser__headline">Libraries</h2>+      <p class="list-teaser__text">+        Libraries are included in the Microservices. +        The drawbacks are dependencies on specific technologies/languages, +        potential inconsistency in implementations and +        missing separation of service infrastructure and business logic. +        <br>+        <br>+        However, the developer productivity can (at least in the short term) be better through the familiar use of libraries. +        Also, sometimes domain knowledge is needed, for example to configure the fallback for a circuit breaker or to define business metrics. +        In these cases, a Service Mesh is of no use. +      </p>+    </div>++    <div class="list-teaser list-teaser__body">+      <h2 class="list-teaser__headline">No (synchronous) Microservices</h2>+      <p class="list-teaser__text">+        Synchronously integrated microservices are a popular architecture, despite several drawbacks such as latency and operational complexity. +        One of the reasons is that no other architecture facilitate faster delivery of software.+        <br>+        <br>+        What is often overseen is that there are more approaches to microservices than integrating them synchronously. +        Patterns like SCS and asynchronous communication aim to mitigate many problems of classic mircoservices.

I see. I thought you meant to say that service meshes are useless for async microservices. Maybe you want to add a paragraph that explains how service meshes might help for async?

HPrinz

comment created time in 3 months

Pull request review commentservicemesh-es/servicemesh.es

Added "How to Choose" section and "Choose if..." row

+<div class="page-layout-xl--default">+  <h2 class="section-heading--primary">Alternatives to Service Meshes</h2>+  +  <p>+  Undoubtedly, Service Meshes are promising technologies that deserve the hype. But they also go along with challenges such as cognitive and technical complexity. +  Like any tool, they are not useful in every situation. Sometimes it might be a wise to keep existing boring technologies or to go with alternative solutions.+</p>++  <div class="blocks">++    <div class="list-teaser list-teaser__body">+      <h2 class="list-teaser__headline">Libraries</h2>+      <p class="list-teaser__text">+        Libraries are included in the Microservices. +        The drawbacks are dependencies on specific technologies/languages, +        potential inconsistency in implementations and +        missing separation of service infrastructure and business logic. +        <br>+        <br>+        However, the developer productivity can (at least in the short term) be better through the familiar use of libraries. +        Also, sometimes domain knowledge is needed, for example to configure the fallback for a circuit breaker or to define business metrics. +        In these cases, a Service Mesh is of no use. +      </p>+    </div>++    <div class="list-teaser list-teaser__body">+      <h2 class="list-teaser__headline">No (synchronous) Microservices</h2>+      <p class="list-teaser__text">+        Synchronously integrated microservices are a popular architecture, despite several drawbacks such as latency and operational complexity. +        One of the reasons is that no other architecture facilitate faster delivery of software.+        <br>+        <br>+        What is often overseen is that there are more approaches to microservices than integrating them synchronously. +        Patterns like SCS and asynchronous communication aim to mitigate many problems of classic mircoservices.

I see. I thought you meant to say that service meshes are useless for async microservices. Maybe you want to add a paragraph that explains how service meshes might help for async?

HPrinz

comment created time in 3 months

Pull request review commentservicemesh-es/servicemesh.es

Added "How to Choose" section and "Choose if..." row

+<div class="page-layout-xl--default">+  <h2 class="section-heading--primary">Alternatives to Service Meshes</h2>+  +  <p>+  Undoubtedly, Service Meshes are promising technologies that deserve the hype. But they also go along with challenges such as cognitive and technical complexity. +  Like any tool, they are not useful in every situation. Sometimes it might be a wise to keep existing boring technologies or to go with alternative solutions.+</p>++  <div class="blocks">++    <div class="list-teaser list-teaser__body">+      <h2 class="list-teaser__headline">Libraries</h2>+      <p class="list-teaser__text">+        Libraries are included in the Microservices. +        The drawbacks are dependencies on specific technologies/languages, +        potential inconsistency in implementations and +        missing separation of service infrastructure and business logic. +        <br>+        <br>+        However, the developer productivity can (at least in the short term) be better through the familiar use of libraries. +        Also, sometimes domain knowledge is needed, for example to configure the fallback for a circuit breaker or to define business metrics. +        In these cases, a Service Mesh is of no use. +      </p>+    </div>++    <div class="list-teaser list-teaser__body">+      <h2 class="list-teaser__headline">No (synchronous) Microservices</h2>+      <p class="list-teaser__text">+        Synchronously integrated microservices are a popular architecture, despite several drawbacks such as latency and operational complexity. +        One of the reasons is that no other architecture facilitate faster delivery of software.+        <br>+        <br>+        What is often overseen is that there are more approaches to microservices than integrating them synchronously. +        Patterns like SCS and asynchronous communication aim to mitigate many problems of classic mircoservices.

So there is no way to hook into i.e. Kafka and do similar things?

HPrinz

comment created time in 3 months

Pull request review commentservicemesh-es/servicemesh.es

Added "How to Choose" section and "Choose if..." row

 <h2 class="section-heading--primary"> Service Mesh Comparison </h2>         <td>yes</td>       </tr>     </tbody>+    <thead style="background-color: white; color: #ff4d67">+      <tr>+        <th scope="col">Advantages & Drawbacks</th>+      </tr>+    </thead>+    <tbody>+      <tr>+        <th scope="row">Advantages</th>+        <td>Istio can be adapted and extended like no other Mesh. Thanks to it's big and vivid community, it's constantly improved. Istio is <a href="https://istio.io/about/community/customers/" target="_blank">used in production.</a></td>+        <td>Linkerd 2 is designed to be non-invasive and is optimized for performance and usability. It therefore requires little time to adopt. Linkerd 2 is <a href="https://github.com/linkerd/linkerd2/blob/master/ADOPTERS.md" target="_blank">used in production.</a></td>+        <td>AWS App Mesh is integrated in the AWS landscape and it is fully managed for you.</td>+        <td>Consul Connect is well integrated with Consul and the Proxy can be changed and extended.</td>

As it uses Consul it should be possible to run it on any Docker scheduler, right? Is that worth mentioning?

HPrinz

comment created time in 3 months

Pull request review commentservicemesh-es/servicemesh.es

Added "How to Choose" section and "Choose if..." row

 <h2 class="section-heading--primary"> Service Mesh Comparison </h2>         <td>yes</td>       </tr>     </tbody>+    <thead style="background-color: white; color: #ff4d67">+      <tr>+        <th scope="col">Advantages & Drawbacks</th>+      </tr>+    </thead>+    <tbody>+      <tr>+        <th scope="row">Advantages</th>+        <td>Istio can be adapted and extended like no other Mesh. Thanks to it's big and vivid community, it's constantly improved. Istio is <a href="https://istio.io/about/community/customers/" target="_blank">used in production.</a></td>

Do you feel that its support for the different platforms is worth mentioning?

HPrinz

comment created time in 3 months

Pull request review commentservicemesh-es/servicemesh.es

Added "How to Choose" section and "Choose if..." row

+<div class="page-layout-xl--default">+  <h2 class="section-heading--primary">Alternatives to Service Meshes</h2>+  +  <p>+  Undoubtedly, Service Meshes are promising technologies that deserve the hype. But they also go along with challenges such as cognitive and technical complexity. +  Like any tool, they are not useful in every situation. Sometimes it might be a wise to keep existing boring technologies or to go with alternative solutions.+</p>++  <div class="blocks">++    <div class="list-teaser list-teaser__body">+      <h2 class="list-teaser__headline">Libraries</h2>+      <p class="list-teaser__text">+        Libraries are included in the Microservices. +        The drawbacks are dependencies on specific technologies/languages, +        potential inconsistency in implementations and +        missing separation of service infrastructure and business logic. +        <br>+        <br>+        However, the developer productivity can (at least in the short term) be better through the familiar use of libraries. +        Also, sometimes domain knowledge is needed, for example to configure the fallback for a circuit breaker or to define business metrics. +        In these cases, a Service Mesh is of no use. +      </p>+    </div>++    <div class="list-teaser list-teaser__body">+      <h2 class="list-teaser__headline">No (synchronous) Microservices</h2>+      <p class="list-teaser__text">+        Synchronously integrated microservices are a popular architecture, despite several drawbacks such as latency and operational complexity. +        One of the reasons is that no other architecture facilitate faster delivery of software.

That is only the case for synchronous microservices? IMHO there is no good reason to use them.

HPrinz

comment created time in 3 months

create barnchservicemesh-es/servicemesh.es

branch : how-to-choose-42

created branch time in 3 months

push eventservicemesh-es/servicemesh.es

Eberhard Wolff

commit sha abaca4e0b0fe016bb1c13f4148fe1fcb0e73aa0b

More tweaks

view details

push time in 3 months

create barnchservicemesh-es/servicemesh.es

branch : how-to-choose-2

created branch time in 3 months

create barnchservicemesh-es/servicemesh.es

branch : eval-process

created branch time in 3 months

pull request commentservicemesh-es/servicemesh.es

delete temporary files

Great thanks!

larsrh

comment created time in 4 months

push eventservicemesh-es/servicemesh.es

Lars Hupel

commit sha 5e0aec7535eac966fb8f5e72baa145b3f333723c

delete temporary file

view details

Lars Hupel

commit sha 1d3ea8013766e55ddd529c399b4c29b2f6bb14fb

delete temporary file

view details

Eberhard Wolff

commit sha 78504bc893a957a90a13a8f002912d350b2c17e8

Merge pull request #6 from larsrh/patch-1 delete temporary files

view details

push time in 4 months

push eventservicemesh-es/servicemesh.es

Eberhard Wolff

commit sha 30da4da106699d38a9e472600de38005915a1c24

Activate domain

view details

push time in 4 months

push eventservicemesh-es/servicemesh.es

Eberhard Wolff

commit sha 41d8d6b0077feaa09051df717a25ce67444efbce

Activate domain

view details

push time in 4 months

push eventservicemesh-es/servicemesh.es

Eberhard Wolff

commit sha d7718b1e5076e52e388925ab28233cc35ed7ec31

Remove CNAME

view details

push time in 4 months

create barnchservicemesh-es/servicemesh.es

branch : master

created branch time in 4 months

created repositoryservicemesh-es/servicemesh.es

Source for http://servicemesh.es

created time in 4 months

push eventISA-Principles/isa-principles.org

dependabot[bot]

commit sha e5be0fb5000bb943b5b7b725cffacdc99d18cb5e

Bump rubyzip from 1.2.2 to 2.0.0 Bumps [rubyzip](https://github.com/rubyzip/rubyzip) from 1.2.2 to 2.0.0. - [Release notes](https://github.com/rubyzip/rubyzip/releases) - [Changelog](https://github.com/rubyzip/rubyzip/blob/master/Changelog.md) - [Commits](https://github.com/rubyzip/rubyzip/compare/v1.2.2...v2.0.0) Signed-off-by: dependabot[bot] <support@github.com>

view details

Eberhard Wolff

commit sha 93b2a9b7550940aaeb0f07956a3c85b6eee699c2

Merge pull request #28 from ISA-Principles/dependabot/bundler/rubyzip-2.0.0 Bump rubyzip from 1.2.2 to 2.0.0

view details

push time in 4 months

PR merged ISA-Principles/isa-principles.org

Bump rubyzip from 1.2.2 to 2.0.0 dependencies

Bumps rubyzip from 1.2.2 to 2.0.0. <details> <summary>Release notes</summary>

Sourced from rubyzip's releases.

v2.0.0

Security

  • Default the validate_entry_sizes option to true, so that callers can trust an entry's reported size when using extract #403
    • This option defaulted to false in 1.3.0 for backward compatibility, but it now defaults to true. If you are using an older version of ruby and can't yet upgrade to 2.x, you can still use 1.3.0 and set the option to true.

Tooling / Documentation

  • Remove test files from the gem to avoid problems with antivirus detections on the test files #405 / #384
  • Drop support for unsupported ruby versions #406

v1.3.0

Security

  • Add validate_entry_sizes option so that callers can trust an entry's reported size when using extract #403
    • This option defaults to false for backward compatibility in this release, but you are strongly encouraged to set it to true. It will default to true in rubyzip 2.0.

New Feature

  • Add add_stored method to simplify adding entries without compression #366

Tooling / Documentation

  • Add more gem metadata links #402

v1.2.4

  • Do not rewrite zip files opened with open_buffer that have not changed #360

Tooling / Documentation

  • Update example_recursive.rb in README #397
  • Hold CI at trusty for now, automatically pick the latest ruby patch version, use rbx-4 and hold jruby at 9.1 #399

v1.2.3

  • Allow tilde in zip entry names #391 (fixes regression in 1.2.2 from #376)
  • Support frozen string literals in more files #390
  • Require pathname explicitly #388 (fixes regression in 1.2.2 from #376)

Tooling / Documentation:

  • CI updates #392, #394
    • Bump supported ruby versions and add 2.6
    • JRuby failures are no longer ignored (reverts #375 / part of #371)
  • Add changelog entry that was missing for last release #387
  • Comment cleanup #385

Since the GitHub release information for 1.2.2 is missing, I will also include it here:

1.2.2

</tr></table> ... (truncated) </details> <details> <summary>Changelog</summary>

Sourced from rubyzip's changelog.

2.0.0 (2019-09-25)

Security

  • Default the validate_entry_sizes option to true, so that callers can trust an entry's reported size when using extract #403
    • This option defaulted to false in 1.3.0 for backward compatibility, but it now defaults to true. If you are using an older version of ruby and can't yet upgrade to 2.x, you can still use 1.3.0 and set the option to true.

Tooling / Documentation

  • Remove test files from the gem to avoid problems with antivirus detections on the test files #405 / #384
  • Drop support for unsupported ruby versions #406

1.3.0 (2019-09-25)

Security

  • Add validate_entry_sizes option so that callers can trust an entry's reported size when using extract #403
    • This option defaults to false for backward compatibility in this release, but you are strongly encouraged to set it to true. It will default to true in rubyzip 2.0.

New Feature

  • Add add_stored method to simplify adding entries without compression #366

Tooling / Documentation

  • Add more gem metadata links #402

1.2.4 (2019-09-06)

  • Do not rewrite zip files opened with open_buffer that have not changed #360

Tooling / Documentation

  • Update example_recursive.rb in README #397
  • Hold CI at trusty for now, automatically pick the latest ruby patch version, use rbx-4 and hold jruby at 9.1 #399

1.2.3

  • Allow tilde in zip entry names #391 (fixes regression in 1.2.2 from #376)
  • Support frozen string literals in more files #390
  • Require pathname explicitly #388 (fixes regression in 1.2.2 from #376)

Tooling / Documentation:

  • CI updates #392, #394
    • Bump supported ruby versions and add 2.6
    • JRuby failures are no longer ignored (reverts #375 / part of #371)
  • Add changelog entry that was missing for last release #387
  • Comment cleanup #385 </details> <details> <summary>Commits</summary>
  • 2825898 Merge pull request #408 from rubyzip/v2-0-0
  • cb407b1 Bump version to 2.0.0
  • e1d9af6 Merge pull request #406 from rubyzip/bump-supported-ruby
  • 3641a96 Merge pull request #405 from rubyzip/remove-test-files
  • e79d9ea Merge pull request #407 from rubyzip/v1-3-0
  • 7c65e1e Bump version to 1.3.0
  • d65fe7b Merge pull request #403 from rubyzip/check-size
  • 35446f4 Drop old ruby and JDK versions from CI
  • 74d4bec Remove test files from gem
  • 97cb6ae Warn when an entry size is invalid
  • Additional commits viewable in compare view </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+1 -1

0 comment

1 changed file

dependabot[bot]

pr closed time in 4 months

PR merged ISA-Principles/isa-principles.org

Bump nokogiri from 1.10.1 to 1.10.4 dependencies

Bumps nokogiri from 1.10.1 to 1.10.4. <details> <summary>Release notes</summary>

Sourced from nokogiri's releases.

1.10.4 / 2019-08-11

Security

Address CVE-2019-5477 (#1915)

A command injection vulnerability in Nokogiri v1.10.3 and earlier allows commands to be executed in a subprocess by Ruby's Kernel.open method. Processes are vulnerable only if the undocumented method Nokogiri::CSS::Tokenizer#load_file is being passed untrusted user input.

This vulnerability appears in code generated by the Rexical gem versions v1.0.6 and earlier. Rexical is used by Nokogiri to generate lexical scanner code for parsing CSS queries. The underlying vulnerability was addressed in Rexical v1.0.7 and Nokogiri upgraded to this version of Rexical in Nokogiri v1.10.4.

This CVE's public notice is sparklemotion/nokogiri#1915

1.10.3 / 2019-04-22

Security Notes

[MRI] Pulled in upstream patch from libxslt that addresses CVE-2019-11068. Full details are available in #1892. Note that this patch is not yet (as of 2019-04-22) in an upstream release of libxslt.

1.10.2 / 2019-03-24

Security

  • [MRI] Remove support from vendored libxml2 for future script macros. #1871
  • [MRI] Remove support from vendored libxml2 for server-side includes within attributes. #1877

Bug fixes

  • [JRuby] Fix node ownership in duplicated documents. #1060
  • [JRuby] Rethrow exceptions caught by Java SAX handler. [#1847, #1872] (Thanks, @​adjam!)

</details> <details> <summary>Changelog</summary>

Sourced from nokogiri's changelog.

1.10.4 / 2019-08-11

Security

Address CVE-2019-5477 (#1915)

A command injection vulnerability in Nokogiri v1.10.3 and earlier allows commands to be executed in a subprocess by Ruby's Kernel.open method. Processes are vulnerable only if the undocumented method Nokogiri::CSS::Tokenizer#load_file is being passed untrusted user input.

This vulnerability appears in code generated by the Rexical gem versions v1.0.6 and earlier. Rexical is used by Nokogiri to generate lexical scanner code for parsing CSS queries. The underlying vulnerability was addressed in Rexical v1.0.7 and Nokogiri upgraded to this version of Rexical in Nokogiri v1.10.4.

This CVE's public notice is sparklemotion/nokogiri#1915

1.10.3 / 2019-04-22

Security Notes

[MRI] Pulled in upstream patch from libxslt that addresses CVE-2019-11068. Full details are available in #1892. Note that this patch is not yet (as of 2019-04-22) in an upstream release of libxslt.

1.10.2 / 2019-03-24

Security

  • [MRI] Remove support from vendored libxml2 for future script macros. #1871
  • [MRI] Remove support from vendored libxml2 for server-side includes within attributes. #1877

Bug fixes

  • [JRuby] Fix node ownership in duplicated documents. #1060
  • [JRuby] Rethrow exceptions caught by Java SAX handler. [#1847, #1872] (Thanks, @​adjam!) </details> <details> <summary>Commits</summary>
  • beb832e version bump to v1.10.4
  • 5d30128 Merge branch '1915-css-tokenizer-load-file-vulnerability_v1.10.x' into v1.10.x
  • c86b5fc update CHANGELOG
  • 5fe449f regenerate lexical scanner using rexical 1.0.7
  • 6777008 eliminate eval from Builder#initialize
  • 47a7bc7 rufo formatting
  • 094ecb1 rubocop security scan is run as part of the test rake target
  • d068cd4 add rubocop as a dev dependency
  • 45ee92b adding a temporary pipeline for v1.10.x
  • 8e24af5 version bump to v1.10.3
  • Additional commits viewable in compare view </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+1 -1

0 comment

1 changed file

dependabot[bot]

pr closed time in 4 months

push eventISA-Principles/isa-principles.org

dependabot[bot]

commit sha 1a1e48eb6eb60b861187f79ca2121d471b1a8954

Bump nokogiri from 1.10.1 to 1.10.4 Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.10.1 to 1.10.4. - [Release notes](https://github.com/sparklemotion/nokogiri/releases) - [Changelog](https://github.com/sparklemotion/nokogiri/blob/master/CHANGELOG.md) - [Commits](https://github.com/sparklemotion/nokogiri/compare/v1.10.1...v1.10.4) Signed-off-by: dependabot[bot] <support@github.com>

view details

Eberhard Wolff

commit sha 9cea81823a7eff04430fea3d70d3c4585a3d2827

Merge pull request #27 from ISA-Principles/dependabot/bundler/nokogiri-1.10.4 Bump nokogiri from 1.10.1 to 1.10.4

view details

push time in 4 months

issue commentewolff/microservice-kubernetes

Is that possible to add Stackdriver features such as Monitoring, Debugging, Error Reporting, Tracing in this application?

Sure! I am looking forward to your pull request! There is a version for Istio, may that is helpful. https://github.com/ewolff/microservice-istio

Anuradha677

comment created time in 4 months

issue closedewolff/microservice-kubernetes

some questions about the CatalogClient

Hi ewoff, I have trouble in understanding the flowing code in CatalogClient class :

  • ${catalog.service.host:catalog}
  • ${catalog.service.port:8080}

How can Spring get the k8s ip and port ? │s2019-10-10 06:24:02.866 TRACE 7 --- [nio-8080-exec-3] c.e.m.order.clients.CatalogClient : Catalog: URL http://10.104.159.32:8080/catalog/ 2019-10-10 06:24:02.891 TRACE 7 --- [nio-8080-exec-3] c.e.m.order.clients.CustomerClient : Customer: URL http://10.96.95.128:8080/customer/

Br,

closed time in 5 months

wuyongdec

issue commentewolff/microservice-kubernetes

some questions about the CatalogClient

Kubernetes has a build in DNS server that does name resolution. So the host name 'order' is automatically mapped to the IP address of the Kubernetes service. The port would be available as a DNS SRV records, see https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/

wuyongdec

comment created time in 5 months

issue closedewolff/user-registration-V2

have to build user-registration-capacitytest-gatling before it will pass with mvn install

If you just run mvn install from the root, the capacity tests will fail. You can fix it by running mvn test from the user-registration-capacitytest-gatling directory.

It would be great if just one command worked.

closed time in 5 months

rogerdubbs

issue commentewolff/user-registration-V2

have to build user-registration-capacitytest-gatling before it will pass with mvn install

I am unable to reproduce this, sorry.

rogerdubbs

comment created time in 5 months

pull request commentewolff/user-registration-V2

Github Actions Pipeline + Integration Tests

Super, danke!

kesselborn

comment created time in 5 months

push eventewolff/user-registration-V2

Daniel Bornkessel

commit sha 6b772d282760e0fbdbe77011c63c6420dc07cef8

Add integration test Just a simple demonstration, how to test against the built docker image with the user-registration app

view details

Daniel Bornkessel

commit sha fa1a4aa9a9c2e5b914f65ad4d03c3be765df8623

Add github actions pipeline

view details

Daniel Bornkessel

commit sha d97c977eea5f55f482ca7c82dac6b0b3ab4ef1b9

Merge branch 'gh-actions'

view details

Eberhard Wolff

commit sha ce4f8918c65e9c81e511cdcf671f0a80c8213db1

Merge pull request #10 from kesselborn/master Github Actions Pipeline + Integration Tests

view details

push time in 5 months

PR merged ewolff/user-registration-V2

Github Actions Pipeline + Integration Tests

Dieser PR fügt eine Github-Actions Pipeline mit den bestehenden Tests und zusätzlichen Integrationstests hinzu, bei denen eine Docker-Image mit user-registration gestartet wird und ein anderer Container testet diesen Container. Damit die Action durchläuft müssen folgende Secrets angelegt werden:

  • DOCKER_USERNAME
  • DOCKER_PASSWORD (damit das Docker-Image gepushed werden kann ... alternativ kann das Pushen auskommentiert werden)
  • SLACK_WEBHOOK (für Slack-Notifications ... oder dieser Step muss auskommentiert werden)

... README für den Integration-Test fehlt noch

+353 -0

1 comment

7 changed files

kesselborn

pr closed time in 5 months

push eventewolff/microservice-istio

Eberhard Wolff

commit sha 3a9b2cf9bc77d2c94d24225661f444f3e80e48dd

Update to Elastic 7.4.0

view details

push time in 5 months

push eventewolff/microservice-istio

Eberhard Wolff

commit sha 6d1a85f2372fa3d6c526a25f53f72a7caa13b590

Update to Spring Cloud GreenwichSR3 and Spring Boot 2.1.9

view details

Eberhard Wolff

commit sha 1c4d6044038600ee69ed02b3a29f1088fed567c8

Update to Postgres 9.6.15

view details

Eberhard Wolff

commit sha 5461d274696f10e44fbf3d4a608e5ecfd66a7b4d

Uodate to new Kubernetes API versions

view details

push time in 5 months

push eventewolff/microservice-kafka

Eberhard Wolff

commit sha 88aa16718a973da7f1d48881a09368cfb5b2798c

Update to Kafka 2.3.0

view details

push time in 5 months

issue commentewolff/microservice-kafka

project builds, but tests fail

I updated the documentation concerning the ports, see 8b7894a3985e441bb628b607131a26f6bf28a6e4 .

I reassured that in fact docker-compose build does work once the maven build has completed successfully. So I am afraid I cannot reproduce your problem.

DanStadlerNewRelic

comment created time in 5 months

push eventewolff/microservice-kafka

Eberhard Wolff

commit sha bd8cce803a6c064a87b55fd954c7006789669d51

Add remark concerning ports

view details

Eberhard Wolff

commit sha 49dffb94728227c6996a1e265b90c79a215c92ea

Update to Spring Boot 2.1.8

view details

push time in 5 months

issue commentewolff/microservice-kafka

docker compose fails

Please make sure the Maven build step works before building the Docker containers. The error is cause by the missions build artefacts of the Maven build, see #13 . Please reopen if this does not help.

DanStadlerNewRelic

comment created time in 5 months

issue closedewolff/microservice-kafka

docker compose fails

when trying out the docker compose section, I get this failure:

Building order Step 1/4 : FROM openjdk:11.0.2-jre-slim 11.0.2-jre-slim: Pulling from library/openjdk 27833a3ba0a5: Pull complete 16d944e3d00d: Pull complete 6aaf465b8930: Pull complete 0684138f4cb6: Pull complete 67c4e741e688: Pull complete 783178df3a0c: Pull complete Digest: sha256:da5605d071e9e41803f8b45f41f8c24ad6c26056190a871c8d6471982407d05b Status: Downloaded newer image for openjdk:11.0.2-jre-slim ---> b7a931ed7d37 Step 2/4 : COPY target/microservice-kafka-order-0.0.1-SNAPSHOT.jar . ERROR: Service 'order' failed to build: COPY failed: stat /var/lib/docker/tmp/docker-builder600758216/target/microservice-kafka-order-0.0.1-SNAPSHOT.jar: no such file or directory

closed time in 5 months

DanStadlerNewRelic

issue closedewolff/microservice-kafka

project builds, but tests fail

Hi, I wanted to try out your project, so cloned and tried out the how-to-run section. When the tests run after the build, there is a long period of getting these messages:

2019-09-30 19:51:25.888 WARN 88574 --- [ main] org.apache.kafka.clients.NetworkClient : [Consumer clientId=consumer-1, groupId=test] Connection to node -1 could not be established. Broker may not be available.

When the tests do end, this is the final output:

[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.234 s - in com.ewolff.microservice.order.kafka.OrderKafkaTest [INFO] [INFO] Results: [INFO] [ERROR] Errors: [ERROR] OrderServiceTest.lastCreatedIsUpdated » IllegalState Failed to load Applicatio... [INFO] [ERROR] Tests run: 5, Failures: 0, Errors: 1, Skipped: 0 [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] microservice-kafka ................................. SUCCESS [ 0.558 s] [INFO] microservice-kafka-order ........................... FAILURE [02:19 min] [INFO] microservice-kafka-shipping ........................ SKIPPED [INFO] microservice-kafka-invoicing ....................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 02:20 min [INFO] Finished at: 2019-09-30T19:43:11-07:00 [INFO] Final Memory: 42M/157M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.1:test (default-test) on project microservice-kafka-order: There are test failures. [ERROR] [ERROR] Please refer to /Users/dstadler/Documents/code/k8s-mcsvs-java/microservice-kafka/microservice-kafka/microservice-kafka-order/target/surefire-reports for the individual test results. [ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream. [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <goals> -rf :microservice-kafka-order C02Z65TVLVDQ:microservice-kafka dstadler$

closed time in 5 months

DanStadlerNewRelic

issue commentewolff/microservice-kafka

project builds, but tests fail

Please refer to the trouble shooting tips in the build section:

The tests use some ports on the local machine. Make sure that no server runs in the background.

Skip the tests: ./mvnw clean package -Dmaven.test.skip=true or mvnw.cmd clean package -Dmaven.test.skip=true (Windows).

Please reopen the issue if this doesn't work.

DanStadlerNewRelic

comment created time in 5 months

issue commentewolff/user-registration

Chef example (Chapter 3.3.2) doesn't work (Missing Role(s) in Run List)

@Electronic-Junkie This is actually expected. I clarified the documentation, see https://github.com/ewolff/user-registration-V2/tree/master/chef#chef-solo-on-ubuntu-1604 . Please open an issue in https://github.com/ewolff/user-registration-V2 if you feel this does not solve the problem.

jevin36

comment created time in 5 months

push eventewolff/user-registration-V2

Eberhard Wolff

commit sha 5f94317c32430987cadd3f8492211a9e1b947d04

Errata: Chef only works on Ubuntu 16.04

view details

Eberhard Wolff

commit sha 3b1057f27bbf6d02ba82e8cf062c991414a0fac4

Clarified Chef documentation

view details

push time in 5 months

push eventewolff/continuous-delivery-book.com

Eberhard Wolff

commit sha b5232da85799b94a42c1477afe6c648ae8a2e931

Add remark concerning Ubuntu version

view details

push time in 5 months

push eventewolff/user-registration-V2

Eberhard Wolff

commit sha 9e834cd35c379c8285a2c9fdd213b3d8a97e094b

Document how to build only the application. Fixes #9

view details

push time in 5 months

issue closedewolff/user-registration-V2

Fehlender Hinweis, wie Tests einzeln ausgeführt werden

Wenn man nicht alle Module am Anfang mit ./mvnw install installieren möchte, sondern die Tests nacheinander einzeln ausführen möchte, kann man nur die Applikation einzeln übersetzen mit

./mvnw -pl user-registration-application -am install

ein Hinweis hierzu fehlt in den READMEs

closed time in 5 months

kesselborn

push eventewolff/user-registration-V2

Eberhard Wolff

commit sha 80e25fcb0cef82c7ad08a1f6dc4febab2763b709

Accept Chef license

view details

push time in 5 months

issue commentewolff/microservice-kubernetes

how to access changes in index.html file

docker-build.sh should update the Docker images. Afterwards kubectl apply -f microservices.yaml should start the new version. As you are able to deploy the original version in this way, I don't see how there can be a bug in the demo as provided. Sorry.

Anuradha677

comment created time in 5 months

issue closedewolff/microservice-kubernetes

how to access changes in index.html file

Hi,

I need to change the index.html file. But I am not able to see the changes in application after deploy the application. I am using gcr.io for docker images. I am using cloud build for rolling update.I have changed the docker file and kubernetes.yaml in below forked directory. Anuradha677 / microservice-kubernetes

Please help me on this.

closed time in 5 months

Anuradha677

issue commentewolff/microservice-kubernetes

how to access changes in index.html file

You will need to build the docker images as discussed in https://github.com/ewolff/microservice-kubernetes/blob/master/HOW-TO-RUN.md#build-the-docker-images-optional and then run them https://github.com/ewolff/microservice-kubernetes/blob/master/HOW-TO-RUN.md#run-the-containers . I will close this issue for know. Please raise specific issues if you feel the documentation should be improved.

Anuradha677

comment created time in 5 months

pull request commentddd-referenz/ddd-referenz

Typo gefixt in Abschnitt "Domain Event"

Super, danke! 👍🙂

SSchwaiger

comment created time in 5 months

push eventddd-referenz/ddd-referenz

Sebastian Schwaiger

commit sha ca3baf0cc9191b3becf8f9c8bcc7571fb88fee9e

Typo gefixt in Abschnitt "Domain Event" (#40)

view details

push time in 5 months

issue commentddd-referenz/ddd-referenz

Begriff statt Konzept

Danke für das nette Feedback und den Issue!

https://dictionary.cambridge.org/dictionary/english/concept definiert concept als "principle or idea"

https://www.duden.de/rechtschreibung/Konzept spricht bon einem "skizzenhafter, stichwortartiger Entwurf, Rohfassung eines Textes, einer Rede" bzw "klar umrissener Plan, Programm für ein Vorhaben"

Es gibt da schon einen Unterschied, aber "Begriff" passt auf die Definition aus dem englischen Wörterbuch auch nicht. Ich bin daher nicht sicher, ob wir das wirklich so ändern sollten.

jenshimmelreich

comment created time in 5 months

pull request commentewolff/service-mesh-primer

Fix typo at microservices yaml

Great - thanks a lot for spotting!

erdlet

comment created time in 6 months

push eventewolff/service-mesh-primer

Erdle, Tobias

commit sha 2602a5cc71c66b7fbc0d4c9fbbe98455da309943

Fix typo at microservices yaml

view details

Eberhard Wolff

commit sha 3092b5e731dcd4d59f3e0fd35b1c66abc095dfc0

Merge pull request #16 from erdlet/fix-microservices-typo Fix typo at microservices yaml

view details

push time in 6 months

more