Learn more >
by Shereen Ghobrial | Updated February 20, 2019 - Published May 16, 2017
Most modern applications follow a common architecture pattern, which is illustrated in Figure 1. The user interacts with the application front end, which might be a mobile app, a web app, or even a sensor connected to some appliance. The application usually needs a back end that provides the real functionality and value to the user. This back end typically accesses/updates the client data and handles transaction processing. A typical platform for the back end would be a public cloud or on-premises servers.
These challenges have created motivations to use modern languages on enterprise servers. These reasons are shown below.
There is a big demand for COBOL, PL/I, and Assembly programmers on enterprise servers. With a big portion of the current mainframe developers approaching retirement, enterprises are having a hard time hiring graduates familiar with those traditional languages. Providing new modern languages on enterprise servers would enable enterprises to easily hire recent graduates who are familiar with those languages and are already using them on the front end.
Most of those new languages are designed to fit nicely into the API economy for the enterprise. They are suited to build micro services, which makes them a good fit to run on the back end. Having the modern languages enabled on enterprise servers would enable enterprises to leverage their current investments on CICS and COBOL. This means enterprises can expand current COBOL and CICS applications with modern languages, such as Swift and Node.js.
There are many languages that would satisfy the first two needs, but they are not available on the server platform. They would typically exist in what we might call the mid-tier (a server that is between the front end and the back end, working as a staging station, or a caching server). This means lots of network communication, which would impact your application’s performance.
For your application to have a quicker response time, you need to have your application back end as close as possible to your data. If your data exists on a cloud server, your back end should be hosted there. If your data exists in a mainframe, your back end should be hosted there. This raises the need to have modern languages, such as Swift and Node.js, on the cloud and server platforms.
The Java language was introduced more than 20 years ago, and is one of the main platforms that services modern enterprise applications. From the beginning, one of Java’s main appeals was its “Write once, deploy anywhere” mantra; allowing code to be developed, tested and deployed where it makes sense. To achieve this, Java compiles Java source to bytecodes, which are portable. These bytecodes are then interpreted and dynamically optimized on the target platform. Over the years, Java has evolved and matured in terms of frameworks, security, and interoperability with other languages, and has continued improving in performance. In addition to the merits in the language itself, there is a large Java developer population worldwide, making it easy for enterprises to find and hire programmers to build Java applications.
Node.js embraces the open source community and provides a module management system that allows developers to contribute and share different modules via Node Package Manager (NPM). Developers love NPM, which currently hosts more than 400,000 modules. The growth rate of community-contributed modules in NPM is three times the growth rate of other runtimes, as shown in Figure 2.
The large number of available modules in NPM leads to increased developer productivity. If you need to build certain functionality in Node.js, chances are modules that achieve the same functions already exist. By leveraging such community modules as building blocks, developers can leverage and rapidly assemble their application.
Node.js leverages an event-driven, non-blocking, asynchronous I/O framework as its programming paradigm. As such, for I/O tasks, Node.js leverages the underlying asynchronous I/O support in the operating system. This means you can run thousands of concurrent connections with minimal overhead, allowing your application to react smoothly to high transaction demand in peak hours.
Swift was introduced by Apple in 2014 and was given to the open source community in December 2015. Since then, it has been well received by the development community and jumped to number 15 in RedMonk ranking and to number 11 in the 2017 StackOverflow Developer Survey. It has the industry backing of big companies including Apple and IBM. There is an ecosystem of frameworks evolving around Swift with different web frameworks being written in Swift, such as Perfect.org, Kitura, and Vapor. Conferences and meetups are being held by Swift enthusiasts to exchange Swift experiences and best practices, such as try! Swift in New York, and Bangalore.
All these factors indicate that Swift is a language with great potential. But what are the reasons behind all this excitement? There are three factors that make it an interesting language.
Swift is a relatively new language, and it was designed with all the modern features you would expect in a modern language. It is relatively easy to learn because its concepts are similar to other popular languages. Its syntax is concise and straightforward to read, with little verbiage. Though the language is relatively new, its compiler is built on the LLVM compiler infrastructure, which has been around for some time now and have a proven strong performance for other languages such as C and C++. This means we get a good combination of a modern language with a mature optimizing compiler.
Because Swift is new, it was designed to avoid the mistake that many programmers tend to make in previous languages. Swift is a strongly typed language, with many types of error-detection happening at compile time. Variables are automatically initialized, and memory is automatically allocated and managed. These features would eliminate the issues around bad pointers, uninitialized variables, or values miscalculated due to wrong type-casting.
The Java programming language has been used in enterprise servers for almost 20 years, and we see good adoption with successful mission-critical Java applications running in production. Node.js is relatively new, and we are seeing many enterprise clients moving to Node.js to leverage its fast I/O and high scalability. Swift 3.0 was the first release that was truly built for server-side development including support for x86 Linux and Linux on z Systems. It will be interesting to see what type of workloads will be developed using Swift on the server, especially after the introduction of Swift on z/OS.
What will really drive the adoption of these modern languages is a fresh and young generation of application developers. The technical merits of a programming language is not enough to make it successful. The main motivation for having these languages on the enterprise server is mainly driven by the available skills. Having a polyglot ecosystem on the server platforms enables the enterprises to have a choice in their investment and modernization efforts. This leads to higher productivity, a faster DevOps cycle, and a better ROI in the IT investment.
Back to top