Rate this app:

More details

Add your questions or answers

Q: How to get the best score?

Q: What is your favourite trick in this game/app?

Q: What is your strategy?

Softonic Gameplay, Trailers and Related Videos

About the application:

Softonic is the world's biggest tool and apk discovery destination and one of the world's most highly-trafficked sites. You have probably landed on their site when you need to download something - and you are not the only one. Over 100 million players are reaching Softonic - per month. It’s an apk tutorial that helps you explore the best apks for your device, offering you reviews, news, articles and gratis downloads. CloudAMQP provides hosted RabbitMQ clusters, in all the largest data centers all over the globe and Softonic is one of our a lot of customers. We met up with Riccardo Piccoli, a developer at Softonic, at the RabbitMQ Summit 2018 in London where he kindly shared Softonic’s customer story with us. This article is broken down into two pieces; the first part is an overview of the system, which shows a easy RabbitMQ use cases of an event-based architecture. The second part is a deep-dive into the internal architecture in Softonic - plugins they are using and examples of happenings they are sending. A easy RabbitMQ use case Users can upload files to Softonic. All uploaded files are scanned for virus and info about the file is collected, before the file is distributed to another players. The fresh binary data is, first of all, persisted within a dedicated service, and a notification about the upload is sent to an happening bus. Another services collect this info which in the end will be added to the site. In this case, the player gets notified straight after the upload has succeeded and a scanning happening is simply placed on an event-bus for another services to handle. An happening bus, also called notice queue, allows web servers to answer to requests quickly instead of being forced to perform a resource-heavy process on the spot, and instead of keeping the player waiting. The scanning process is one of those services. The virus scanning application takes a notice of the happening bus, such as a “ScanFile” command and starts the processing of the file. At the same time, another players are able to upload fresh files to Softonic and processing tasks are just piling up in the queue. The happening “FileScanned” is added back to the event-bus, once the consuming application has handled the event. The tool and apk discovery portal Softonic is reached by over 100 million players per month, delivers more than 2 million downloads per day and has a constant flow of happenings and commands between their services. CloudAMQP met up with Softonic to hear their story on how RabbitMQ, as an happening bus between microservices, contributes to a reliable, quick and effective architecture excellent for their purpose. An architecture like this creates two easy apks and low coupling between the sender and the receiver. Players can still upload files, even if the scanning application is busy or is under maintenance. Different happenings or commands are published to the happening bus, e.g., a “ScanFile” command. Softonic is using RabbitMQ as an happening bus, happenings or commands are simply added to the queue. The consuming application retrieves the happening and starts to process the happening. Some data is stored to the database, and more happenings might be published back to other happening queue (more about this in “Internal Structure of RabbtiMQ”). The consuming application stores lot’s of info in a database (MySQL). When a microservice receives an happening, it can modernize its own business entities, which might lead to more happenings being published, and that is exactly the case here. Internal Structure of RabbitMQ It’s time for a deep-dive into the internal architecture of RabbitMQ, and into the Softonic Application. Two RabbitMQ concepts need to be described if you are not already familiar with them. Softonic is using the consistent hash exchange plugin and RabbitMQ sharding. asynchronously Happening 0 will be processed straight away, happening 1,2 and 3 will be re-published to the queue so that another sharded consumers can process them.