Blog
Mert Özen's blog posts on software development, backend, frontend, and DevOps.
Testing Microservices: Service Tests, End-to-End Tests with Aspire and Contract Tests
In microservices the weight of testing sits at the service boundary: Ordering is tested against a real SQL Server and RabbitMQ with Testcontainers, and the saga conflict from post 07 happens 9 times in 10 runs and stays consistent through retries. Event schemas are checked with JSON Schema snapshots, the BFF–Catalog HTTP contract with Pact, and one checkout runs end to end with Aspire.Hosting.Testing, waiting for the push.
Containers and Deployment: SDK Container Builds, Kubernetes and an Independent Pipeline per Service
Images are built without a Dockerfile, with dotnet publish /t:PublishContainer on a chiseled base and a non-root user; Angular goes into the BFF's image. The preview aspire publish produces a valid Helm chart but turns migrators into Deployments and adds no probes; the post covers hand-written Kustomize manifests, the data loss seen on kind, the managed infrastructure decision and a GitHub Actions pipeline per service with path filters.
Looking Back: Distributed Monolith Symptoms, Costs and What We Would Merge Again
Bookstore's microservice version did not turn into a distributed monolith: shared code stayed at 68 lines of contracts and checkout has a single synchronous step, but the central package file triggers every pipeline on each change. Compared with the monolith, application memory is 7.4 times larger and the order request's p50 went from 5.8 ms to 22.7 ms; we would merge Notifications into the BFF and keep Payments separate.