Our vision is that we are creating a fully automated smart fridge network, meal manufacturing and most important - "healthy eating communities". Our obsession is not any specific architecture - it's our customers, Kwaku and their goals. There are many charachteristics that the system should support, hence our architecture is hybrid, where every capability and subsystem is designed in such a way as to best serve both their specific task, and the overall purpose. It scales and grows together with the business it is built to support. Having said that, it seems that eventually our architecture natuturally evolved into a more of the microservice and event driven variety because of necessity to support more complex workflows over time, and the need to gather data for business analytics.
In addition, to the capabilities listed in the system component digram there are unlisted more detailed infrastructure capabilities such as
- Data Protection and Encryption
- Application Services (Backend for Frontend) for Server Side Rendering, HTTP batching, data and information formatting, filtering and merging.
- API Gateway
- Experimentation for A/B testing
- Feature flagging
- CICD
- Security scans and SSDLC
- Testing
- Load testing
- Service and Platform hosting in Cloud
- More