We evaluated confluent cloud and ended up going with https://aiven.io. It's a completely managed solution, running in a private vpc peered with the rest of our aws infrastructure. At the time we evaluated it was substantially less expensive than confluent cloud (~5x). Aiven implemented their own binary compatible schema registry when the license changed, it hasn't caused any problems for us.
MSK wasn't available when we were doing our analysis. hth, jt On Mon, Sep 7, 2020, 7:52 AM Chad Preisler <chad.preis...@gmail.com> wrote: > We use Confluent Cloud. Make sure you consider the opportunity cost of you > labor into your MSK cost. Other than creating topics and managing ACLs you > won’t have to lift a finger to manage your Confluent Cloud Kafka cluster. > That means you get to spend all your time building apps to run your > business. They also have fully managed KSQL and Kafka Connect. They’ve > changed their pricing recently, so make sure to check them out. > > On Mon, Sep 7, 2020 at 4:15 AM Tom Black <tom.v.bl...@gmail.com> wrote: > > > > > > > > > > > Himanshu Shukla wrote: > > > > > We are planning to go for amazon MSK instead of having our own self > > > > > launched cluster on bare EC2 machines. > > > > > > > > > > It would be very helpful, if someone who has used it before or know > about > > > > > it, can share the feedback/observations regarding the same. > > > > > > > > > > My main concerns are, > > > > > Is it worth using Amazon MSK? > > > > > > > > They are expensive. I am curious why you'd consider to use the full > > > > managed service instead of building your own cluster? > > > > > > > > Regards. > > > > >
