Service architecture

We are not only tidying our garage; We're also re-engineering the architecture and infrastructure holding up our garage.

The way we want to do things going forward is to give everything in the garage its own garage; A garage for the bike, a garage for the screwdriver, a garage for the hammer, and so on and so forth.

In technical terms, this is called “Microservice Architecture”.

• Smaller garages are really easy to put stuff in and take stuff out of
• It’s really clear what is in the garage and where to find it

• When you want to do something big, you have to unlock lots of little garages to get everything you need
• This is rare but, when you have many tiny garages, sometimes you lose a whole garage!

AWS is our cloud hosting provider. The way we architect our AWS will have a huge impact on how secure and scale-able our API platform is; That means it's really important to get right. We're currently working with the team at AWS (and other AWS certified architects) to make sure that what we are proposing to do now will not limit us in our ultimate goal.