|
|
|
|
|
by tristanz
2065 days ago
|
|
I have a hard time buying this hybrid architecture is the future. Running a bunch of stateful services with potentially large storage requirements in my own infrastructure is not zero-maintenance even if the control plain is managed. And proxying the UI for end users introduces back security and usability issues. The best experience and lowest friction sale is to deliver a fully managed experience and earn the trust of customers. Confluent, Snowflake, Mongo Atlas, Rockset, CockroachDB, Elastic, Splunk, New Relic, etc all prove this is a great model for both customers and vendors. For the largest security conscious customers you can offer a fully VPC/on-prem solution with exactly the same form factor if you want. Hybrid can have its place, but I'd always try hard to offer a managed solution if you can justify it. |
|
Thanks for the feedback. In general we try to keep the footprint of services on customer environments small. Since Pixie is mostly an ephemeral system our storage requirements are relatively modest. What this does allow us to do is process enough of the data on the customer machines locally that we only have to send back and store summaries. The long term goal is to build a cloud + edge based system where we can efficiently process data by having data locality.
Kubernetes gives us a substrate where these types of systems are manageable without too many complications. In the longer run we will likely have VPC hosted services as well for people who just don’t want to deal with it.