Welcome!

Weblogic Authors: Yeshim Deniz, Elizabeth White, Michael Meiner, Michael Bushong, Avi Rosenthal

Related Topics: Weblogic

Weblogic: Article

Services-Oriented Architecture and Services-Oriented Development of Applications

A strategy for transition

Services-oriented development of applications (SODA) is an important development model for enabling organizations to reorient business processes in the transition to a service-oriented architecture (SOA). This article describes one such approach.

Services-Oriented Development of Applications (SODA)
Gartner refers to SOA and SODA as foundational elements of future computing. SODA is a new style of developing software, designed to work specifically within the SOA paradigm. SOA represents a collection of loosely coupled, coarse-grained, heterogeneous components that can be easily snapped together using Web services. The result is enhanced developer productivity, code reuse, and business agility. The SOA Blueprints (www.middlewareresearch.com/soa-blueprints/), an industry-derived set of best practices and associated reference implementation, is an excellent resource for those looking to move to an SOA.

SODA is centered on the creation and assembly of services and service contracts first, deferring the design and implementation of the objects and components that realize the services until after the coarse-grained service contracts have been ironed out. SODA developers focus more on the process flow within and between applications, and less on the code that creates the underlying system. For a brief and to the point description of SODA, see www.serviceoriented.org/soda.html.

Pain Points
The issues described below are certainly not all-encompassing, but are meant to exemplify the issues that often impact a development process (particularly when undertaken by larger enterprises with multiple development teams), and which might be alleviated by transitioning to a SODA-based development approach.

Dependencies / Bottlenecks
Bottlenecks related to the ordering of dependencies are usually the biggest issue. Developers are often waiting for a dependent item to be designed and/or implemented before they can continue with their tasking. One of the issues is the division of labor in a multi-team environment. A standard division of labor often employed in this environment consists of having different teams working on the same vertical slice of functionality in different tiers, causing these dependency-related bottlenecks to spring up.

Management and mitigation of dependency-related issues is crucial to ensuring that developers can continue to be productive throughout development iterations; however, it isn't possible to "manage" a dependency issue away if many of the pieces are being developed in parallel (which is often the case with a fixed deadline).

Creation of the data model for each of an organization's releases (iterations) oftentimes begins roughly in parallel with the development of the software that interacts with it and not much earlier, which is not ideal but not always possible to avoid. Similarly, the domain model for a release may not be completed prior to a development iteration that will be using it. Proper planning in building out the data and domain models first is critical to avoiding these issues but if the project is already well underway, it is what it is ("next time, we'll do it right"). These issues result in a bottleneck for the business services, object/relational persistence mapping, and enterprise application integration (EAI)/business-to-business (B2B) developers, who require both data and domain models to be completed before much of their work can commence. The dependency problems can quickly cascade.

Division of Labor
Development teams are often divided horizontally by tier (especially those that are geographically dispersed). One team may be working on the presentation tier and the other on the business tier. This division often exists out of necessity due to the fact that off-site teams may not have access to the back-end systems with which the business tier needs to interact. Development of the presentation-tier functionality does not require access to these systems (at least during the design and initial implementation phases of the iteration). This division of labor has its problems, though, in that the development of discrete pieces of functionality (use cases) is being performed by separate (again, often geographically separated) teams. These teams often communicate through interfaces to business services and the data transfer objects (DTOs) (http://java.sun.com/blueprints/corej2eepatterns/ Patterns/TransferObject.html) exposed through them - a standard Java 2 Enterprise Edition (J2EE) best practice. The DTO structure and content often changes during a development iteration, as both the presentation and business services developers dig deeper into their designs and subsequent implementations. In addition, the structure/content of the DTOs is (mostly) driven by the structure of the domain model, and as it evolves, so do they. These issues could be lessened somewhat if the same team were working on an end-to-end slice of functionality (one team would be in control of the structure/content of the domain model, DTOs, business service interfaces, and the associated presentation). The key roadblock to going down a road with this approach is the capability to consistently simulate interfaces with the back-end systems, so that an off-site team can be given a full vertical slice. When teams are collocated, such back-end systems often have usage restrictions, especially when the back-end system is connected to and/or owned by another project, department, or business.

How Can a SODA Approach Help?
All resources are considered to be as services with SODA (from UI components on the front end to interaction with an external business partner on the back end). The primary development activity for the vast majority of developers here is the orchestration of those services. A small number of J2EE and integration gurus are responsible for the development of the implementation and/or extension of services in the case where the chosen SODA tools do not provide them off-the-shelf.

More Stories By Steve Buzzard

Steve Buzzard is currently working as a J2EE principal architect with Anexinet Corporation (www.anexinet.com), a leading systems integration firm headquartered in Philadelphia, with offices in New York and Washington D.C. Steve has over 19 years of experience in professional software development and has been working almost exclusively with the WebLogic Technology Stack since late 1998.

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
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...
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...
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...
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...
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...
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...