Page 71 - Futr Investment Proposal
P. 71
71
Technology Review (ctd)
Prepared by Phil Cox (CTO, Mobedia)
2.2 Cloud Technology Furthermore, the ‘don’t reinvent the wheel’
For reference, multiple cloud providers mentality extends beyond customer facing
Several cloud providers are currently used aren’t in place to provide additional functionality to the underlying technology.
based on the provider that currently has resilience. The resilience/failover For instance, the open source chatbot
the best tech for the job. mechanisms within each cloud platform are machine learning framework Rasa has been
used but there is no additional mechanisms built upon for the core product.
The cloud providers currently used are to allow Azure to take over in the event of
AWS, Google and Azure. a complete AWS outage for instance. 2.4 Requirements
However, such an approach at this stage
Use of cloud technology has clear would be overkill. Whilst I haven’t yet seen an example of a
advantages and I believe Futr are currently requirements document for a microservice
using the latest and greatest from these 2.3 Reuse Wherever Possible I have been taken through the
services, resulting in a platform that requirements for the new SaaS onboarding
requires minimal maintenance and offers it seems like the decision has been taken to processes.
huge scalability potential. integrate rather than redevelop i.e. to use
what’s out there rather than reinvent the If the documentation for this project is
In particular, the use of serverless wheel. anything to go by, it is super detailed with
technology for much of the product explicit wireframes and concepts, even to
provides a very cost effective and For example, the product integrates with the point of providing sample CSS to
maintenance free way of running, for Survey Monkey rather than attempting to describe button colours, fonts and
instance, the API endpoints. This, together offer an internal survey creation tool as part transitions for example.
with the other cloud components used, of the product.
results in an average running cost of £860 Therefore, whilst documentation of existing
per month. In my opinion this is very wise, particularly services is raised as a negative below, if we
at the current product stage. It reduces the assume all requirements are as good as
It is my understanding that when serverless initial implementation time whilst also this brief, the requirements for each service
technology can’t be used, containers are simplifying the onboarding process for will provide a good level of documentation
used and run on a managed container customers, allowing them to hook into around the expected service operation
orchestration platform such as Azure tools they likely already use. going forward.
Kubernetes Service (AKS).
