|
|
|
|
|
|
by lenkite
1738 days ago
|
|
|
> and writing interfaces and top of that piece of crap that can only process data at night or during the weekend. I worked on mainframes and this seems like some deliberate policy not a mainframe limitation. Also your Kafka+Java architecture is unlikely to still be supportable in 2 decades. Will have the same problems with Java and Kafka in the future as you have with Cobol today. |
|
|
I doubt that. Java has shown a huge commitment to backward compatibility; you can take code from 20 years ago and run it unmodified today. Kafka is younger but it's also a project that takes compatibility seriously.