Whereby (formerly appear.in)

Website

whereby.com

Pricing URL

Official Whereby (formerly appear.in) Pricing

Release Date

2017 January

Categories

#Communication #Video Conferencing #Group Chat & Notifications #Online Meetings

Startup details

Country

Norway

State

Oslo

City

Oslo

Founder(s)

Ingrid Ødegaard

Employees

50 - 99

@imqueue

Website

imqueue.org

Pricing URL

-

Release Date

-

Categories

#Developer Tools #Realtime Backend / API #Tech #App Development #Data Integration #Web Service Automation

Whereby (formerly appear.in) features and specs

• Ease of Use
  Whereby is extremely user-friendly and does not require any software installation, making it accessible to users with varying levels of technical proficiency.
• No Account Required for Guests
  Guests can join meetings without creating an account, which simplifies the process for participants who may be less tech-savvy or pressed for time.
• Browser-Based
  As a browser-based application, Whereby works on multiple platforms, including Windows, Mac, Linux, and mobile devices, thus providing great flexibility.
• Customizable Room Links
  Users can create personalized room links that are easy to remember and share, increasing convenience for both hosts and participants.
• Integrated Tools
  It offers built-in tools such as screen sharing, meeting recording, and chat, providing a rich feature set for collaboration.
• Security
  Whereby rooms are private and require permission to join, providing a secure environment for meetings.

Possible disadvantages of Whereby (formerly appear.in)

• Limited Free Plan
  The free version of Whereby limits meetings to 45 minutes and only supports up to 4 participants, which might be restrictive for larger teams or longer meetings.
• Performance
  Performance can sometimes be less reliable compared to some other video conferencing tools, potentially leading to connection issues or lag during meetings.
• Fewer Integrations
  Whereby offers fewer third-party integrations compared to competitors like Zoom or Microsoft Teams, which may limit its utility for businesses that rely on integrated workflows.
• Cost for Premium Features
  Many of the more advanced features, such as meeting recording and increased participant limits, are locked behind a paywall, which may not be cost-effective for individuals or small businesses.
• Mobile App Limitations
  While it is mobile-friendly, the experience on mobile devices is not as robust as on desktops, and some features may be limited or harder to use.

@imqueue features and specs

• TypeScript-first design
  imqueue is built with TypeScript at its core, providing strong typing, better IDE support, and compile-time error checking, which helps catch bugs early and improves the developer experience when building microservices.
• RPC-style messaging abstraction
  It simplifies inter-service communication by abstracting away the complexities of message queue protocols, allowing developers to make calls that feel like local function calls while the underlying complexity of message passing is handled by the framework.
• Built on RabbitMQ
  By leveraging RabbitMQ as its message broker, imqueue benefits from a mature, battle-tested messaging system with reliable delivery guarantees, clustering support, and a large ecosystem of tools and documentation.
• Code generation and tooling
  imqueue provides CLI tools and code generation capabilities that can automatically create service clients and boilerplate code, reducing repetitive work and helping maintain consistency across microservices.
• Microservices-focused architecture
  The framework is specifically designed for building distributed microservices systems, offering features like service discovery and structured communication patterns that address common challenges in distributed system design.

Possible disadvantages of @imqueue

• Smaller community and ecosystem
  Compared to more mainstream microservices frameworks, imqueue has a relatively small user base and community, which can mean fewer third-party resources, tutorials, Stack Overflow answers, and community-contributed plugins or extensions.
• Limited documentation depth
  While basic documentation exists, some users report that advanced use cases, edge cases, and troubleshooting guides are not as thoroughly documented as more established frameworks, requiring more trial-and-error or direct code inspection.
• RabbitMQ dependency lock-in
  Being tightly coupled to RabbitMQ means teams must adopt and manage this specific message broker, which could be a limitation for organizations that prefer or already use alternative messaging systems like Kafka, NATS, or AWS SQS.
• Learning curve for framework-specific patterns
  Developers need to learn imqueue's specific conventions, decorators, and architectural patterns, which adds an additional learning curve on top of understanding TypeScript and general microservices concepts.
• Potential scalability concerns for very large systems
  As with many queue-based RPC frameworks, extremely high-throughput or very large-scale distributed systems may encounter performance bottlenecks or require significant additional configuration and tuning of the underlying RabbitMQ infrastructure.

Analysis of Whereby (formerly appear.in)