OpenResearch

If you haven't looked at .NET recently, you're missing out.

What modern .NET delivers:

⚡ Performance that competes with Go and Rust
🌍 True cross-platform: Linux containers, ARM, everywhere
📦 Minimal APIs - less ceremony, more productivity
🔥 Hot reload during development
☁️ Cloud-native by design
NET 8+ brought native AOT compilation. Startup times dropped dramatically. Memory footprint shrank.

ASP.NET Core handles millions of requests per second. Benchmarks put it near the top.

The tooling matured. The ecosystem grew. The community expanded beyond Windows shops.

For new projects, modern .NET deserves consideration regardless of your current stack.

What's your impression of .NET today?

Everyone uses Git. Not everyone uses it well.

Workflow practices that make a difference:

🌿 Small, focused branches - easier to review, easier to merge
📝 Meaningful commit messages - future you will thank you
🔄 Rebase for clean history, merge for collaboration
🔒 Protected main branch - always deployable
🧪 CI runs on every push - catch issues early

Conventional commits help automation. Semantic versioning communicates change impact. Good branch naming explains intent.

Git is a tool for collaboration. Your workflow should reduce friction, not create it.

The best workflow is the one your team actually follows. Complexity without compliance is worse than simplicity.

Start simple. Add process when pain points emerge.

What Git practices does your team follow?

Microservices solve organizational problems, not just technical ones.

When microservices actually help:

👥 Multiple teams need to deploy independently
📈 Different services have different scaling needs
🔧 Technology diversity is genuinely beneficial
🚀 Deployment frequency varies significantly by component

When they hurt:

❌ Small team trying to manage distributed complexity
❌ Premature optimization before understanding the domain
❌ Network calls where function calls would work
❌ Distributed debugging without distributed tracing

Start with a modular monolith. Extract services when you have clear reasons and the operational maturity to manage them.

The infrastructure overhead is real. The debugging complexity is real. The benefits are also real - when the context is right.

Most systems don't need microservices. Some genuinely do.

What's your architecture approach?

Sometimes you need messages delivered reliably. ActiveMQ has done this for decades.

Why ActiveMQ remains relevant:

📨 JMS compliance for Java enterprise
🔄 Multiple protocols: AMQP, STOMP, MQTT, OpenWire
🏢 Battle-tested in enterprise environments
📊 Flexible messaging patterns: queues and topics
🔧 Manageable complexity

ActiveMQ Classic for traditional deployments. Artemis for the next generation with better performance and clustering.

For Java shops using JMS, ActiveMQ is the natural choice. The integration is seamless.

Kafka handles event streaming at scale. ActiveMQ handles point-to-point messaging with guaranteed delivery. Different tools, different jobs.

Not every system needs Kafka's complexity. Sometimes a reliable message queue is exactly right.

What's your messaging strategy?