This pattern consists of two parties; master and slaves. The master component distributes the work among identical slave components, and computes a final result from the results which the slaves return.
Usage
In database replication, the master database is regarded as the authoritative source, and the slave databases are synchronized to it.
Peripherals connected to a bus in a computer system (master and slave drives).
This pattern consists of two parties; a server and multiple clients. The server component will provide services to multiple client components. Clients request services from the server and the server provides relevant services to those clients. Furthermore, the server continues to listen to client requests.
Usage
Online applications such as email, document sharing and banking.
This pattern can be used to structure programs that can be decomposed into groups of subtasks, each of which is at a particular level of abstraction. Each layer provides services to the next higher layer.
The most commonly found 4 layers of a general information system are as follows.
Presentation layer (also known as UI layer)
Application layer (also known as service layer)
Business logic layer (also known as domain layer)
Data access layer (also known as persistence layer)
Usage
General desktop applications.
E commerce web applications.
Before I go ahead and discuss the three simple rules for mastering Git and Github, please consider completing the following tasks:
And now, without much further ado, the three simple rules to master Git and Github while learning how to code…
Even if you are working on small and simple projects, and even if you are working alone, following those three rules every time you code will make you a Git and GitHub master user very quickly.
Rule #1: Create a Git repository for every new project
This first rule is quite straightforward, but making a habit out of it is very important. Every time you start working on something new — your portfolio, a learning project, a solution to a coding challenge, and so on — you should create a new Git repository and push it to GitHub.
Having a dedicated repo is the first step to being able to use version control for every line of code you write. Using version control is how you will work once you join a company and start working on real-world projects. Learn this early and make it a habit.
Quick Note: if using the terminal becomes a hassle and makes you less likely to use Git for all your projects, consider using the Github Desktop app.
Rule #2: Create a new branch for every new feature
Let’s say you are working on your portfolio and you want to build a new “Contact me” section/component. Create a dedicated branch for this new feature, give it a meaningful name (e.g. contact-me-section), and commit all the code to that specific branch.
If you don’t know what branches are, go back to the Github Flow reading that I recommended before.
Working with branches allows you and your team members to work on different features in a parallel way while keeping the specific code for each feature isolated from the rest. This makes it harder for unstable code to get merged into the main code base.
Even if you are the only person on your team, getting used to using feature branches will make the Github Flow process a breeze once you join a real job.
Rule #3: Use Pull Requests to merge code to Master
Every repository starts with a master branch by default. You should never push changes directly to the master branch. Instead, you should use feature branches as described above, and open a new Pull Request to merge the feature branch code with the master branch code.
In a real job, someone will look at your Pull Request and do a code review before approving it. GitHub will even run automated tests to your code and let you know if there is an issue with it. You will also be notified if there is any merge conflict between your code and the code in the master branch. This can happen, for example, if another developer pushed a change to the master branch that affects a file that you also modified.
After your code has been reviewed, tested, and approved, your reviewer will give you thumbs up for you to merge the Pull Request, or they will directly merge your pull request.
Even if you are working alone, get used to creating Pull Requests as a way to merge your changes to the master branch. This, by the way, is the basic workflow used by almost every open source project. If you ever contribute to one (you should!), understanding this three rules will make it really easy for you to get your contribution accepted without any problem.
If you are still confused, just start slow and keep the three rules in mind. Don’t try to think about “How” to do things yet and focus on “What” to do and “Why” it’s important for now.
Once the “What” and the “Why” are clear, you can figure out the “How” when the times comes to do things. Once you have repeated this process 2–3 times, it will become really easy and natural for you.
I have a proud to announce that I received a recognition as Technical Rock Star award for Cloud Computing.
The technical expertise that you shared this month is making an impact on the lives of developers around the world!! Your technical contributions encouraged developers to learn more, improve their skills, and achieve their goals faster.
You ROCKED it!! Expertise like yours shows that IBMers are superstars. This Gold Second Place Album is to recognize your achievement. Please print the attached certificate and share it with great pride.
We want to make sure you are seen as the expert that you are, by all IBMers, so please expect to be contacted by the Technical Rock Star team to capture your success story.
Thank you for participating in this month’s program. You are playing a critical role in the transformation of IBM! I encourage you to keep participating in this year long program! YOU make a difference. WE SALUTE YOU!!!
The challenge was reach and engagement on social media to enhance and promote IBM’s Cloud thought leadership and get the word out about Cloud, IBM Bluemix and its services like Data Services.
Through my social networks (Twitter, Google+, Linkedin, Stack Overflow, my personal blog etc), I’ve shared resources that I’m reading such as webinars, blogs, tutorial, code samples, videos, books, papers, articles regarding Cloud computing. I tried share my experiences and insights to Developers, Architects Engineers and students.
Rather than receiving the award, I’m really very proud to receive the congratulations of several people at IBM that I admire.
They took a minute from the busy day to wish congrats to me. I appreciate it from the bottom of my heart.
A tech guy as me to be recognized as Technical Rock Star is awesome.
I’m feeling like Rock Star.
Thank you so much.
HP passa IBM na liderança do mercado de servidores
Fabricante faturou US$ 3,4 bilhões no primeiro trimestre deste ano; empresa também lidera no número de servidores embarcados
No primeiro trimestre de 2010, a HP tomou a dianteira na liderança no mercado global de servidores, de acordo com a consultoria Gartner que tomou como base o faturamento das companhias com este segmento. As receitas da fabricante alcançaram US$ 3,4 bilhões e passaram a representar 31,5% do total do mercado. Com isto, a IBM caiu da primeira para a segunda colocação – hoje a Big Blue detém 28,4% de market share. No mesmo período de 2009, a HP tinha 28,8% do mercado, enquanto a IBM liderava com 30,7%.
O Gartner atribui a queda da IBM ao fato de os clientes terem preferido não comprar neste momento mainframe e a linha Unix, uma vez que a empresa se prepara para lançar a próxima geração mais adiante neste ano.
Os cinco fornecedores globais de servidores mais bem-colocados são, respectivamente: HP, IBM, Dell, Fujitsu e Oracle.
Continue lendo aqui.
Kleber Rodrigo de Carvalho
Estou finalizando as disciplinas do curso de MBA em Sistemas Corporativos de Alto Desempenho – Mainframes e Servidores de Grande Porte na FIAP. Como exerci o papel de monitor do curso, quero agradecer a todos os professores, que fizeram parte do curso.
– Methodology and Research Design (8 hours) – Aldilene R Adorno Guirau
– Unit 1 – IBM System Z – Mainframe Servers (76 hours)
– – IBM System Z Architecture (32 hours) – Prof Monica Veselic
– – IBM System Z Advanced Architecture (44 hours) – Prof Rafael Lima
– Unit 2 – RISC/UNIX/Linux System Servers (48 hours)
– – IBM Power System (RISC/AIX) e I5 OS/Linux (24 hours) Prof Botão
– – HP System 9000 Integrity HP/UX (12 hours) – Prof Gustavo Yazbek
– – SUN System SunFire Solaris (12 hours) – Prof Marcelo Resende
– Unit 3 – Intel-based Windows HPC Servers (48 hours)
– – IBM Modular System/Blades High-Performance Servers (12 hours) – Prof Kiran
– – Intel DELL High-Performance Servers (12 hours) – Prof André Santana
– – Intel HP High-Performance Servers (12 hours) – Prof Fabricio Durante
– – Intel UNISYS High-Performance Servers (12 hours) – Prof Marcel Valverde
– Unit 4 – Storage Technology (64 hours)
– – EMC Symmetrix and Clariion Storage (16 hours) – Prof Alexandre Costa
– – Sun Storagetek Storage (16 hours) – Paulo Otto
– – HDS Hitachi Storage Data Systems (16 hours) – Prof Paulo Otto
– – IBM DS-8000 Storage (16 hours) – Prof Isabel Zorz
– Unit 5 – Network, CICS, WebSphere/MQ, ITIL (48 hours)
– – Network architecture TCP/IP, SNA and CICS (24 hours) – Prof Paulo C Costa
– – WebSphere/MQ – application integration (8 hours) – Prof Carina L. Carvalho
– – ITIL V3 and SLA fundamentals (16 hours) – Prof Adriano Neves
– Unit 6 – Management and Operating Control Tools (64 hours)
– – CA/Unicenter Network and Resource Management (8 hours) – Prof Teodoro Novo
– – IBM Tivoli/Omegamon Network and Resource Management (8 hours) – Prof. Claudinei Dias
– – HP OpenView Network and Resource Management (8 hours) – Prof – Alexandre Barbieri
– – BMC MainView Network and Resource Management (8 hours) – Prof Claudinei Dias
– – Compuware Control and Operational Performance Tools (8 hours) – Prof. Claudinei Dias
– – BMC Control and Operational Performance Tools (8 hours) – Prof Claudinei Dias
– – CA Control and Operational Performance Tools (8 hours) – Prof Teodoro Novo
– Unit 7 -Relacional Databases
– – IBM DB2 (20 hours) – Prof Itsche Baran
– – Oracle (20 hours) – Prof Vidal Olavo P. Gonçalves
Deixei as disciplinas em inglês, porque escrevo bastantes sobre esse curso com meus amigos de outros países, assim é mais fácil de eu mostrar o que eu estou estudando.
Quero deixar aqui o meu muito obrigado a todos os professores. Tenho que agradecer a todos pelo conhecimento que eles compartilharam com todos nós alunos.
Paulo Sérgio Pecchio – Diretor da FIAP Corporate
Francesco Querini – Coordenador
Maria Isabel Barrenada Ros – Gerente da FIAP Corporate
Acima estão as pessoas da área administrativas que me ajudaram com várias dúvidas dos alunos. Meu muito obrigado vai para principalmente para a Isabel e Pecchio, que me ajudaram muito nessas tarefas.
Kleber Rodrigo de Carvalho
Eu terminando minhas disciplinas no curso de MBA em Sistemas Corporativos de Alto Desempenho – Mainframes e Servidores de Grande Porte na FIAP. O curso de MBA (Master of Business Administration) que é o Mestrado em Administração de Empresas é um grau acadêmico ao nível do mestrado destinado a administradores e executivos na área de gestão de empresas. Difere do MBA (Master of Business Administration), que traduzindo também significa mestrado em administração de empresas. Apesar do MBA ter grau de “mestrado” em diversos países, no Brasil ele é enquadrado como “Especialização”, ou seja, uma “Pós-graduação Lato Sensu”. Quem o obtém, portanto, não tem o título de Mestre reconhecido no Brasil.
Mesmo com essa diferença entre o MBA feito fora do Brasil e o MBA feito no Brasil, o foco do curso é “business”, ou seja como o gestor de TI pode usar a Arquitetura de Servidores de Alto Desempenho para impulsionar o seu negócio. O nome do curso é MBA em Sistemas Corporativos de Alto Desempenho – Mainframes e Servidores de Grande Porte, mas gosto de falar Arquitetura de Servidores de Alto Desempenho para resumir do que o curso trata. Também já vi traduções para este curso como a Data Center and Enterprise Systems Management MBA ou como eu mesmo já escrevi High Availability in Enterprise Systems.
O curso é desenvolvido para habilitar o profissional a avaliar – com um enfoque abrangente – a atual infraestrutura tecnológica na qual atua e propor melhorias em seus mais diferentes componentes, sejam de hardware, de software, de comunicação de dados e redes e da infraestrutura de TI em geral, segundo os melhores conceitos de gestão empregados pelas maiores empresas do mercado. Na verdade no curso temos várias disciplinas de arquitetura dos servidores tanto da perspectiva de harware como de software nas 3 principais plataformas.
Através dessas 3 principais plataformas (RISC, x86 e Mainframe), vemos também comunicação de dados e redes e da infraestrutura de TI em geral nessas plataformas.
No site do curso de MBA, tem o conteúdo programático, que se divide em uma carga horária total de 380 horas.
Esse curso me deu uma ótima visão sobre Servidores RISC, com sistemas operacionais UNIX e LINUX, Servidores Intel / x86 / Windows based de alta performance, com sistema operacional Windows/Server e Servidores Mainframes IBM System Z, com sistemas operacionais Z/OS e LINUX, além de abordar soluções de STORAGE armazenamento de alta capacidade nessa 3 plataformas também. Para quem saber mais sobre o conteúdo programático do curso, pode acessar o site do curso ou a tradução que eu fiz do contéudo programático para o inglês.
Já estou usando conceitos aprendido durante o curso no meu dia a dias, e tenho certeza que esse curso ajudou muito no meu crescimento profissional. Fica ai ai dica para quem quer estudar um pouco sobre Arquitetura de Servidores de Grande Porte.
Kleber Rodrigo de Carvalho
My blog is highlighted in developerWorks Java main page.
http://www.ibm.com/developerworks/java/
Since developerWorks implemented the social network called mydeveloperWorks (basead on Lotus Connection solution) I have participated in this social media. If you are in IT area, I really advise you to create you profile and get connected. MyDeveloperWorks is a fun way to keep updated and to learn which are the hot tech topics.
Kleber Rodrigo de Carvalho
OreillyMedia presented John Adams (Twitter) “Fixing Twitter: Improving the Performance and Scalability of the World’s Most Popular Micro-blogging Site”
Kleber Rodrigo de Carvalho
