BPM used as monolithic L4G

With my last months studying BPM products, I'm quite impressed by product marketing fliers and other 'best pratices'/ training materials putting emphasis to the fact that traditional, code driven, approach to develop business application is bad, and with BPM it is better to have a unique artifact in a central repository, for managing all the elements of a business application such as UI, information model, service definitions, connectors, business rules, process logic.
I'm confused by the lack of applying basic design and architecture best practices such as separation of concern, and artifact life cycle. With monolithic process application, any change to the information model, or the UI enforce migrating all the process instances running on the runtime server. This is interesting to note that SOA reference architecture, defines, UI services separated from process, from data, and rules services. Which makes perfectly sense for re usability, components life cycle, flexible, sustainable architecture.
Do not apply bad patterns because of such BPM product, use BPM for workflow orchestration, visibility into your process, monitoring the business activities inside the process, and think about valuable architecture and design, and do not blindly follow marketing sirens.

Comments

Post a Comment

Popular posts from this blog

Our team just publicly published a white paper on how to use Watson Discovery on the IBM Cloud platform to create content collections and custom cognitive applications. It is related to the training tutorial I co-developed with colleagues at IBM but adds other best practices and business use cases. You can read this pdf here:  IBM-Advantage-Paper-for-Cognitive-Discovery.pdf Please give us feedback.
Read more

Event-driven solution is still a hot topic

Image
Recently I have to justify why Event-Driven Architecture is still a hot topic on the current market: as I work with a lot of companies in financial, healthcare or retailer industries, I see strong adoption for loosely coupled, event-driven microservice solutions, with new data pipeline used to inject data to modern data lakes, and the adoption of event backbone technology like Apache Kafka, or Apache Pulsar. With my team, we are working on reference architectures, reference implementations, and first-of-a-kind solutions based on event-driven implementations. Over the last year, this space is evolving a lot with the adoption of serverless, knative eventing, cloud-native technologies, microprofile 3.x messaging... In this blog, I want to introduce our EDA work and references to some assets you may be able to leverage for your own project. I will continue future blogs to present in more detail some of those assets and best practices we have to develop for customer engagements. Event-drive
Read more

Hybrid Cloud Integration Solution Implementation

Hybrid cloud integration represents interesting challenges on how to protect existing SOA services with new cloud-native web applications and microservices. Co-existence is a must on today IT landscape. I'm leading an effort at IBM to implement a complete hybrid solution where architects and developers will be able to learn best practices around: how to develop a SOAP app in Java using JPA, JAXWS deployed on WebSphere Liberty how to develop gateway message flow within IBM Integration Bus how to define API product with API Connect, and use secure communication with TLS for backend APIs how to set up secure connection from IBM Cloud public to on-premise service using IBM Secure Gateway how to develop a Single Page Application with Angular 5 using a Test Drive Development approach with nodejs/expressjs back end how to secure the web app with passport how to access existing LDAP service for user authentication how to perform CI/CD in the hybrid world how to monitor all thos
Read more