Are you new to technical software architectures and want to understand how Simple Workspace is hosted? Here is a simple breakdown!
Simple Workspace is a collaborative production platform. What does this mysterious phrase mean?
- That it’s a software environment;
- The aim of which is to facilitate the manufacture of elements (by automating, for example);
- With several users;
- Good accounts make good friends.
The production of these elements - text files, pages… - is handled by applications1. Like your computer’s file browser2, these applications can be grouped and hierarchized. For instance, a separate project is created for each catalog and grouped into a folder for each year.
All these applications, folders, and projects are associated with an account. And it is within this account that users are defined.
An account
To sum up: an account equals a list of users and a project tree.
In the case of the first instance
When a user logs on to Simple Workspace, he or she is told two things:
The web address3 to use in his browser; Their login and password. Why a web address? Because Simple Workspace is a website like any other! But instead of saying Simple Workspace website, we’re talking about Simple Workspace instance.
So, you’ve just validated the web address in your browser, and a screen appears asking you to identify yourself. Once you’ve logged in, you’ll have access to Simple Workspace’s project browser, i.e. to the applications, folders, and projects you’re allowed to view. (This will be the same for all users of this account).
Remember: the notion of users and the project tree are attached to an account. RIGHT. But why on earth distinguish the notion of instance from that of account, if an instance is always associated with a single account? You guessed it: because an instance can be associated with several accounts!
And yes, after logging in, the user sees the applications, folders, and projects of all the accounts to which he or she has access!
An instance with three accounts
In a nutshell: an instance is a website like any other, with its address, and several accounts can be associated with it.
Where Native Americans and virtuality come into play
All requests from users connected to a Simple Workspace instance must be processed. Remember: a Simple Workspace instance is a website like any other. You need skilled software to manage a website. This is the role of Apache . It’s the link between your browser and Simple Workspace.
To run Apache, you need a computer. Instead of using a desktop or laptop computer, we use a server. (This is a computer optimized for running this type of software.) Better still, at J2S, we use a virtual machine (VM). From the point of view of the software running, nothing changes. But all the hardware is hidden. What’s in it for me?
- If there is a hardware failure, the software will not be interrupted because virtualization will automatically switch to operational hardware - pretty cool, right?
- To administer the computer, you need to log on to an administration interface. It’s easier to increase memory this way rather than to install a new memory stick.
Oh, and I forgot to mention: Apache can manage multiple websites at once, meaning several Simple Workspace instances can coexist!
A VM with four instances managed by Apache
In the VM, Apache manages the various instances (and their accounts).
On-demand
OK, but what does this mean for you as a Simple Workspace user?
Speaking of hosting, you don’t have to manage anything - everything is taken care of by J2S: we’ve chosen fast, secure disks for your data, we manage backups on a separate site, we take care of updates, security…
Then, when it comes to organizing your projects, there are three possibilities.
Dedicated account
Here is the default mode of operation. The account is exclusive to you.
Your account
It is executed in an instance that contains other accounts in a VM that manages several instances.
Dedicated instance
The instance is dedicated to your company. So all accounts managed by this instance are yours.
This instance is run in a VM that manages several instances.
Your instance and its three accounts
This is especially interesting if, for example, your company has several subsidiaries. Each one can have its own account!
Dedicated VM
Finally, with a dedicated VM, the entire virtual machine is exclusive to you. There is no software cohabitation with other companies.
Your virtual machine (VM) and its four instances
They are useful for companies with specific security requirements.
How about InDesign Server?
As for InDesign Server, Simple Workspace uses Adobe InDesign Server4 for page production. It’s similar to Adobe InDesign Desktop but without the user interface.
When Adobe InDesign Server is running, it can only handle one task at a time5, which can cause delays. If several instances of Adobe InDesign Server need to be addressed they can be run simultaneously to increase efficiency.
However, when multiple instances are executed, there may be variability in the time taken to complete tasks, and instances may also fail to respond or quit unexpectedly. To address this, J2S Dispatcher acts as an orchestrator, determining which Adobe InDesign Server instance to assign a new request from Simple Workspace.
Finally: J2S Dispatcher links Simple Workspace instances to Adobe InDesign Server instances.
Here you go!
Interested in finding out more, or in a live demonstration? Contact us : we look forward to hearing from you.
Jean-Yves Jourdain Co-founder of J2S
Jean-Yves Jourdain
Cofounder of J2S
Simple Mom or Simple Brief for instance. ↩︎
macOS’s finder for example. ↩︎
The Adobe InDesign Server topic has already been covered in this article ↩︎
Still, he does it very well 😉 ! ︎ ↩︎