"The farmer" is a video processing tool that has been leading the bussiness for decades, it has a great support for multiple environments and formats working on multiple platforms. Videos are gathered in reels and batches that are processed, improved and encoded into different formats by the tool. All processes are managed from the tool using a desktop environment in a high-performant machine, they don't provide a web application nor APIs for using video processing services.
All the customers are now asking to fetch data from "The farmer" to share it via web-pages or custom reports, but "The farmer" developers are limited by the technology for development and time constraints. What they do have is a replica database (MySQL) where they write all the videos metadata and related information, but such database is read-only and accessible from a single host.
What approach can "The farmer" company provide for their customers to enable data-sharing with the mentioned constraints?
A wall street firm handles trading of many different commodities in national and international levels, all the transactions are managed internally providing APIs for external customer to fetch reports and data about their stocks, transactions and trade forecasting. They are running on an average of 2000 transactions per second on weekdays and 100 transactions per second on weekends.
Two months ago the firm has been merged with two other firms, this means that their customer base has doubled overnight. Because of it they have had latency issues and outages, increasing the exchange rate from 200 concurrent requests per second to 1000 concurrent requests in their main servers. The increased load is causing delays in the internal transactions and overall disatisfaction in all traders.
What they can do to improve/scale-up their service quality without affecting transactions and external customers?
Die Mannschaft is Germany's football association that over the past ten years has been including technology into the match field, keeping track of player's statistics, performance, predictions and overall metadata for their internal tournaments.
For a long time they have been keeping all of this data locally, without sharing it with any other organization. In December 2018, the local government has created new laws forcing Die Mannschaft to share all their data with other government institutions. But there's the risk of their infrastructure not being able to support the amount of external requests, they have estimated that at least 5000 organizations will be fetching their data continuously.
What approach would you suggest them to use for efficiently sharing their data with other organizations?
Post is the biggest mail-company in Switzerland, they deliver physical and electronic messages overall the country. In the late 90s, the Swiss government has defined that all invoices should be sent to your inbox via email, this measure was created to reduce the amount of paper used for printing invoices and increase the overall ranking for environment-friendly countries in the EU.
But such law has created a problem for Post, early on they have decided a set of synchronous APIs for all businesses to send their invoices, and such decision has proven to be unefficient, as their consumers-base is growing, the services are getting slower and slower. Over time they have used bigger servers and load balancers to reduce latency, but the problem persist and pretty soon will be evident that they can't keep up with the load.
They can't stop the services from working nor change their APIs since they are regulated by the government, what approach would you suggest to improve Post's situation?
AAA is a banking company with its branches and main offices running under a long-running system developed in COBOL, this system handles authentication and authorization for all the applications in all levels, from internal infrastructure to transactions. In the past year the company has grown in customer-base and acquisitions with other banks, leading to the following scenario:
"Acquired banks use multiple web applications for customer support and other reporting facilities, their authentication and authorization mechanism is Single Sign On using SAML".
AAA would like to extend its internal COBOL authentication and authorization metchanism to be used in the newly acquired web applications, what approach would be advisable in this case?