Engineering Blog - Architecture (Production concerns? (How can I know what…
Engineering Blog - Architecture
Hippo as CMS
What SQL DB should I choose?
Initial option: MySQL
I've worked with MySQL before at Airbiquity,
so it should be easier for me to understand
rather than trying to learn about the other SQL
Hippo CMS with it's built-in
CQRS Message Broker?
Hippo's Built In Event Bus
CQRS Query services?
Equivalent to Hippo's Built In Event Listeners:
Instead of copying the bits to an ES, the event listener
will send a request to another Microservice that will
handle the event.
Why do this?
separates the internal database models from the external contract models (the contract of the microservice)
Any drawbacks to this approach?
Each implementation of the event listener can
be seen as an equivalent to a single subscriber
A microservice responsible for showing the results, e.g., the UI layer
This MS will contain a datastore to hold
What data store should we use?
We can use both Vue.js and Thymeleaf:
Where will this be hosted?
How much will it cost me vs Digital Ocean?
I can develop on my local and can
guarantee that it will work in Production.
Look at the Docker branch I created in
This is worth looking into as well:
Maybe no at first... and then introduce Docker later?
How can I know what code changes will
be released and how will it effect the current
instance of Hippo in Production?
This might help:
What do I need to do in order to get my
local Hippo ready for Production?
How to setup reverse proxy?