As the data tend to get over the software which was originally created to work with this data, choosing the data storage framework (as well as the basic data structures and serialization/deserialization mechanics) is one of the most important tasks in planning/drafting the specs/requirements for new software, systems integration or system upgrade.
We work with both SQL and NoSQL data storages. According to the technical requirements we can use either powerfull, reliable, structured SQL databases or faster-to-draft/scalable/reading/writing NoSQL data storages or a hybrid solution to work with both worlds. Our current and past projects have so far used Interbase/Firebird, PostgreSQL, Oracle, MS SQL, MySQL/MariaDB RDBMS on the SQL side, and MongoDB and RedisDB on the NoSQL side.
Linux, Apache, MySQL, PHP7, PostgreSQL, Python, Delphy, RabbitMQ, Swift, alamofire, moya, mbprogresshud, JavaSE, Kotlin, retrofit2, rxjava2, dagger2, android jetpack components, JS
The game portal had a huge number of automatic content checks. The information derived from scanning was used to get advances in gambling.