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 🇭🇷.

03/09/2026

Redis is often added as a cache. Then you discover what else it can do.

Use cases beyond caching:

📊 Leaderboards - sorted sets make ranking trivial
🔔 Pub/Sub - real-time notifications
📋 Task queues - lists with blocking pops
🗺️ Geospatial - location-based queries
🔢 Rate limiting - atomic increments with TTL
📈 Time series - with Redis TimeSeries module

Each data structure solves specific problems elegantly. Sorted sets for ranking. HyperLogLog for cardinality. Streams for event logs.

Redis Cluster scales horizontally. Redis Sentinel provides high availability.

The speed is remarkable. Sub-millisecond latency for most operations.

Before adding another database, check if Redis already solves the problem.

What's your favorite Redis use case beyond caching?

01/09/2026

Summer's winding down. Teams are back at full capacity.

There's a certain energy in September, almost like a second January. A fresh start feeling.

It's the perfect time to ask:

📋 What's been sitting in your backlog all summer?
🚧 Which technical debt have you been avoiding?
🎯 What ambitious goal could you achieve by year-end?
👥 Does your team have the capacity to make it happen?

September through November is often the most productive period of the year. The holidays haven't hit yet, teams are focused, and there's still time to finish something meaningful.

Don't waste this momentum.

What's the one thing you want to ship before the year ends?

27/08/2026

API Gateways sit at the edge. They handle cross-cutting concerns so your services don't have to.

What gateways provide:

🚦 Routing - direct requests to the right service
🔐 Authentication - verify identity once
⚡ Rate limiting - protect backend services
📊 Observability - centralized logging and metrics
🔄 Protocol translation - REST to gRPC, etc.

Gateway options: Kong, NGINX, AWS API Gateway, Azure API Management. Cloud-native or self-hosted - both work.

Keep gateways thin. Business logic belongs in services. Gateways handle infrastructure concerns.

Gateway failures affect everything. Design for resilience. Consider multiple gateways for different clients.

The right abstraction simplifies both client and service development.

How do you handle API gateway concerns?

25/08/2026

Microservices are not automatically better than monoliths.

There. We said it. Now let's talk about when each actually makes sense.

We've built both. Here's when each makes sense:

**Microservices work when:**
🔄 Different components need independent scaling
👥 Multiple teams need to deploy independently
📈 You're at a scale where monolith coupling hurts

**Monoliths work when:**
🏃 You're moving fast and need simplicity
👤 Small team, clear ownership
📊 Traffic patterns don't require differential scaling

The worst outcome? A distributed monolith: all the complexity of microservices with none of the benefits.

Start simple. Split when you have a real reason. Every boundary you add is a boundary you maintain.

What's been your experience with microservices?

20/08/2026

Code is read more than written. Optimize for reading.

Principles that improve every codebase:

📝 Meaningful names - reveal intent, not implementation
🔲 Small functions - do one thing well
📋 Comments explain why, not what
🧹 Remove dead code - it only confuses
🔄 DRY, but not religiously - some duplication is fine

Clean code isn't about following rules blindly. It's about empathy for the next developer.

Refactor continuously. Small improvements compound. The best time to clean is during regular work.

Code reviews catch issues, but they also teach. Use them to spread good practices.

Readability beats cleverness every time.

What clean code principles matter most to you?

18/08/2026

Clicking around in cloud consoles? That's how production incidents happen.

Infrastructure as Code (IaC) means your cloud resources are version-controlled, reviewable, and repeatable.

Why we standardize on Terraform:

📝 Cloud-agnostic (AWS, Azure, GCP)
🔄 State management that actually works
👥 Code review for infrastructure changes
📋 Documentation through code
🔁 Reproducible environments

"But it takes time to learn!" Yes. Less time than debugging why staging works but production doesn't.

We provision everything through code. Servers, databases, networks, IAM policies - all of it. The initial investment pays dividends immediately.

Is your infrastructure in code yet?

14/08/2026

New on YouTube 🚨
*Building with Apple Intelligence: Create Private, On-Device AI Apps for iOS* 🍎🤖

What if you could build AI-powered iOS apps without sending user data to the cloud?

In this OpenResearch Mobile Meetup session, Armend Bellalari explores how to leverage Apple Intelligence and on-device AI to create fast, privacy-first user experiences.

Using the TravelGuard AI proof of concept, the session covers how Apple's latest AI capabilities can power natural language features while keeping processing entirely on the device.

Highlights include:
• Apple Intelligence architecture and privacy-first design
• Foundation Models and the Neural Engine
• Natural language processing with NLTagger
• App Intents, Siri, Spotlight, and Shortcuts integration
• Intent ranking and matching
• SwiftUI implementation details
• Building an AI-powered service finder from the ground up

Whether you're exploring Apple Intelligence or looking to integrate on-device AI into your next iOS app, this talk offers practical insights and implementation guidance.

▶️ Watch the full session: https://youtu.be/zt4rJ1AQIAU

How are you planning to use Apple Intelligence in your iOS applications? We'd love to hear your ideas in the comments.

13/08/2026

Databases change. Managing those changes matters.

Migration practices that work:

📋 Version controlled migrations - track every change
🔄 Idempotent scripts - safe to run multiple times
⬆️ Forward only - avoid down migrations in production
🧪 Test migrations against production-like data
🚀 Run migrations before deploying code

Tools that help: Flyway, Liquibase, Alembic, Rails migrations. Pick one that fits your stack.

Large table migrations need care. Online DDL, shadow tables, gradual rollouts. Locking production tables is not acceptable.

Separate schema changes from data changes. Different risks, different timing.

Never modify a deployed migration. Create a new one instead.

Database changes deserve as much rigor as code changes.

What's your migration strategy?

11/08/2026

Cars are becoming computers on wheels. And that creates entirely new challenges.

For over 10 years, we've worked with automotive leaders to build connected vehicle solutions. Here's what we've learned:

🚗 Reliability is non-negotiable
📊 Scale means millions of data points per second
🔐 Security is paramount (vehicles are safety-critical)
⚡ Latency matters for real-time features
🔧 Systems must evolve over decades, not years

Working with companies like Porsche and Volkswagen Group has taught us that automotive-grade software requires a different mindset.

The intersection of automotive and software is one of the most exciting spaces in tech. And we're proud to be part of it.

Are you working on connected mobility solutions?

06/08/2026

Kotlin Multiplatform takes a different approach: share the logic, keep the UI native.

Why KMP is gaining traction:

🔄 Share business logic across Android, iOS, Desktop, Web
📱 Native UI on each platform - no compromise on UX
🛠️ Gradual adoption - start with one shared module
⚡ Native performance - compiles to platform-native code
🧪 Shared tests for shared code

What you typically share:

✅ Networking and API clients
✅ Data models and validation
✅ Business rules and calculations
✅ Local storage and caching
✅ State management

What stays platform-specific:

📱 UI layer - SwiftUI on iOS, Compose on Android
🔧 Platform APIs - camera, sensors, notifications

The sweet spot: teams that know Kotlin and want native UX without duplicating business logic.

JetBrains and Google are investing heavily. The ecosystem is maturing fast.

Have you explored Kotlin Multiplatform?

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

Webseite

http://www.openresearch.com/

Benachrichtigungen

Lassen Sie sich von uns eine E-Mail senden und seien Sie der erste der Neuigkeiten und Aktionen von OpenResearch erfährt. Ihre E-Mail-Adresse wird nicht für andere Zwecke verwendet und Sie können sich jederzeit abmelden.