Doorgaan naar hoofdcontent

Cordys Solution Architect Accelerator Program

On the 30th and 31th of May 2012 the first Cordys Solution Architect Accelerator Program took place at Putten, The Netherlands. A couple of potential Cordys Solution Architects of partners were invited to follow this program. I was one of the "lucky" ones. This program is setup so that more solution architects are trained and can be used in projects, because there is a miss in the field of Cordys projects.
This was a first session and this session will also be held in US, UK and India.
As always Cordys had organized this event very nice. There was also place for discussions and a social event in the evenening with bowling and BBQ.










The program was:

Day1:
* High Level architecture overview of BOP4
* Security Models
* Case Management
* Workflow (part 1)
Evening: Bowling, BBQ and Beers

Day2:
* Workflow (part 2)
* CWS
* Cordys Cloud Provisioning

Next steps:

  • The architecture team will help in developing more architectural patterns and best practices of the Cordys platform. 
  • All member will get certified (Fundamentals, BPMS, Solution Architect)
  • All architects will get a Cordys buddy to help the architects with challenges
  • Next sessions will be organized to discuss more topics




Thanks Cordys for this great initiative and opportunity to become a Solution Architect for the Cordys produkt and help Cordys in moving forward !

Reacties

Populaire posts van deze blog

OSB 10gR3 and SWA and MTOM

This blog is about using soap with attachments and the use of MTOM within the OSB (10gR3). A service is created that accepts a soap with attachment (DocumentService) and translates it to a service that accepts a binary element. MTOM is used for performance reasons for the second. Some notes: * For the use of attachments you need RPC-style document instead of the usual document-style. This due to the fact that the document-style limits a message to a single . * A service can not have both SWA and MTOM within OSB. First a WSDL is setup for the DocumentService: The $attachments variable holds the attachments and the body holds the attachment data. Also other data is stored within the attachment element (see h

Microservices mindmap

"The tree" - See also   my photo page When you are fairly new within the Microservices land, there are a lot of terms fired at you. So also for my own understanding i have made a mindmap. I think it has a good status now, so that i can share it with you. As always feedback is very welcome ! You can download the mindmap here .

Book review: Data Management at Scale (Piethein Strengholt)

 This blog is a review of the book "Data Management at Scale (See also at bol.com ) Data Management is a hot topic nowadays and this book does a fantastic job at adding value to this topic. It is a must read and one of the few technical books I finished reading in a weekend. The book gives a fantastic overview on how to implement a Data Mesh data architecture. The Data Mesh concept is explained by Martin Fowler here . The book is a good mix between conceptual and implementation architecture level. It gives a lot of examples of how this architecture at scale can work, for both small and big companies. It is practical and I used it to implement it at one of my customers. The book describes an architecture in which the focus is on the DIAL (Data- and Integration Access Layer).  On a high level the book covers the following topics: The key principles for data management at scale - Domain-Driven Design  - Domain Data Stores - Meta data management Ready Data Store The concept of servin