Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

The Challenges of E-Government Architecture

DZone's Guide to

The Challenges of E-Government Architecture

E-Government is about the government not wasting citizens' time. Architecting for e-government means dealing with distributed systems, complex interactions between departments, and legal and organizational challenges.

· Integration Zone ·
Free Resource

SnapLogic is the leading self-service enterprise-grade integration platform. Download the 2018 GartnerMagic Quadrant for Enterprise iPaaS or play around on the platform, risk free, for 30 days.

After working for a year on the matter, I did a presentation at a small conference about the options for an architecture of e-government solutions. A 40-minute talk could not cover everything, and it is presented in the context of Bulgaria (hence 2 graphs with Cyrillic script in the slides), so I hope it’s useful anyway.

It follows a previous post of mine that proposes an architecture, which I’ve expanded here.

Here are the slides:


The main points are:

  • all data registers must be integrated somehow;
  • the integration should preferably not rely on a centralized ESB-like system;
  • privacy must be addressed by strict access control and audit logs, including access for citizens to data about who read their data and why, including notifications;
  • the technical challenge is only 20%, the rest is legal and organizational.

Despite being government-related, it’s actually an interesting technical task that not many have solved properly.

With SnapLogic’s integration platform you can save millions of dollars, increase integrator productivity by 5X, and reduce integration time to value by 90%. Sign up for our risk-free 30-day trial!

Topics:
government

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}