Currently our Verj.io server is hosted onsite here at DBC, the forms are able to integrate with our Active Directory giving us single signon internally.
We can also query our Oracle/MS SQL and Ingres databases directly, we also communicate with our databases using Web Services.
If we moved our installation to the Cloud would it still be possible to contiune with this type of system integration?
Moving Verj.io installation into the Cloud
Moderators: Jon, Steve, Ian, Dave
-
- Ebase User
- Posts: 201
- Joined: Fri Dec 20, 2013 1:29 pm
- Location: Dartford Borough Council
- Contact:
-
- Moderator
- Posts: 1342
- Joined: Wed Sep 12, 2007 12:49 pm
Re: Moving Verj.io installation into the Cloud
Is this a question about the Verj.io cloud or cloud platforms in general?
I don't have practical experience of doing this so this answer is largely theoretical. Technically I think it will be possible to access both Active Directory and databases from a cloud system. But the reasons why you might choose not to do this would include:
1. Security
2. Performance (applies more to databases than Active Directory)
Active Directory
To access an on-premise AD from the Verj.io cloud, you would need to install another Ebase system locally to act as a front-end. This would be appropriately secured and would proxy requests from the cloud. I think the main objection to this would be the degree to which it compromised security.
Other cloud platforms do seem to have technical solutions to this issue including synchronising a cloud directory with the on-premise directory or variations on the front-end theme. The same security considerations apply.
Databases
This probably means opening up ports to your on-premise databases to the internet and then securing these appropriately. The security objection applies here also, plus performance will inevitably be degraded. Other solutions such as taking periodic copies of your databases might also be possible depending on the applications involved.
I don't have practical experience of doing this so this answer is largely theoretical. Technically I think it will be possible to access both Active Directory and databases from a cloud system. But the reasons why you might choose not to do this would include:
1. Security
2. Performance (applies more to databases than Active Directory)
Active Directory
To access an on-premise AD from the Verj.io cloud, you would need to install another Ebase system locally to act as a front-end. This would be appropriately secured and would proxy requests from the cloud. I think the main objection to this would be the degree to which it compromised security.
Other cloud platforms do seem to have technical solutions to this issue including synchronising a cloud directory with the on-premise directory or variations on the front-end theme. The same security considerations apply.
Databases
This probably means opening up ports to your on-premise databases to the internet and then securing these appropriately. The security objection applies here also, plus performance will inevitably be degraded. Other solutions such as taking periodic copies of your databases might also be possible depending on the applications involved.
0 x
-
- Ebase User
- Posts: 201
- Joined: Fri Dec 20, 2013 1:29 pm
- Location: Dartford Borough Council
- Contact:
Re: Moving Verj.io installation into the Cloud
Thanks for the reply Jon, we will have to give this some consideration, but it is good to know the challenges
0 x
Who is online
Users browsing this forum: No registered users and 3 guests