Skip to content

updating links inside architecture folder to https #15476

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Oct 29, 2019
Merged

updating links inside architecture folder to https #15476

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
ee93a3e
updating links inside architecture folder to https
eddynaka Oct 28, 2019
1e4f9e6
Update docs/architecture/microservices/multi-container-microservice-n…
eddynaka Oct 28, 2019
f0269a0
updating to new link
eddynaka Oct 28, 2019
de1c33e
Merge branch 'updating-architecture-to-https' of https://github.com/e…
eddynaka Oct 28, 2019
ce6ada8
Update docs/architecture/microservices/multi-container-microservice-n…
eddynaka Oct 29, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/architecture/cloud-native/identity-server.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,7 @@ Many cloud-native applications leverage server-side APIs and rich client single

## References

- [IdentityServer documentation](http://docs.identityserver.io/)
- [IdentityServer documentation](http://docs.identityserver.io/en/latest/)
- [Application types](https://docs.microsoft.com/azure/active-directory/develop/app-types)
- [JavaScript OIDC client](http://docs.identityserver.io/en/latest/quickstarts/6_javascript_client.html)

Expand Down
4 changes: 2 additions & 2 deletions ...microservices/multi-container-microservice-net-applications/subscribe-events.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -100,7 +100,7 @@ As mentioned earlier in the architecture section, you can have several approache

- Using [transaction log mining](https://www.scoop.it/t/sql-server-transaction-log-mining).

- Using the [Outbox pattern](http://gistlabs.com/2014/05/the-outbox/). This is a transactional table to store the integration events (extending the local transaction).
- Using the [Outbox pattern](https://www.kamilgrzybek.com/design/the-outbox-pattern/). This is a transactional table to store the integration events (extending the local transaction).

For this scenario, using the full Event Sourcing (ES) pattern is one of the best approaches, if not *the* best. However, in many application scenarios, you might not be able to implement a full ES system. ES means storing only domain events in your transactional database, instead of storing current state data. Storing only domain events can have great benefits, such as having the history of your system available and being able to determine the state of your system at any moment in the past. However, implementing a full ES system requires you to rearchitect most of your system and introduces many other complexities and requirements. For example, you would want to use a database specifically made for event sourcing, such as [Event Store](https://eventstore.org/), or a document-oriented database such as Azure Cosmos DB, MongoDB, Cassandra, CouchDB, or RavenDB. ES is a great approach for this problem, but not the easiest solution unless you are already familiar with event sourcing.

Expand Down Expand Up @@ -321,7 +321,7 @@ If the “redelivered” flag is set, the receiver must take that into account,
<https://go.particular.net/eShopOnContainers>

- **Event Driven Messaging** \
[http://soapatterns.org/design\_patterns/event\_driven\_messaging](http://soapatterns.org/design_patterns/event_driven_messaging)
<https://patterns.arcitura.com/soa-patterns/design_patterns/event_driven_messaging>

- **Jimmy Bogard. Refactoring Towards Resilience: Evaluating Coupling** \
<https://jimmybogard.com/refactoring-towards-resilience-evaluating-coupling/>
Expand Down