Java IoT Authors: Yeshim Deniz, Liz McMillan, Zakia Bouachraoui, Elizabeth White, William Schmarzo

Related Topics: Java IoT

Java IoT: Article

Take Two Patterns and Call Me in the Morning

Take Two Patterns and Call Me in the Morning

Life is not easy for today's enterprise application architects. In today's IT world, the architect not only has to design solutions for a plethora of interdependent systems (as is obvious from the job description and title), he or she also has to conform to the ever-evolving standards in a shorter API life cycle, plan for the not-too-distant future, collaborate with business and technical environments, and work on a feasible roadmap for his or her application/application portfolio.

In large organizations, standards for various facets of business and technology are already laid out and managed between several competency centers/centers of excellence, and strict governance is often in place to ensure consistency throughout the organization. To successfully deliver products against hard deadlines, the architects have to make sure that everything complies in the governance process.

With the advances in software engineering, especially in component-based and service-oriented architectures, common guidelines have emerged in the form of design patterns. These design patterns help architects leverage what others have learned in their software design journey. The Java platform is an obvious example of the application of design patterns. Before distributed platforms such as Java came along, the number of folks who could spell "design pattern" was limited to the few who had read the Gang-of-Four book, and that was just a handful of developers in any organization. With Java - Listeners, Proxies, Observers, Factories, Delegates, Facades - all these became a part of the designers' common vocabulary. Reference architectures, frameworks, and plug-and-play followed soon after. Although Java is not solely responsible for this, it has definitely played a big part in the promotion of these concepts. Add UML and RUP to the mix and you not only have the toolkit, but also the ability to document and manage your application's development in a common way.

With all these wonderful tools in the architect's toolkit, why is the job still so complex? Given the tools at hand, an application architect should easily be able to develop applications that leverage:

  • Application frameworks
  • Architecture blueprints
  • Adaptive architectures
  • Reference architectures
  • Prescriptive architectures
These architectures and frameworks have been developed in the software community, as well as within organizations, and they facilitate the design of applications from a common base and building blocks. Apply them to your application and presto - you have a two-minute recipe to create an instant product. Where's the catch?

The basic problem is that the guidelines and patterns, though invaluable, are created outside the application domain. Although they do address the needs of applications, that need is addressed across a number of applications. After all, it's the only way that reuse can be promoted. In this editorial we are focusing on the application architect. The architects in competency centers and standards groups focus on promoting reuse. The focus of the application architect is on leveraging reusable components and leveraging documented patterns to solve a business problem. However, unless a clear path is laid out for navigating through the available choices, he or she may easily choose to develop alternatives in order to meet the demands of the application.

This impasse between the prescription of reuse and its feasibility in the application's context needs to be carefully addressed. Just as the design principles that apply to a broad range of applications are made available for the applications, a guidebook that navigates through these principles should be developed for the application/application portfolio. This guidebook should focus on application design, treating the application as the center of the universe. Then clear governance practices should be established around exporting the reusable artifacts, learnings, and application patterns that emerge out of each application design cycle. These should then be incorporated into the rationale for selecting design patterns published by groups external to the application. After all, communication is a two-way street. Design patterns are no exception.

More Stories By Ajit Sagar

Ajit Sagar is Associate VP, Digital Transformation Practice at Infosys Limited. A seasoned IT executive with 20+ years experience across various facts of the industry including consulting, business development, architecture and design he is architecture consulting and delivery lead for Infosys's Digital Transformation practice. He was also the Founding Editor of XML Journal and Chief Editor of Java Developer's Journal.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

IoT & Smart Cities Stories
Bill Schmarzo, author of "Big Data: Understanding How Data Powers Big Business" and "Big Data MBA: Driving Business Strategies with Data Science," is responsible for setting the strategy and defining the Big Data service offerings and capabilities for EMC Global Services Big Data Practice. As the CTO for the Big Data Practice, he is responsible for working with organizations to help them identify where and how to start their big data journeys. He's written several white papers, is an avid blogge...
Nicolas Fierro is CEO of MIMIR Blockchain Solutions. He is a programmer, technologist, and operations dev who has worked with Ethereum and blockchain since 2014. His knowledge in blockchain dates to when he performed dev ops services to the Ethereum Foundation as one the privileged few developers to work with the original core team in Switzerland.
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a m...
Andrew Keys is Co-Founder of ConsenSys Enterprise. He comes to ConsenSys Enterprise with capital markets, technology and entrepreneurial experience. Previously, he worked for UBS investment bank in equities analysis. Later, he was responsible for the creation and distribution of life settlement products to hedge funds and investment banks. After, he co-founded a revenue cycle management company where he learned about Bitcoin and eventually Ethereal. Andrew's role at ConsenSys Enterprise is a mul...
In his general session at 19th Cloud Expo, Manish Dixit, VP of Product and Engineering at Dice, discussed how Dice leverages data insights and tools to help both tech professionals and recruiters better understand how skills relate to each other and which skills are in high demand using interactive visualizations and salary indicator tools to maximize earning potential. Manish Dixit is VP of Product and Engineering at Dice. As the leader of the Product, Engineering and Data Sciences team at D...
Dynatrace is an application performance management software company with products for the information technology departments and digital business owners of medium and large businesses. Building the Future of Monitoring with Artificial Intelligence. Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more busine...
Whenever a new technology hits the high points of hype, everyone starts talking about it like it will solve all their business problems. Blockchain is one of those technologies. According to Gartner's latest report on the hype cycle of emerging technologies, blockchain has just passed the peak of their hype cycle curve. If you read the news articles about it, one would think it has taken over the technology world. No disruptive technology is without its challenges and potential impediments t...
If a machine can invent, does this mean the end of the patent system as we know it? The patent system, both in the US and Europe, allows companies to protect their inventions and helps foster innovation. However, Artificial Intelligence (AI) could be set to disrupt the patent system as we know it. This talk will examine how AI may change the patent landscape in the years to come. Furthermore, ways in which companies can best protect their AI related inventions will be examined from both a US and...
Bill Schmarzo, Tech Chair of "Big Data | Analytics" of upcoming CloudEXPO | DXWorldEXPO New York (November 12-13, 2018, New York City) today announced the outline and schedule of the track. "The track has been designed in experience/degree order," said Schmarzo. "So, that folks who attend the entire track can leave the conference with some of the skills necessary to get their work done when they get back to their offices. It actually ties back to some work that I'm doing at the University of San...
When talking IoT we often focus on the devices, the sensors, the hardware itself. The new smart appliances, the new smart or self-driving cars (which are amalgamations of many ‘things'). When we are looking at the world of IoT, we should take a step back, look at the big picture. What value are these devices providing. IoT is not about the devices, its about the data consumed and generated. The devices are tools, mechanisms, conduits. This paper discusses the considerations when dealing with the...