Wie sind die Öffnungszeiten?

Montag 09:00 - 18:00 Dienstag 09:00 - 18:00 Mittwoch 09:00 - 18:00 Donnerstag 09:00 - 18:00 Freitag 09:00 - 18:00

OpenResearch

Name: OpenResearch
Address: Biberstrasse 9/10, Wien, 1010, AT
Telephone: +431253599401

Startseite
Österreich
Wien
OpenResearch

We build digital products people love to use. Based in Vienna 🇦🇹, Prishtina 🇽🇰 & Croatia 🇭🇷.

13/10/2026

Java isn't flashy. It doesn't have the hype of newer languages. And that's exactly why it's still everywhere.

For enterprise systems that need to run for years, Java delivers:

☕ Massive ecosystem of battle-tested libraries
🏢 Talent pool that's deep and available
🔧 Tooling that's mature and powerful
📈 Performance that keeps improving (GraalVM, anyone?)
🛡️ Backward compatibility that respects investments

We use Java for backends that power critical business processes. When stability and maintainability matter more than excitement, Java is hard to beat.

It's not about old vs. new. It's about right tool for the job.

Is Java part of your tech stack?

12/10/2026

🚀 A milestone worth celebrating at OpenResearch!

We’re proud to announce that we’ve successfully achieved SIL 1 certification for a mobile application running on both iOS and Android!

Bringing functional safety requirements to mobile platforms is no small feat. It takes rigorous engineering, thorough testing, extensive documentation, and a strong commitment to quality.

This achievement demonstrates that modern mobile technology and demanding safety requirements can go hand in hand.

A big thank you to everyone involved for their dedication, expertise, and persistence throughout the process.

At OpenResearch, we love tackling complex engineering challenges - and this is one we're particularly proud of.

08/10/2026

GraphQL isn't REST's replacement. It's a different tool for different problems.

When GraphQL helps:

✅ Multiple clients need different data shapes
✅ Over-fetching is a real problem
✅ Rapid frontend iteration matters
✅ Strong typing benefits your workflow
✅ Real-time subscriptions are needed

When REST is fine:

✅ Simple CRUD operations
✅ Caching is critical (HTTP caching is simpler with REST)
✅ Team knows REST well
✅ Simple client needs

GraphQL complexity is real. N+1 queries, authorization per field, caching strategies - all need attention.

Tools like Apollo, Hasura, and Relay smooth the path. But understand the fundamentals first.

GraphQL is a powerful option, not a universal answer.

What's your API style preference?

06/10/2026

Three months left.

What will you accomplish? What will you ship? What will you learn?

Q4 is tricky. The holidays are coming, but so are year-end deadlines. Success requires intentional planning.

Our Q4 playbook:

📅 Front-load critical work before December holidays
🎯 Prioritize ruthlessly: not everything will ship
👥 Account for vacation and reduced capacity
📊 Set realistic milestones, not hopeful ones
🔒 Lock scope for anything that must ship this year

We've seen too many teams overpromise in October and scramble in December. Better to commit to less and deliver more.

What's your team's most important Q4 goal?

01/10/2026

As Angular apps grow, state management becomes critical.

Options for managing state:

📦 Services with BehaviorSubjects - simple, often enough
🔄 NgRx - Redux pattern, predictable but verbose
📊 NGXS - less boilerplate than NgRx
🎯 Signals - Angular's new reactive primitive
🔧 Component state - local when possible

NgRx shines when:

✅ State is shared across many components
✅ Complex async operations need coordination
✅ Time-travel debugging helps
✅ Team benefits from enforced patterns

NgRx is overkill when:

❌ State is mostly local
❌ Simple service injection works fine
❌ Team doesn't need the structure

Start simple. Add state management when pain emerges.

How do you manage state in Angular?

29/09/2026

Some software can afford to be down for maintenance. Roadside assistance apps cannot.

We've built systems for organizations like ÖAMTC and ADAC where reliability isn't a metric. It's a mission.

What we've learned about mission-critical systems:

🚨 Design for failure (because it will happen)
📊 Redundancy at every critical point
⚡ Fast recovery over perfect prevention
👀 Observability that catches problems early
🧪 Chaos engineering to verify resilience

When someone is stranded on a highway at night, the app must work.

These projects taught us that reliability is a feature you build in, not bolt on. Every architecture decision matters.

What's the most critical system your team maintains?

24/09/2026

Security isn't a feature you add later. It's built in from the start.

Practices that matter:

🔐 Input validation - never trust user input
🔒 Parameterized queries - SQL injection still happens
🎫 Least privilege - minimal permissions everywhere
📋 Dependency scanning - known vulnerabilities are free attacks
🔄 Secrets management - not in code, not in env files
📊 Security logging - know when something's wrong

OWASP Top 10 isn't outdated. The same vulnerabilities persist because the same mistakes persist.

Automated scanning catches known issues. Manual review catches logic flaws.

Security is everyone's responsibility. Not just the security team's.

Regular updates matter. Unpatched systems are easy targets.

What's your security practice?

22/09/2026

Software has a carbon footprint. Every inefficient query, every over-provisioned server, every unnecessary data transfer.

We're thinking more about sustainable engineering:

🌱 Right-sizing cloud resources (don't over-provision)
⚡ Efficient code that does more with less
🔄 Caching to reduce redundant computation
📊 Monitoring to catch waste
🌍 Choosing green cloud regions when possible

It's not just about the environment. Efficient systems are also cheaper to run.

The cloud makes scaling easy. That's also made waste easy. Time to be more intentional.

Small optimizations add up across millions of users and billions of requests.

Is sustainability on your engineering team's radar?

17/09/2026

Development without process is chaos. Too much process is paralysis.

What actually helps:

📋 Clear priorities - know what matters most
🔲 Small work items - easier to estimate, easier to complete
📊 Visible progress - boards everyone can see
🔄 Regular check-ins - short, focused, actionable
📝 Written requirements - assumptions become visible

Agile isn't the ceremonies. It's the principles. Responding to change. Working software. Collaboration.

Estimates are guesses. Acknowledge uncertainty. Ranges beat point estimates.

Technical debt is a project management concern. Make it visible. Budget time for it.

The best process is the one your team actually follows.

How does your team manage work?

15/09/2026

What if every deployment was just a Git merge?

That's the promise of GitOps, and it works.

How GitOps changes operations:

📝 Infrastructure and app config in Git
🔄 Automatic sync to cluster state
📋 Audit trail for every change
🔙 Rollback is just git revert
👥 Developers don't need cluster access

We've spoken at DevFest Vienna about our GitOps journey. The learning curve is real, but the operational stability is worth it.

Tools like ArgoCD and Flux make this practical. Combined with Terraform for infrastructure, you get a fully declarative, version-controlled system.

No more kubectl apply from laptops. No more wondering what's running in production.

Is your team exploring GitOps?

Adresse

Biberstrasse 9/10
Wien
1010

Öffnungszeiten

Montag	09:00 - 18:00
Dienstag	09:00 - 18:00
Mittwoch	09:00 - 18:00
Donnerstag	09:00 - 18:00
Freitag	09:00 - 18:00

Telefon

+431253599401

Website

http://www.openresearch.com/

Benachrichtigungen

Erfahren Sie als Erste/r von Neuigkeiten und Aktionen: Wir schicken Ihnen eine E-Mail, wenn OpenResearch etwas veröffentlicht. Ihre E-Mail-Adresse wird für keinen anderen Zweck verwendet, und Sie können sich jederzeit abmelden.