What happens when you push to GitHub? The short answer: A lot. 👀⬇️ https://lnkd.in/gRmqmeBN
Good to know!
Wow this is a big improvement! The sequential to parallel processing with Kafka is a beautiful solution. Decoupling and independent retries + clearly owned services is a major step in maintainability and performance. Would love to read a follow up with more details about retries, observability and Kafka setup. Well done and thanks for sharing. I only wish I could process 300 milion Kafka messages a day😄
Interesting to learn about the process. Thanks 👨💻
> What happens when you push to GitHub? The angry Git pixies reject your push because you rebased locally and forgot to force push.
You ever going to fix the "bug" where any users' email can be pulled up via the API? Why use GitHub when there are safer and more private alternatives? (Genuine question)
Github never disappoints. They are one of the few who give us some detailed insights through blogs. ❤️ from India. Once I read about how they enhanced ux by using dynamic image preview on github repos and created my own version with a weather app. https://weather-app.itsyeshu.me/search/?city=Bengaluru&counter=1&timezone=Asia/Calcutta
Pushing back up code to GIT is a life saver. Especially when multiple people on your team are working on different areas of code. This saves time, money and limits error and improves error proofing. It preserves a source of truth with data lineage for years to come.
github Gamez
1w
Very helpful!
Stephen Ball
1w
Right on! That's a lot like the Kafka layer we introduced at Spreedly. I came up with the implementation approach and similarly focused in on a message delivery app that would buffer/retry until Kafka acknowledgement. It worked great! https://medium.com/spreedly-engineering/from-riak-to-kafka-part-i-ca56492d5a01
Great insights! Pushing code to GitHub is one of the most fundamental interactions our developers engage in daily. 🌟