Airline-Microservices
community
Airline-Microservices | community | |
---|---|---|
7 | 7 | |
334 | 700 | |
- | 1.4% | |
8.5 | 9.0 | |
about 2 years ago | about 16 hours ago | |
C# | Python | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Airline-Microservices
- Airline-Microservices: This application based on different software architecture and technologies like .Net Core, CQRS, DDD, Vertical Slice Architecture, Docker, kubernetes, tye, masstransit, RabbitMQ, Grpc, yarp reverse proxy, Identity Server, Redis, SqlServer, Entity Framework Core, gRPC.
- Implementing an Airline microservices sample with DDD, CQRS, Messaging, Distributed Tracing (masstransit, rabbitmq , outbox pattern, open telemetry)
- Airline microservices sample (ddd, cqrs, masstransit, rabbitmq , outbox pattern, open telemetry, event sourcing)
- Implementing an Airline microservices application with DDD, CQRS, Messaging, Distributed Tracing (masstransit, rabbitmq , outbox pattern, open telemetry, event sourcing)
community
-
All you need is Wide Events, not "Metrics, Logs and Traces"
otel is working on their events spec https://github.com/open-telemetry/community/issues/1688
- Open-Telemetry Donation Proposal: Continuous Profiling Agent
- Elastic offers donation of profiling agent to OpenTelemetry project
-
OpenTelemetry in 2023
1. Agreed. It's the sink and the house attached to it, and the docs are thin and confusing as a result.
2. I had a similar experience to you. I wanted to implement a simple heartbeat in our app to get an idea of usage numbers. This is surprisingly not possible, which greatly confuses me given the name of the project. The low engagement on my question put me off and I abandoned my OpenTelemetry planning completely. [1][2]
[1] https://github.com/open-telemetry/community/discussions/1598
- Decision about public video recordings
-
Frontend Overhaul of OTel Demo: Go to Next.js
One of the OpenTelemetry Project's many Special Interest Groups (SIG) is the OpenTelemetry Community Demo SIG which gives support to a set of instrumented backend microservices and a web frontend app that are primarily used to showcase how to instrument a distributed system using OpenTelemetry. The application's main focus is to demonstrate the implementation process to instrument an application no matter what programming language, platform, or operating system your team is using, as well as providing different approaching techniques (automatic and manual instrumentation, metrics, baggage). All of this while following the standards and conventions defined by the official OpenTelemetry Documentation. More about the specific requirements can be found here. At Tracetest, we have always focused on becoming part of and embracing the OpenTelemetry community. One of our goals this summer was to get more involved with a core OpenTelemetry project where we could provide a meaningful contribution. The OTel demo became the best match for achieving that goal as it would not only help the community, but we at Tracetest needed a good example to test and showcase what can be done with our tool. During the version 0.7 project cycle, we created two specific tickets to get us closer to the community and start looking for things to pick up:
- community/mission-vision-values.md at main ยท open-telemetry/community
What are some alternatives?
pitstop - This repo contains a sample application based on a Garage Management System for Pitstop - a fictitious garage. The primary goal of this sample is to demonstrate several software-architecture concepts like: Microservices, CQRS, Event Sourcing, Domain Driven Design (DDD), Eventual Consistency.
trouble-training - FullStack DDD/CQRS with GraphQL workshop including distributed tracing and monitoring. This shows the configuration from React frontend to .Net backend.
thalo - An Event Sourcing runtime with WebAssembly & embedded event store
b3-propagation - Repository that describes and sometimes implements B3 propagation
example-voting-app - Example distributed app composed of multiple containers for Docker, Compose, Swarm, and Kubernetes
docs - Prometheus documentation: content and static site generator
booking-microservices-sample - Booking Microservices is a Sample application for booking ticket. This application based on different software architecture and technologies like .Net Core, CQRS, DDD, Vertical Slice Architecture, Docker, kubernetes, tye, masstransit, RabbitMQ, Grpc, yarp reverse proxy, Identity Server, Redis, SqlServer, Entity Framework Core, Event Sourcing and different level of testing. [Moved to: https://github.com/meysamhadeli/booking-microservices]
tracetest - ๐ญ Tracetest - Build integration and end-to-end tests in minutes, instead of days, using OpenTelemetry and trace-based testing.
booking-modular-monolith - Practical Modular Monolith, built with .Net, DDD, CQRS, Vertical Slice Architecture, Event-Driven Architecture, and the latest technologies.
opentelemetry-proto - OpenTelemetry protocol (OTLP) specification and Protobuf definitions
ecommerce-microservices - ๐๏ธ A practical e-commerce Microservices based on Domain Driven Design, Vertical Slice Architecture, CQRS pattern, Event Driven Architecture.
odigos - Distributed tracing without code changes. ๐ Instantly monitor any application using OpenTelemetry and eBPF