So, was mongodb discarded?
ffflabs opened this issue · comments
Part of the readme says you need to sync existing CMS e-commerce backend API (or create one if there isn't) with a NoSQL database. (Like in any NoSQL engine)
Further on, everything relates to elastic search. Is this a permanent decision or it's just the way you chose to dockerize?
Moreover, if you're using redis as a cache layer, wouldn't it be possible to just go for redis as the NoSQL layer as well? I'm willing to contribute to a woocommerce driver, but the overall architecture seems too convoluted, too many mobile parts and I'm breaking my head around it.
Hi! Correct, mongodb currently not being developed - however, it should still theoretically works :) However Vue Storefront support Elastic only.
We haven't had any need for other caching layer (than Redis) - correct, it shouldn't be hard to add other cache backend as well.
WooCommerce - we're starting some efforts on this but for the next 2-3 weeks will be to early to join our efforts (we're preparing architecture etc).
Have You seen https://github.com/DivanteLtd/vue-storefront-integration-boilerplate ?
Yes I've seen it. I haven't found enough spare time to play with it though.
Regarding redis, I meant you could use it as a NoSQL storage, or use Elastic as the caching layer.
I don't know how hard would be to actually perform queries on Redis but if you used different prefixes for different entities, who knows.
On the other hand, Elastic should be blazing fast for whatever query you perform, so I'm not sure you need Redis at all. If you use a different index in the same key-value way that you use Redis the performance should be on pair.
These are just random thoughts I had when comparing the 3 tier boilerplate vs the actual infrastructure layout that depicts 6 or 7 microservicee