Here is how I structure my code in webMethods Integration Server to get a true platform that gives you high business agility.

While you can start simple with just one package, this soon becomes a problem. Here is real-world advice how to structure your code base. This reduces complexity, makes your solution much easier to maintain, and reduces the risk of bugs. And as a special bonus, you end up with a real integration platform. All based on real-world experience.

You can find the complete article at Structuring packages in webMethods Integration Server

Nice article on WebMethods basics Christoph. We should have a discussion on best coding practices for maintainable and scalable code writing by applying integration patterns and frameworks.

There are multiple approaches and need to factor in few things:

• Is only one IS/MSR or multiple instances that communicate with each other?
  
  • is that thru Publish /Subscribe using native messaging (broker/UM), JMS  or streaming
• are APIs to be uesd for IS to IS communication?
• How are API/Service signature contracts to be shared?  Is that thru shared packages?
• How are shared utilities managed?

I have seen envrironments from a single IS instance to a large cluster with over 400+ packages overall.

This makes me think that I should migrated over this article from tech community to here

https://tech.forums.softwareag.com/t/webmethods-packages-from-a-developers-perspective/257088