Have you broken any of your Client/Server
architecture down yet?
Do your developers workflow charts look like a
Do you rely on more “outside” applications than
• Not quite the same feeling or time required
• One can not really test an API or a piece of code
in the time it takes to eat a doughnut
“..when it comes to the length of a Free Trial, many
people want to believe there is a magic number –
7, 14, 15, 30, 45, 60, 90..” – Lincoln Murphy
• Still a server, but YOU don’t manage it
• Not to be confused with headless servers
• FaaS (Function as a Service)
• IBM Cloud Functions (based on Apache
OpenWhisk) is a FaaS platform which
executes functions in response to incoming
• It costs nothing when not in use.
• The FaaS executes application logic but does
not store data.
• Developers have freedom to independently develop and deploy
services, make use of newer technologies, easy to modify
• Can be developed by a fairly small team
• Code for different services can be written in different languages
• Easy integration and automatic deployment
• Code is organized around business capabilities
• Starts the web container more quickly, so deployment is faster
• When change is required in a certain part of the application, only
the related service needs to be modified and redeployed
• If one microservice fails, the other will continue to work
• Easier to scale and integrate with third-party services
• No long-term commitment to technology stack 14
• Testing can be complicated and tedious with some many parts
• Architecture brings developers issues like mitigating fault
tolerance, network latency, load balancing, varied message
• As it grows, integration and managing the application can become
• Developers have to plan for communication between the services
• Situations may require communication and cooperation between
• The architecture usually results in increased memory consumption
• Partitioning the application into microservices is very much an art
at present 15
One server does everything, but is also the single
point of failure
When microservices are broken down, they all
become a point of failure to the server.
Have you coded for failover or secondary
services for, not if, but when, the service
High Level remember to think about:
1)Design for a collection of services
2)Separate the data
3)Communications between components
4)Design for performance and scaling
5)Security starts within the application
6)Monitor all the pieces
I was impressed by
their solution in
IBM Cloud https://www.ibm.com/cloud/solutions/
Sign up for an IBM Cloud Lite Account! https://ibm.biz/BdZqwA
App Dynamics https://www.appdynamics.com/
Erin Mckean, IBM Developer Advocate
19LEGO Slides from www.SlideHunter.com used under
Keith Brooks - CIO
Parece que tem um bloqueador de anúncios ativo. Ao listar o SlideShare no seu bloqueador de anúncios, está a apoiar a nossa comunidade de criadores de conteúdo.
Atualizámos a nossa política de privacidade.
Atualizámos a nossa política de privacidade de modo a estarmos em conformidade com os regulamentos de privacidade em constante mutação a nível mundial e para lhe fornecer uma visão sobre as formas limitadas de utilização dos seus dados.
Pode ler os detalhes abaixo. Ao aceitar, está a concordar com a política de privacidade atualizada.