Shared GR and IDE node (alternative architecture)

As a second alternative to using the recommended multi-user development architecture, you can utilize a centralized GR in combination with centralized IDE. Developers then use RDS to access these resources.

This arrangement, with both the GR and IDE shared by developers, allows better coordination between team members that having a local IDE for each developer, although like the other alternative architecture described above, it also has its share of disadvantages including cost and congestion, as listed below.

Sharing both the GR and IDE requires more resources than simply sharing the GR however. The maximum number of concurrent users will vary between two and five, depending on computer hardware resources, whether or not you are using SQL Server Express (which will support fewer users) or a full version of SQL Server, and the size of the galaxy.

This approach has he following advantages and disadvantages:

Advantages:

• Single repository: All work is stored in, and accessible from, a centralized repository.

• IT infrastructure: with a shared GR and IDE, there are fewer potential bottlenecks between the two Application Server components.

• Multiple projects and versions: the centralized IDE allows better project/version management.

Disadvantages:

• Congestion: since all users are accessing the same GR and IDE, system response can slow down. A limit of five concurrent users is recommended.

• Cost: RDP CALs (client access licenses)