SDL Worldserver Reviews

The most important advantages are saving time and resources. Automated translation service is a game-changer for businesses seeking efficient localization solutions. Its advanced technology delivers accurate translations quickly, saving time and resources. The platform's user-friendly interface and seamless integration make it a valuable asset for global communication and content dissemination. While some nuances may still require human touch, their automated translation service proves to be a reliable tool for enhancing multilingual content workflows. We have enjoyed how efficient it is.

Despite its strengths, it does come with a few disadvantages. One notable drawback is its dependency on machine translation, which can occasionally result in inaccuracies or missed nuances, especially for complex or specialized content. Additionally, while the platform offers integration options, some users might find the setup process to be somewhat intricate, requiring technical expertise. Another consideration is that the cost of using WorldServer's services may add up over time, particularly for extensive translation needs. Lastly, the support for certain languages or dialects might be limited, potentially posing a challenge for businesses targeting less commonly spoken languages.

WorldServer's integration capabilities facilitate smoother collaboration among global teams and departments, enhancing overall workflow and reducing potential bottlenecks.

In essence, WorldServer's solutions address the challenges of efficient, accurate, and timely translation, resulting in improved communication, expanded market presence, and enhanced operational efficiency for our businesses.

• High Availability. WorldServer provides a multi-node cluster to ensure high availability and seamless failover.

• High Scalability. WorldServer supports dynamically adding or removing nodes to easily handle high concurrent traffic.

• Strong Consistency. WorldServer uses the Raft consensus algorithm to guarantee strong consistency and data synchronization.

• High Performance. WorldServer uses RocksDB as the storage engine, and each node can handle up to tens of thousands of QPS.

• Automatic Pruning. WorldServer can automatically delete or compress historical data based on access frequency to maintain high performance.

• High Complexity. As a distributed database, WorldServer has a relatively complex architecture and operations.

• High Resource Consumption. To ensure high availability, WorldServer requires more computing, storage and network resources.

• No SQL Support. WorldServer is a NoSQL database and does not support traditional SQL queries.

• Steep Learning Curve. WorldServer has its own set of query syntax and client libraries, requiring developers to invest time to learn.

• Unstability. As a relatively new distributed NoSQL product, WorldServer is not as stable as mature products like MySQL.

WorldServer is a distributed NoSQL database, helps us solve typical scalability, high availability, consistency and high performance requirements in the big data era. Using it enables our system and business to have elastic scalability, always-on availability and fast response capabilities. The value and benefits are obvious.

Extremely Reliable. WorldServer's multi-node cluster guarantees continuous uptime and instantaneous failover.

Incredibly Scalable. WorldServer allows you to quickly manage heavy concurrent traffic by adding or removing nodes on the fly.

High reliability. Raft is a consensus mechanism used by WorldServer to ensure reliable data consistency and synchronisation.

Superior Efficiency. Each node of WorldServer is capable of handling tens of thousands of queries per second (QPS) thanks to RocksDB, its storage engine.

Auto-Pruning System. In order to keep WorldServer running smoothly, it can remove or compress data from the past on the basis of how often it is accessed.

Extremely Complicated. WorldServer is a distributed database with a sophisticated design and set of procedures.

Large amounts of material are used. WorldServer needs more CPU time, storage space, and network bandwidth to guarantee high availability.

• SQL is not supported. Since it is a NoSQL database, WorldServer cannot process SQL statements.

• A Great Deal of Trial and Error Required to Master. Developers must spend time learning WorldServer's unique query syntax and client libraries.

• Uncertainty. WorldServer lacks the reliability of more established distributed NoSQL solutions like MySQL because of its infancy.

We can meet the common big data era challenges of scalability, high availability, consistency, and performance with the help of WorldServer, a distributed NoSQL database. Our system and company may take advantage of elastic scalability, continuous availability, and lightning-fast response times thanks to its use. It's easy to see the benefits and value.

SDL Worldserver is a powerful and capable tool. It gets the job done and it has a lot of functionalities. Once you learn how to use it you cannot go wrong with your workflow. There are a lot of connectors.

That being said, there is a steep learning curve, and the user interface is bloated and not intuitive at all, as it is with all SDL products. The API is somewhat buggy, and sometimes the connectors don't work the way they are supposed to.

SDL Worldserver gets the job done, and if your client already uses Trados or another SDL tool, Worldserver is the way to go. If you're still in the implementation phase of your company, you could consider other options that are easier to use and less buggy.

Translation Memory management.

It does the job it's supposed to do and offers a wide range of functionalities. There is an API for integration with other systems and you can develop and deploy your own packages. The workflow designer is very simple and easy to use.

There are bugs particularly with the Integration API - and the documentation of the API does not always correspond to the actual way that the API works. You do need the support of SDL to get around the bugs btw such as UI related functionalities that are not described in the API - even though they may be supported in an un-intuitive way. Another negative point is that when something goes wrong the logs are hard to understand. Finally, the UI is really outdated.

I am confident that the future releases will be of better quality.

For the time being keep a good support contract with SDL to make sure you don't face problems.

Translation Memories, Translation functionalities on an enterprise level, Generating SDL projects.