Advertising Cobol Streamhouse | Hackernoon

introduction

Cobol (the common language of business) still plays an important role in the base of the blade in the world, especially in commercial and financial systems. While accurate numbers differ, modern estimates indicate that the amount of CoBol icon is still in use:

1. there 775-850 billion lines From Code Code for daily use around the world.
2. Cobol systems are approximately treated 3 trillion dollars value From daily transactions.
3. 43 % of banking systems It is still used by Copol.
4. 95 % of ATMs In the United States and 80 % of personal credit card transactions are processed using Cobol systems.
5. almost 70 % to 80 % Among the world’s commercial transactions is treated in Copol.

Copol was all over the news these days for various reasons. Here are some modern links that you can enjoy before diving in meat what is happening.

Although Cobol may not be prevalent in the new development, it is still a decisive component in many ancient systems, especially in banking industries, financing, insurance and government industries. Despite her age, Copol is still relevant Because of its reliability, efficiency, and its suitability for the tasks directed to business. to this end , Deltastream It is a presentation Cobol Streamhouse!

What is Cobol Streamhouse?

For decades, Cobol was the backbone of critical systems in industries such as finance, insurance and government. Despite the reputation of Kopol for reliability, her resistance to modernization has left many organizations struggling with a paradox: How do you maintain the value of the legacy code that was tested in the battle with the opening of lightness and the ability to expand in the world of the day that the data moves? The Cobol Streamhouse project is our answer – a bold initiative to integrate the modern data staple with Cobol, starting with broadcasting capabilities and data whose data promise to breathe a new life in these strong systems.

The purpose of Cobol Streamhouse is clear and direct: to achieve the benefits of data processing in actual time and advanced applications of applications that, so far, have been distinguished in the processed past. We are not here to tear and replace-the presence of permanent Cobol is evidence of its value-but to expand its capabilities, while ensuring that it flourishes along with the cloud original techniques. By interviewing Cobol on its own conditions, we formulate a bridge between yesterday’s symbol and tomorrow’s capabilities, and enable organizations to benefit from their current investments without disrupting a full rewriting.

Our journey begins with two basic phases that address the most urgent needs in the structure of modern data: flow and data management. The first stage offers a flow to Cobol via the Apache Kafka (CoBKA) application explicitly designed for this old language. Kafka, which is famous for its ability to deal with highly productive data flows, is the cornerstone of modern data staple. Bring him to Cobol means enabling these systems to process transactions, records and events when they occur – not only in night payments. Imagine a banking system that can analyze the actual time payments or the insurance platform that adjusts risk models during flying. Our Cobka application maintains the original strengths of the language-reliability, accuracy and consensus-with the inclusion of the event that depends on the event.

To complete this, the second stage of APache iceberg, which has been re -conceived in Cobol as Cobberg, offers to create a strong data framework. The attractiveness of Iceberg lies in its ability to manage huge data collections with features such as the development of the plan, division, and acid transactions-capabilities that precede light years before the common flat file in the old Copol environments. By implementing iCeberg in Cobol, we prepare these systems to deal with systematic and semi -organized data, while maintaining the integrity of transactions. This is not only about storing data; It comes to making it inquiries, ready, and ready for modern analyzes, from SQL engines to machine learning frameworks. Together, Kafka and Iceberg position in Cobol the foundation for an ecosystem for data, which is suitable for the union and its future.

These initial stages are just the beginning. We treat the most urgent gaps between Cobol and contemporary structure by starting broadcast functions and lake data. The Kafka application opens actual time visions, while ICEberg provides the basis for developing and flexible data management. Moreover, we do this without forcing the developers to abandon the construction of a sentence or the Copol-our applications are designed to feel local, not installed. This approach maintains the experience of Cobol programmers, many of whom spent contracts to master the language, with a new generation call to see its potential in a modern context.

Cobol Streamhouse is not related to rewriting history; It comes to rewriting the future of old systems. When we offer these capabilities, we prove that the update should not mean migration. With the flow of Lakehouse technologies and data on hand, Cobol can confidently take confidently in the actual time of computing centered on data-without the loss of reliability that made it indispensable in the first place.

summary

If you want to learn more about Cobol in the context of a language you understand, I wrote This article is multi -part For HP Chronicle in 1986. It was intended to teach C for CoBol because Cobol was more prevalent than C.

Make sure to review the cobol streamhouse Jaytab. Each symbol is available to view and use. Set sample and dualities a project and consumer It is included. We are enthusiastic about this development and opportunities it offers.