Over a million developers have joined DZone.

The Future of (Rapid) Programming: Fat-Stack Appliance Platforms?

Can programming platforms like Java be designed and released in a way to engage programming newcomers and decrease time-to-market?

· Java Zone

What every Java engineer should know about microservices: Reactive Microservices Architecture.  Brought to you in partnership with Lightbend.

What will be the future of programming platforms?

The industry is moving in a way where the old method of releasing a programming language in a silo may raise questions. Is it enough to only release a new version? I am not sure about the answer, but some radical change might be needed.

Let me give an example. Oracle is releasing Java versions with new features and capabilities, but let's think of a scenario where Oracle starts releasing “Java Platform Appliance”. This platform will include the latest version of JDK/JRE and some pre-defined stack of related and commonly used software, as well as some references or example implementations (more commonly known as accelerators) to build custom applications. The appliance platform can include the following most commonly used packages:

  1. A Solr-based search engine, which will have some ready-made setup. There will be pre-defined templates to create different kinds of search applications.

  2.  A SMACK-based platform to augment Big Data processing — easy plug and play framework for real-time and batch processing.

  3. A Spring-based integration template and accelerator for some common and popular integration brokers like ActiveMQ and RabbitMQ.

  4. A Spring-based batch platform (a reference implementation of Spring batch module).

  5. Some reference implementation to connect to NoSQL databases (use of Spring-based framework may work here).

  6. A web-based template to create a Spring-Hibernate (ORM) and Spring MVC (Web tier) application.

  7. Reference implementation of logging using SFL4J.

  8. A reference OSGI implementation for modularization.

  9. Build packages using Ant, Maven, and Gradle.

The goal of this appliance is that developers can start using the platform as an easy sandbox to build common web applications. The common design patterns, principles, and best practices will be followed during the building of these accelerators.

What do you think? Will it change the way we look at the platform for programming languages now? Will it help to reduce time-to-market?

Microservices for Java, explained. Revitalize your legacy systems (and your career) with Reactive Microservices Architecture, a free O'Reilly book. Brought to you in partnership with Lightbend.

Topics:
java

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}