In a previous blog post (How To Survive an Apache Kafka® Outage) I outlined the effects on applications during partial or total Kafka cluster outages and proposed some architectural strategies to handle these types of service interruptions. The applications most heavily impacted by this type of outage are external interfaces that receive data, do not control request flow, and possibly perform some form of business transaction with the outside world before producing to Kafka.
The past year has seen an unprecedented AI hype wave triggered by the launch of OpenAI’s ChatGPT. Analysis abounds on whether the hype is real, where value will accrue and whether generative AI-first product builders have a real shot at category disruption or creation. As frenzied R&D and market activity continue unabated, market maps and take after take continue to drop hot. But what about revenue?
ERP systems run the world’s businesses. These stalwart systems are great at managing records and processes for finance, operations, supply chain management and more. But their insights need an upgrade. That’s the case put forward by Maxa, an enterprise-grade startup that has made it their mission to reinvent the way companies access and use ERP data for transformational insights.
Follow this formula to streamline financial statements and automate data for accurate financial analysis.
Stepping into the world of Apache Kafka® can feel a bit daunting at first. I know this firsthand—while I have a background in real-time messaging systems, shifting into Kafka’s terminology and concepts seemed dense and complex. There’s a wealth of information out there, and it’s sometimes difficult to find the best (and, ideally, free) resources.
