FAQ
From Online MQ
Here are some frequently asked questions from our customers :
- What is OnlineMQ?
- OnlineMQ offers a cloud reliable message queue for storing messages as they travel between computers. By using OnlineMQ, developers can simply move data between distributed application components performing different tasks, without losing messages or requiring each component to be always available.
- How secure is the service?
- We use SSL for our GUI (Authenticate with user & password)
- You may choose to send messages via secure https or via http, all with strict authentication of account (user name and password).
- In addition Queue Managers & Queue owners can control which OnlineMQ users are allowed to write messages to or read messages from their queue.
- Account administrator can use IP authorization in order to block unauthorized IP's to send messages.
- How does OnlineMQ handle failures in message processing?
- With OnlineMQ you can choose to use a simple send message or choose for transaction session that apply a handshake method. Most of the time (like any message bus supporting http / https) each message will be delivered exactly once, and after it is read from the queue it will be processed and deleted before another process can read it.
- Does OnlineMQ guarantee message delivery?
- Our product lives or dies based on whether or not we get the messages you want, to you, so we do our best to make sure that always happens. We have a clustered, load-balanced, system with replicated nodes and various failovers.
- What kind of libraries/Application do you supply?
- Tester client - Test your account immediately. (send and receive messages/files)
- File Transfer - a demon that sends files from a specific folder toward a predefined queue
- Java sources - open source wsdl libraries.
- How long can I keep my messages in a queue?
- OnlineMQ users may keep their messages in a queue for as long as needed (depend on the package purchased) , normally it is up to 7 days. OnlineMQ is designed to provide transient storage for messages waiting to be processed, rather than for long-term data storage.
- What time response can we expect ?
- Our goal is to ensure you have access to messages within 20 seconds for 10KB message and 40 seconds for larger messages. Usually it's much faster.
- How reliably is my data stored in OnlineMQ?
- OnlineMQ stores all queue and message information in redundend data storage in the biggest cloud unix datacenter in the world (joyent). OnlineMQ's network is highly reliable, highly available data centers.
- How much and what kind of data can I contain within a message I send to a queue?
- OnlineMQ messages can contain up to 256 KB of data & files including XML...etc
- How big can queues be?
- A single queue may contain an unlimited number of messages, and a developer may create an unlimited number of queues.
- How do I interface with OnlineMQ?
- OnlineMQ provides simple, standards-based REST, SOAP (WSDL) interfaces that are designed to work with any Internet-development toolkit. The operations are intentionally made simple to work with messages and queues.
- Why OnlineMQ is better then developing an "in-house" solution
- Why should you as an application developer worry about these low-level communication and queuing issues when you should be worrying about how to solve your business problems. A lot of effort and time is put into the Online MQ and it will save you a lot of coding and maintenance time for a reasonable amount of money.
- These alternatives require significant upfront time to develop and configure compared to integrating with an existing web service. Also, these alternatives would require ongoing hardware and system administrative resources to operate. The complexity of configuring and managing these systems is compounded if they need to be configured to provide redundant storage of messages so they are not lost if hardware fails.