Distributed Applications Programmers

Part IV from How to be Programmer

Distributed application programming is considered by many to be one of the hardest to learn and requires diverse knowledge in computer and communication technologies.
1. Take a speed introduction to telephony systems and their hardware. This step is optional. However, it is very useful in understanding network topologies.
2. Familiarize yourself with networking hardware architectures and devices such as hubs, switches and routers.
3. Take a course in networking protocols and essentials. You need a good understanding of the Open Systems Interconnection (OSI) model, Ethernet, IP, TCP, UDP and HTTP before you start programming distributed applications.
4. Learn the XML language and familiarize yourself with it.
5. Do step 2 and 3 in "prepare yourself for desktop application programming"
6. Start by learning a shell scripting language. For Windows based programming, that would be any script that works with Windows Scripting Host. For Linux based programming, Bash scripts and Perl will be sufficient. Javascript is strongly recommended for this in both platforms for the following reasons:
o It is supported by almost any scripting host in any operating system (Windows Scripting Host supports javascript by default, most Linux distributions has a package for javascript scripting console support).
o It is considered to be easier to learn by many developers.
o It has an ALGOL derived syntax which familiarizes you with much more other programming languages when you need to choose a second programming language (C, C++, C#, Java and J# all have ALGOL derived syntax)
o By learning javascript, you familiarize yourself with client-side scripting of web pages which is a bonus side-effect!
7. Apply only procedural programming using your scripting language of choice at first. Later, you can use more advanced programming techniques and paradigms according to your scripting language and what it supports. All scripting languages has some procedural programming aspects at some level.
8. Use the scripting language you learned to write scripts that perform communications between machines. Learn what is necessary for doing that. Simple communications will suffice.
9. Make a transfer to a desktop scripting/programming language. Preferably, one that is a multi-paradigm language such as Python. Take a simple introduction to that second language. Java is considered by most programmers to be the language of choice for many reasons. However C# is gaining momentum fast in this field. Java and C# are preferred for the following reasons:
o They are object oriented programming languages which shields programmers in large teams from implementation details as they both supports components (units of code, pre-compiled, that perform a certain task and can be used in other programs)
o They support event driven programming as well as OO and procedural programming at some level.
o The framework that the language is built upon is distributed by nature (in the case of Java).
o The availability of many ready-made packages that deal with networking both as open source code and framework built-in packages; makes it easier for programmers to build upon the work of others.
10. Concentrate more on the core features of the language, especially those supporting networking. Pay less attention to user interface elements such as outputting, window design and techniques, and user interface elements.
11. Take a course on distributed applications design and architectures. This can be done using books, online tutorials or academic courses. However, understanding the architecture of distributed applications and its concepts is necessary.
12. Learn about building serviced components and services using your programming language of choice.
13. Learn one or more of the following technologies. It is recommended that you get at least an introduction to all of them. Most distributed application programmers do not stop at one or two programming languages, but learn at least one programming language on each operating system. That is because if you want your application to be "distributed", you should provide a version of it at least for each major operating system.
o Common Object Request Broker Architecture (CORBA)
o Simple Object Access Protocol (SOAP)
o Asynchronous JavaScript and XML (AJAX)
o Distributed Component Object Model (DCOM)
o .NET Remoting
o XML Web Services


Source : wikihow.com