![class CoffeeApp {
public static void main(String[] args) {
CoffeeMachine machine = new CoffeeMachine();
Coffee espresso = machine.brewCoffee(CoffeeSelection.ESPRESSO);
}
}
Abstractions
1. The abstraction
1. Coffee!
Example based on: https://stackify.com/oop-concept-abstraction/](https://image.slidesharecdn.com/tudelftpresentation-cloudserverless-181101141453/85/TU-Delft-Presentation-Cloud-Serverless-22-320.jpg)
![Abstractions
class MyBusinessLogic {
private final SortingStrategy strategy;
public MyBusinessLogic(SortingStrategy sorting) {
this.sorting = sorting;
}
public void arrange(int[] input) {
output = sorting.sort(input);
// do something with the output
}
} 1. Actual sorting
strategy used is
injected
2. Sorting strategy
is used](https://image.slidesharecdn.com/tudelftpresentation-cloudserverless-181101141453/85/TU-Delft-Presentation-Cloud-Serverless-23-320.jpg)
![Interfaces
class MyBusinessLogic {
private final SortingStrategy strategy;
public MyBusinessLogic(SortingStrategy sorting) {
this.sorting = sorting;
}
public void arrange(int[] input) {
output = sorting.sort(input);
// do something with the output
}
} 1. We only accept
the
“SortingStrategy”
type](https://image.slidesharecdn.com/tudelftpresentation-cloudserverless-181101141453/85/TU-Delft-Presentation-Cloud-Serverless-31-320.jpg)
![Interfaces
interface SortingStrategy {
public int[] sort(int[] list);
}
1. I accept a list of
numbers
2. I return a list of
numbers](https://image.slidesharecdn.com/tudelftpresentation-cloudserverless-181101141453/85/TU-Delft-Presentation-Cloud-Serverless-32-320.jpg)
TU Delft Presentation - Cloud & Serverless
- 2. $ whoami Sander Knape ● Technical Team Lead Cloud @ Coolblue (~3 years) ● Student @ Utrecht University ○ Bachelor Cognitive Artificial Intelligence ○ Master Business Informatics ● Backend + Frontend development ● Moved more towards (dev)ops @ Coolblue ○ Operational ○ Cloud computing
- 4. Agenda Agenda ● Introduction ● Abstractions & Interfaces ● Cloud Computing ● Serverless Technology
- 6. Online + 9 physical shops
- 9. Delivery
- 10. More delivery
- 11. Revenue in the years
- 15. So why the Cloud? Towards the future ● Scalability ● Managed services ● Getting to the next level
- 16. Team Deployment
- 18. What is an abstraction? “Abstraction is the process of taking away or removing characteristics from something in order to reduce it to a set of essential characteristics.” https://whatis.techtarget.com/definition/data-abstraction
- 19. What is an abstraction?
- 20. What is an abstraction?
- 21. We can verb-ize that “To abstract (away), specifically in computer science, refers to intentionally obscuring the details of how something works in order to simplify things conceptually.” https://en.wiktionary.org/wiki/abstract_away
- 22. class CoffeeApp { public static void main(String[] args) { CoffeeMachine machine = new CoffeeMachine(); Coffee espresso = machine.brewCoffee(CoffeeSelection.ESPRESSO); } } Abstractions 1. The abstraction 1. Coffee! Example based on: https://stackify.com/oop-concept-abstraction/
- 23. Abstractions class MyBusinessLogic { private final SortingStrategy strategy; public MyBusinessLogic(SortingStrategy sorting) { this.sorting = sorting; } public void arrange(int[] input) { output = sorting.sort(input); // do something with the output } } 1. Actual sorting strategy used is injected 2. Sorting strategy is used
- 24. Leads to re-usability function doSomethingEasy() { result = doSomethingComplex(); // something easy } function doSomethingElseThatIsEasy() { result = doSomethingComplex(); // something else that is easy } ... function doSomethingComplex() { // something complex } 1. Complex result received, without any required knowledge
- 25. Abstractions
- 26. Microservices
- 27. Microservices My service Order service Customer service
- 28. Interfaces
- 29. Interfaces “A situation, way, or place where two things come together and affect each other” https://dictionary.cambridge.org/dictionary/english/interface
- 30. Microservices My service Order service Customer service
- 31. Interfaces class MyBusinessLogic { private final SortingStrategy strategy; public MyBusinessLogic(SortingStrategy sorting) { this.sorting = sorting; } public void arrange(int[] input) { output = sorting.sort(input); // do something with the output } } 1. We only accept the “SortingStrategy” type
- 32. Interfaces interface SortingStrategy { public int[] sort(int[] list); } 1. I accept a list of numbers 2. I return a list of numbers
- 33. Interfaces
- 34. What is an abstraction?
- 35. Datacenter
- 36. Datacenter Building Power Physical security Cooling
- 38. Racks and servers Switches & routers Servers Cables
- 40. Virtualization
- 44. Datacenter abstraction Building Power Physical security CoolingDatacenter Hardware Switches & routers Servers Cables Virtualization Hypervisor OSOS Application
- 46. What is cloud computing?
- 47. Data centers, many data centers
- 49. Cloud providers
- 50. Public vs. Private vs. Hybrid
- 51. What is the Cloud? Cloud Characteristics ● Self-service ● Pay for what you use ○ Rapid elasticity ○ “Infinite” capacity ● Network-driven ● Managed services ○ Maintenance (e.g. OS patches, version upgrades) ○ Performance ○ Security
- 52. Show by example Let’s create a queue!
- 53. What is the Cloud? Cloud Characteristics ● Self-service ● Pay for what you use ○ Rapid elasticity ○ “Infinite” capacity ● Network-driven ● Managed services ○ Maintenance (e.g. OS patches, version upgrades) ○ Performance ○ Security
- 54. Self-service SQS
- 55. Pre-self-service 1. Request redundant hardware 2. Get hardware setup in the datacenter 3. Install OS 4. Find, Evaluate & Install queue software 5. Replicate queue software for redundancy (+ more) 6. Keep OS up to date a. Security patches b. Update for new features Getting a queue on-prem
- 56. Pay for what you use
- 57. Pay for what you use Own Datacenter Cloud
- 58. Autoscaling for our Webshop
- 60. Environmental benefits Cloud Providers can more easily ● Optimize for large scale ● Distribute requirements across hardware, essentially requiring less overhead ● Innovate in energy reduction and green energy
- 61. Network-driven
- 63. Managed services
- 64. What is the Cloud? Cloud Characteristics ● Self-service ● Pay for what you use ○ Rapid elasticity ○ “Infinite” capacity ● Network-driven ● Managed services ○ Maintenance (e.g. OS patches, version upgrades) ○ Performance ○ Security
- 65. Datacenter abstraction Building Power Physical security CoolingDatacenter Hardware Switches & routers Servers Cables Virtualization Hypervisor LinuxOS Application
- 66. Datacenter abstraction Building Power Physical security CoolingDatacenter Hardware Switches & routers Servers Cables Virtualization Hypervisor LinuxOS Application
- 67. Datacenter abstraction Building Power Physical security CoolingDatacenter Hardware Switches & routers Servers Cables Virtualization Hypervisor LinuxOS Application
- 70. What is Serverless? “A managed service that abstracts away the entire concept of the function of a server in the development lifecycle”
- 71. What is Serverless? Serverless == Managed Service ?
- 72. What is Serverless? RDS vs. DynamoDB
- 73. Managed services vs. Serverless Managed Services Serverless
- 74. Function as a Service Lambda time
- 75. Managed services vs. Serverless vs. FaaS Managed Services Serverless FaaS
- 76. Lego blocks
- 77. Pick one
- 78. Should you use Serverless? It depends.
- 79. Monolith vs ...
- 80. … Microservices
- 81. This is (mostly) in the past now
- 83. Pro’s & Cons Serverless tradeoffs ● Vendor lock-in ● Interface size ● Network overhead ● Architectural vs. Application complexity ● Local testing
- 84. Vendor lock-in
- 86. Portability
- 88. Portability Amazon Web Services Google Cloud
- 90. Interface size
- 91. Interface size
- 92. Network overhead http High performance Less performance
- 94. Architectural complexity ● Deployment pipelines ● Monitoring, logging, alerts ● Interconnectivity ● Testing ● ...
- 95. Foundation
- 96. Local testing
- 97. Best of both worlds EC2 Lambda &
- 98. So why the Cloud? And why Serverless? Towards the future ● Scalability ● Managed services ● Getting to the next level
- 99. Sander Knape | s.knape@coolblue.nl | www.coolblue.nl
Editor's Notes
- #2: https://d0.awsstatic.com/whitepapers/architecture/AWS_Well-Architected_Framework.pdf https://aws.amazon.com/architecture/well-architected/
- #10: Online shops from www.pdashop.nl to www.bladblazershop.nl Currently active in Belgium & Netherlands
- #11: Online shops from www.pdashop.nl to www.bladblazershop.nl Currently active in Belgium & Netherlands
- #12: And this year we passed for the first time in the history of coolblue the 1b revenue. As you can see we grow 50% YoY. This means that every year we need to invest in the infrastructure to support this growth. Looking back to the christmas of 2016 we heavenly invested in physical hardware for supporting our MySQL cluster. And at that moment we couldn’t grow more in our current Datacenter.
- #13: Coolblue is in AWS. So that means some examples in this presentation will be focused around AWS.
- #18: When? Before July 2017.. Set by the team!
- #19: It’s a 76 pages whitepaper created by AWS and helps developers, operation engineers, architects etc to build up to par Cloud architectes. It contains best practices and guidance on 5 conceptual areas, called the “5 pillars of the Well-Architected Framework”.
- #20: In buying milk, a lot is abstracted away. The cow is not involved in you drinking milk.
- #21: Same with setting coffee.
- #22: It’s a 76 pages whitepaper created by AWS and helps developers, operation engineers, architects etc to build up to par Cloud architectes. It contains best practices and guidance on 5 conceptual areas, called the “5 pillars of the Well-Architected Framework”.
- #25: This leads to re-usable code
- #26: Of course abstractions are not only visible in code. When building a website (Layer 7), you don’t need to be aware of exactly how the other layers work. You don’t even need to know how TCP/IP, UDP e.t.c. works. At most only the interface into the underlying layer.
- #27: If there is an “order” service that you query, you have no idea how the orders are stored, what language the service is written in, e.t.c. But you do know you can do an HTTP call and that you can query a specific URL. In other words: you specified a contract.
- #30: It’s a 76 pages whitepaper created by AWS and helps developers, operation engineers, architects etc to build up to par Cloud architectes. It contains best practices and guidance on 5 conceptual areas, called the “5 pillars of the Well-Architected Framework”.
- #31: HTTP status codes are also applicable to web services
- #32: We have already seen an interface in a previous example
- #33: This is an interface
- #34: This is an interface
- #35: The coffee machine also has an interface. It accepts beans and water.
- #36: In Cloud, IaaS and PaaS are often used as terms.
- #37: In Cloud, IaaS and PaaS are often used as terms.
- #38: In Cloud, IaaS and PaaS are often used as terms.
- #39: In Cloud, IaaS and PaaS are often used as terms.
- #40: In Cloud, IaaS and PaaS are often used as terms.
- #41: In Cloud, IaaS and PaaS are often used as terms.
- #42: In Cloud, IaaS and PaaS are often used as terms.
- #43: In Cloud, IaaS and PaaS are often used as terms.
- #44: In Cloud, IaaS and PaaS are often used as terms.
- #46: When? Before July 2017.. Set by the team!
- #51: We’ll focus mainly on public cloud.
- #57: Give example of Coolblue where we used to buy a lot of hardware before Christmas
- #58: Give example of Coolblue where we used to buy a lot of hardware before Christmas
- #59: Give example of Coolblue where we used to buy a lot of hardware before Christmas
- #60: Give example of Coolblue where we used to buy a lot of hardware before Christmas
- #61: Give example of Coolblue where we used to buy a lot of hardware before Christmas
- #62: Give example of Coolblue where we used to buy a lot of hardware before Christmas
- #63: Give example of Coolblue where we used to buy a lot of hardware before Christmas
- #64: Cloud Computing is easier, but still hard
- #69: In Cloud, IaaS and PaaS are often used as terms.
- #70: When? Before July 2017.. Set by the team!
- #71: It’s a 76 pages whitepaper created by AWS and helps developers, operation engineers, architects etc to build up to par Cloud architectes. It contains best practices and guidance on 5 conceptual areas, called the “5 pillars of the Well-Architected Framework”.
- #73: It’s a 76 pages whitepaper created by AWS and helps developers, operation engineers, architects etc to build up to par Cloud architectes. It contains best practices and guidance on 5 conceptual areas, called the “5 pillars of the Well-Architected Framework”.
- #75: It’s a 76 pages whitepaper created by AWS and helps developers, operation engineers, architects etc to build up to par Cloud architectes. It contains best practices and guidance on 5 conceptual areas, called the “5 pillars of the Well-Architected Framework”.
- #82: Forget the names, we manage a lot. We also spend a lot of time managing those tools, well we used to spend a lot of them managing these;
- #83: Introducing the Silver Bullet: which doesn’t exist. A single solution to every problem.
- #86: In Cloud, IaaS and PaaS are often used as terms.
- #88: What if you go a little left in the abstraction?
- #90: We have decided to commit to AWS. This does mean however that it would take time to port our software to another cloud provider if we would want to.
- #91: Hundreds of settings
- #92: Way less settings. Good because you don’t need to think about the complexity. Bad because you might need to change your setting for your specific use case.
- #94: Monolith vs services
- #95: Monolith vs services
- #96: That’s why it is so important to have a proper foundation. It should be easy to get all these things in place (pipelines, monitoring/logging, e.t.c.)
- #97: In Cloud, IaaS and PaaS are often used as terms.
- #100: Done :P