Pabosa

From 2value wiki 2
Revision as of 21:00, 4 April 2013 by 2value>Interwiki linking script (→‎Open source architecture)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Subpages Pabosa

Process automation based

System integration is a weak point in the open source field. Readily available open source frameworks and extensions to those frameworks are quite easily leading to chaos. Technicians tried to overcome integration problems by building bridges between frameworks. Not fully aware that maintainability decreases with every bridge that is added in the process.

Lessons learned

2Value has been there and done that. And took the full responsibility... And we have learned some lessons.

  1. Stick to what already gives you competitive edge
  2. Process first, then automate
  3. Less is more
  4. Multiple data stored? No problem if you do it right!
  5. Multiple sign on? Inevitable.

Focus

2Value is a virtual firm working in the field of open source websystems, php based. Our webbased architecture serves small & medium businesses and (semi) governmental organisations.

Definitions

SSI
Single Sign In ("let me")
SSO
Single Sign On ("remember me")

Open source architecture

Architecture small.jpg

The Sync middleware is the kernel of the OSA. It is a mysql INNODB table that hold copies (!) of data primairy stored elsewhere. The copy is as a kind of commit of data to used in the databaselevel of other frameworks of the architecture.

Applications get their data via API calls to Sync

E.g. Atrium CRM holds email adresses of customers. Sync has them too. The saas solution Mailings offers new subscribers. Our OSA checks new subscribers against Sync (and not against Atrium CRM!).

Technical goals

  1. Reusable XML schemas instead of one trick pony bridges like sugar2Value, magebridge
  2. use available xml schemas
  3. Berkly DB for Open LDAP?