Service Oriented Development, the benefits… without the risks!

See AMP Version

Service Oriented Development offers all the benefits of custom software development without the risks and without the costs of a Commercial Software; this is what we intend to address in this sequel to the previous post.

We explained in the previous post that while Custom Software Development constitutes a significant risk in terms of sustainability of services and development costs; commercial software often entails huge pre-installation adaptation costs and recurring license fees.

Thus, we explained to have taken another path a few years ago because it seemed to offer the best of both worlds for both the client and the developer; service-oriented development based on three principles:

  1. Parallel Development, by iteration
  2. Service-oriented architecture (SOA)
  3. Platformless architecture

Domain-driven, Service Oriented Development

At the macro level, Service Oriented Development can run in parallel with existing Information Systems and IT applications and it is function-oriented; iterating functionalities that meet specific business needs as they are required over time.

Moreover, its extension at the micro-level enables “domain-driven” development; that is to say, to develop functionalities (supporting) relative to specific processes.

Thus, the competitive contribution of the new functionalities developed will be leveraged at the level of “business needs” and “departments” but also at the level of “processes”.

Service Oriented Development is definitely an excellent strategic choice to quickly provide new functionalities generating an immediate competitive advantage and allows you to distance yourself from the competition.

No risks, Service Oriented Development

We argued that services developed within a service-oriented architecture, so-called platformless, using the REST low-level protocol and the .Net core 2 environment offered the freedom, if need be, to no longer be dependent on a specific environment for hosting, such as Windows, Cloud or Linux.

The fact that the architecture of the services developed is autonomous also greatly minimizes the risk of security breaches and facilitates monitoring.

Moreover, we favor their hosting in the Cloud. And in most cases, we recommend using the HTTPS protocol to secure the connection.


This service-oriented architecture (SOA) certainly has a more complex architecture, but it offers several benefits to organizations including reduced maintenance costs and “scalability.”

Happy reflection,

Denis Paul & Michel

Leave a Reply

Your email address will not be published. Required fields are marked *