- #CONFLUENCE AUDIOBOOK S. K. DUNSTILL HOW TO#
- #CONFLUENCE AUDIOBOOK S. K. DUNSTILL SOFTWARE#
- #CONFLUENCE AUDIOBOOK S. K. DUNSTILL FREE#
If you are using a Kubernetes service like EKS, you pay for nodes and for the service itself (Kubernetes masters). If you are going to run Kafka on AWS, you’ll need to pay for EC2 machines to run your brokers.
So, how much does Kafka really cost? Start with some fairly obvious and easy-to-quantify expenses
#CONFLUENCE AUDIOBOOK S. K. DUNSTILL HOW TO#
Managers are incentivized and get promoted for building large teams, and no one seems to know how to convert this budget into managed services.Īs an industry, we did not learn how to make great decisions about the use of managed services. We decided to use Confluent Cloud, and I need a budget of $7,000 a month for our use case.” Engineering organizations are built to hire engineers. This requires an event streaming platform. What you likely have less experience with is going to your manager and saying, “This year, my team is building a real-time inventory management system. If you are an engineering manager, then you have years of practice going to your manager and saying, “This year, my team is also running Kafka, we are spending 20 hours a week on maintenance. But quite often, the managers themselves don’t know how to calculate the trade-offs involved and how to justify the necessary budget. Sometimes they trust their team’s ability to deliver quality service more than they trust a service provider.
When you talk to engineering managers, the responses vary. When I ask why, the responses usually include: the joy of running Kafka themselves, the career opportunities it creates, and perhaps most commonly, a sense of futility-“my manager would never approve this expense.”
#CONFLUENCE AUDIOBOOK S. K. DUNSTILL SOFTWARE#
And I noticed that many software engineers and engineering managers do not always do this.Įven at the low end of the scale, where a managed service is ridiculously inexpensive, I see engineers run their own Kafka and not even consider a managed service. And of course, you should seriously consider a decision of this magnitude. With large-scale use cases, it is quite natural to seriously consider just running your own Kafka or MinIO instead of Amazon S3, for that matter. This is what usage-based billing is all about, and it is one of the biggest cloud benefits. This is quite typical for managed databases as a service-they can be very low cost for casual use and very expensive when you use them in anger. As your usage scales and your requirements become more sophisticated, your cost will scale too. Apache Kafka ® is free, and Confluent Cloud is very cheap for small use cases, about $1 a month to produce, store, and consume a GB of data. Five dollars a month is quite easy for an engineer to afford even out of her own pocket.Ĭloud services can have a wide price range. And what if GitHub cost me $5 a month? I’m paying this much for my to-do list management software.
#CONFLUENCE AUDIOBOOK S. K. DUNSTILL FREE#
To be fair, GitHub is free for open source projects, so this is an easy call. Instead, I just create a repository on GitHub. I don’t write a document analyzing the pros and cons of each decision. I don’t even try to run similar software on a computer on someone’s datacenter. When I have a small software project that I want to share with the world, I don’t write my own version control system with a web UI.
0 kommentar(er)
