Page 70 - Futr Investment Proposal
P. 70
70
Technology Review
Prepared by Phil Cox (CTO, Mobedia)
Summary Positives retained/compatible/versioned, they do
not need to be overly concerned with
From the high level discussions that have 2.1 Microservices approach services outside of their remit.
taken place, the product seems to be of
good quality, the microservices approach The fact the system has seemingly been • Development options - whilst the
and the adoption of existing cloud built with this approach from the ground business is young and the technical
technologies for speed of setup, reduced up is a big advantage. team is small, Lee was explaining the
ongoing maintenance and scalability being outsourcing approach he has taken with
key advantages. This allows each component of the system the technology. The microservices
to be developed, maintained and approach allows Lee to write a brief for
Inevitably there were a few minor concerns deployed in isolation with the technology a specific part of the technology and
as the current technology was explained, being the sum of all these parts. ask a 3rd party to deliver this specific
most notably the spread of programming piece, de-risking the implementation
languages in use and documentation. For initial development, no micro-serice request through several much smaller
has taken longer than 2 days to develop. projects rather than one monolith.
More detail on positives and negatives Furthermore, the 3rd party doesn’t
identified is provided below. Some advantages of this approach include: receive copies of the technology as a
whole, only receiving what they require
In short, in my opinion, the technology • Development team scalability - as the to do their job, which I imagine, in a lot
shouldn’t be a blocker for progression of technical team grows within the of cases, is nothing other than the brief.
this opportunity. However, at this stage, business teams can be formed around
this recommendation is purely based on specific services or, if necessary, • The brief for work becomes specifically
the conversations to date e.g. the code dedicated to one single service. This focused on the required task, providing
and infrastructure setup have yet to be team then becomes responsible for the a level of documentation for the service
reviewed in detail. development, maintenance and going forward.
deployment of their service(s) - they can
focus on and specialise in these specific
areas and, providing the contract into
their service is
