||It has been suggested that this article be merged into RedDwarf Server. (Discuss) Proposed since October 2012.|
|Original author(s)||Sun Microsystems|
|Initial release||August 30, 2007|
|Stable release||0.9.11 / October 29, 2009|
Project Darkstar was an open source MMOG middleware solution written in Java. Project Darkstar began as a personal project of Jeff Kesselman in 1999. It later became a research project at Sun Microsystems, and aimed to "help developers and operators avoid a range of serious, yet typical, problems associated with massive scale online games, virtual worlds, and social networking applications today, including zone overloading, data corruption, and server underutilization." February 2, 2010, Oracle shut down the project, and a community fork has been made called RedDwarf Server.
Project Darkstar began as a personal project of Jeff Kesselman in 1999 while he was the Senior Game Integration Engineer at the Total Entertainment Network. In 2004, Sun's Game Technology Group was formed, and at that time Mr. Kesselman brought the third iteration of the project into Sun where it was dubbed the Sun Game Server. (The SGS moniker survives to this day in the package names of the Project Darkstar Server.)
Mr. Kesselman worked on the third version for a year as a solo project in Sun, debuting an early version at the Game Developers' Conference that year. Following the reorganization of the Software CTO's office in 2005, the project was moved to Sun Labs under Sun Labs Director Karl Haberl. Karl increased the man-power, adding Seth Proctor and Dan Ellard as co-researchers, as well as contractors James Megquier and Sten Anderson. This team delivered what is now known as the Early Access version, the first working server, for GDC 2005. Following this, Jim Waldo and his team became interested in the technology and technical lead was handed over to him to pursue. At about the same time, the name Project Darkstar was chosen and the open source community launched.
On February 2, 2010, in the wake of the purchase of Sun by Oracle, Jim Waldo posted on the "Project Announcement" forum that "Sun Labs engineering effort is no longer being applied to Darkstar development". A number of members of the Sun Labs team and a number of members of the Darkstar community have gone on to work on the RedDwarf Server as a successor to Darkstar.
When a Project Darkstar server implementation is run, it either starts a new network or joins one that is currently running. All networks contain clients, server implementations, a Project Darkstar stack on which the server implementations run, and several meta-service nodes that handle traffic between each node in the server stack. A server implementation is a user created program written with the Project Darkstar API. The clients include all client-side applications and games that are connected to a game server in the network.
Project Darkstar is being developed to support all features vital to a massively multiplayer game, and at the same time be scalable enough to support non-massive multiplayer online games. As such, there are many features that it supports, and many features that are being implemented and integrated into it actively.
Current Feature Set
- CPU load balancing
- Persistent data storage using Berkeley DB
- Duping prevention
- Channel communication
- Scalable data structures
- Pluggable protocols
- Administrative tools
Planned Feature Set
- Networked load balancing
- Profiling tools
- Management tools
The API of Project Darkstar is the key component for developers who use the technology. With it, they can develop game servers to communicate correctly with their client technology and have a server up and running that runs on top of the Project Darkstar game stack. The API is written to hide the concurrency of the underlying system that the Project Darkstar stack performs for the developer, so that the program can be written with the illusion that it is single threaded, even though the stack is fully parallel. The main parts of the API include task management, data persistence, and channel communication.
Control of information in a Project Darkstar server is generally handled by tasks, although in some special cases they are not necessary. They are used in instances where storage or retrieval of data must be protected from a server crash or shutdown, as tasks are saved and remembered when they are run, and can be respawned when the server is restarted in the same state as they were in before the crash. This is useful, for instance, when updating character information. If something goes wrong with the server internally, the character information is persisted and on a server restart the character information will be restored from the last state it was in before the crash.
The Berkeley DB used by Project Darkstar stores all data that is to be persisted. Anything that is to be stored in the database must also be serializable, as the database is programmed to store binary information. A managed object can be anything from player data (i.e. position, equipment) to internal server data and control logic (i.e. scalable data structure, tasks). The usefulness of managed objects is seen in the instance of a server failure. Since managed objects are updated transactionally, any corrupted data is discarded on the server restart and the managed object is rolled back to its last working state.
Channels give developers an easy way of communicating with many clients. The way channels work is by giving clients a way of subscribing to channels such that they can send messages to the channel and receive messages from the channel. When a message is sent to the channel from a client or the server, the message is multicast to all clients who are subscribed to it. It is an abstraction built on top of the communications layer to assist in the development of easy and extensible communication between many clients and the server.
Example Projects Powered by Project Darkstar
- Open Wonderland - a 100% Java open source toolkit for creating collaborative 3D virtual worlds 
Some authors have suggested that the management of Central Object Store and Distributed Random Access might not be realistically possible in a highly interactive game environment.
- Stephen Shankland (2006). "Sun's Project Darkstar aims for gaming services". CNET. Retrieved 2012-02-27.
- Brent Rabowsky; Radiosity Press (8 January 2010). Interactive Entertainment: A Videogame Industry Guide. gameindustrybook. p. 55. ISBN 978-0-9842984-1-9. Retrieved 27 February 2012.
- Tim Blackman (2006). "Scalable Data Storage in Project Darkstar". Oracle.com. Retrieved 2012-02-27.
- Andrew Davison (30 April 2007). Pro Java 6 3D Game Development: Java 3D, JOGL, JInput and JOAL APIs. Springer. p. 10. ISBN 978-1-59059-817-7. Retrieved 27 February 2012.
- Diomidis Spinellis; Georgios Gousios (22 January 2009). Beautiful architecture. O'Reilly Media, Inc. p. 52. ISBN 978-0-596-51798-4. Retrieved 27 February 2012.
- Vaclav Snasel; Jan Platos; Eyas El-Qawasmeh (20 August 2011). Digital Information Processing and Communications: International Conference, ICDIPC 2011, Ostrava, Czech Republic, July 7–9, 2011. Proceedings. Springer. p. 219. ISBN 978-3-642-22388-4. Retrieved 27 February 2012.
- Joseph Fong; Reggie Kwan; Fu Lee Wang (2008). Hybrid Learning and Education: First International Conference, Ichl 2008 Hong Kong, China, August 13–15, 2008 Proceedings. Springer. p. 57. ISBN 978-3-540-85169-1. Retrieved 27 February 2012.
- Youngkyun Baek (1 April 2010). Gaming for classroom-based learning: digital role playing as a motivator of study. Idea Group Inc (IGI). p. 272. ISBN 978-1-61520-713-8. Retrieved 27 February 2012.
- Hamido Fujita; Imran Zualkernan (15 October 2008). New trends in software methodologies, tools and techniques: proceedings of the seventh SoMeT_08. IOS Press. p. 359. ISBN 978-1-58603-916-5. Retrieved 27 February 2012.