> is it part of your existing stack or do you have in-house experts in this tech?
Nope and nope. That's definitely the scary / unknown part!
> If you have a lot of spare developer time and people skilled in this, it will likely work well for a while (potentially a really long while).
We don't have a lot of spare developer time and people. However, the Elastic docs make our fairly straightforward use case - dump lots of events in and filter them by date and about 4 different properties - seem not too daunting.
The way it's sold on the Elastic site these days seems like a very "batteries included" kind of approach - am I interpreting their marketing a little too positively? Are we kidding ourselves? Would love to hear more about your thoughts!
> Structuring data is another really important consideration - will you need to normalize and will you need to update labels/dimensions? That’s just the start.
We don't expect much.
Thanks for mentioning the other technologies, too! The way we're structuring it allows us to either use Elastic, SQL, or something else entirely, so thankfully we're fairly agnostic on the data store. If Elastic turns out to be a time sink, we'll have no hesitation trying something else out.
Nope and nope. That's definitely the scary / unknown part!
> If you have a lot of spare developer time and people skilled in this, it will likely work well for a while (potentially a really long while).
We don't have a lot of spare developer time and people. However, the Elastic docs make our fairly straightforward use case - dump lots of events in and filter them by date and about 4 different properties - seem not too daunting.
The way it's sold on the Elastic site these days seems like a very "batteries included" kind of approach - am I interpreting their marketing a little too positively? Are we kidding ourselves? Would love to hear more about your thoughts!
> Structuring data is another really important consideration - will you need to normalize and will you need to update labels/dimensions? That’s just the start.
We don't expect much.
Thanks for mentioning the other technologies, too! The way we're structuring it allows us to either use Elastic, SQL, or something else entirely, so thankfully we're fairly agnostic on the data store. If Elastic turns out to be a time sink, we'll have no hesitation trying something else out.