Microservices and Friends
2 likes1,155 views
The document discusses the transition to a microservices architecture, highlighting improvements in team collaboration, delivery speed, and scalability. It emphasizes the importance of lightweight solutions and resource isolation using technologies like Docker, while also critiquing traditional application servers and enterprise service buses. Additionally, it touches on development practices, tools, and frameworks that facilitate effective deployment and continuous integration in software development.
![GulpGulp
http://markdalgleish.github.io/presentation-build-
wars-gulp-vs-grunt/
Streaming Builds
gulp.task('package', function() {
return gulp.src([ 'app/**/*', 'gulp_tasks/*', 'newrelic.js', 'package.json' ], {"base":
.pipe(tar('platmasphere-client.tar'))
.pipe(gzip())
.pipe(gulp.dest('.'));
});](https://image.slidesharecdn.com/microservicesandfriends-150324193627-conversion-gate01/85/Microservices-and-Friends-36-320.jpg)
Microservices and Friends
- 1. MicroServices & Friends Platmasphere Tech Stack @YunZhiLin
- 2. 1. Architecture1. Architecture 2. DevOps2. DevOps 3. Server Stack3. Server Stack 4. Client Stack4. Client Stack 5. Profit!5. Profit!
- 4. Enterprise ArchitectEnterprise Architect Don't have one - shared responsibility. Self organising team But we make decisions a lot faster. We do have some insteadEnterprise Architect Jokes
- 5. Service EvolutionService Evolution Sources: PWC research
- 7. We HadWe Had Traditional layered architecture: Silo'ed teams of BA, Designers and Dev ( ). Delivery bottlenecks Lack of collaboration and re-use Frustrating to debug/support Difficult to deploy Conway's Law
- 8. We now have:We now have: MicroServices based architecture: Cross functional design/dev of services Parallel delivery Re-usable modules across client and server Easy monitoring and diagnostics. Continuous Delivery
- 10. KISSKISS (Keep It Simple Stupid)(Keep It Simple Stupid)
- 11. No App Servers/WarNo App Servers/War Bloated in size, hogs resources, memoryleak, restarts Another layer of configuration and complexity Run multiple apps 1 app per server, no isolation Provide Infrastructure part of the app Ops - provides own toolsets vs external choices. EJB support - no need in this day and age $$$ and require specialists Sources: ,App Servers are Dead Stop wasting money on Application Servers
- 12. Use Standalone AppsUse Standalone Apps Self contained Configure you app, not the app server Resource isolation via docker containers Java - Jetty; Netty, Undertow, or just Main() Node.js - Harp, Express Ruby - Rails, Sinatra More on Framework later Reference: Heroku for Java
- 13. Enterprise Service BusEnterprise Service Bus solves all integration problems in a box fail proof
- 14. ESB In RealityESB In Reality One massive app server with all the same issues
- 15. MicroServicesMicroServices Independently Scalable Fault Tolerant Free Decentralised Governance Decentralised Data Smart endpoints vs ESBvs ESB Central orchestration. Canonical Data Model Middleware Bottleneck Single point of failure Smart Pipeline $$$$$$ Need pub/sub or queuing: try light weight broker-less messaging such as ZeroMQ.
- 16. JSON/RESTJSON/REST vs SOAP/WSDLvs SOAP/WSDL { "streetNumber": "80", "streetName": "Clarence", "suburb": "Sydney" } Text <?xml version="1.0" encoding="UTF-8" ?> <Property> <streetNumber>80</streetNumber> <streetName>Clarence</streetName> <suburb>Sydney</suburb> </Property PUT /hostname/properties/ <service name="Properties"> <documentation>WSDL File for PropertyService</d <port binding="tns:Properties" name="Properties <soap:address location="http://hostname/pro </port> </service>
- 17. SwaggerSwagger Who needs WSDL or JavaDoc when you have Swagger
- 19. Dev OpsDev Ops
- 20. Who Does Dev OpsWho Does Dev Ops No one does Dev Ops for the sake of Dev Ops DevOps is a means to an end: build good software Every good engineer should be Dev Ops minded
- 21. Continuous DeliveryContinuous Delivery 1. GitHub triggers artefact Snap-CI pipeline 2. Upload tested artefact to Bintray
- 22. Continuous DeliveryContinuous Delivery 3. Push to Quay.io to build Docker 4. Run Container on Tutum PaaS
- 23. Continuous DeliveryContinuous Delivery 5. Monitor Services using NewRelic
- 24. Why DockerWhy Docker Resource Isolation Immutable and Portable Lightweight compared to VM
- 25. Small and Fast DockerSmall and Fast Docker Take advantage of caching in Dockerfile Use small base images such as BusyBox CI friendly: fast build is a good build
- 27. Picking a FrameworkPicking a Framework Use the right tool for the right job Do prototype spikes that cover key requirements Consider the learning curve and team skill set Infrastructure are on-demand, don't feel restricted Performance will matter eventually, but not day 1 Reference benchmarks, or roll your ownTechEmpower
- 28. TechEmpower BenchmarksTechEmpower Benchmarks Don't always believe the hype!
- 29. Frameworks we useFrameworks we use Rails - the original developer productivity framework Dropwizard - Production ready out of box Spring Boot - For when you really need Spring RatPack - Not so easy to do the right thing
- 30. GradleGradle vs Mavenvs Maven repositories { jcenter() maven { url "http://dl.bintray.com/trunkplatform/osworkflow" } } } dependencies { compile group: 'com.trunkplatform.opensymphony', name: 'osworkflow', version: '3.1.4' } <repositories> <repository> <snapshots> <enabled>false</enabled> </snapshots> <id>bintray-trunkplatform</id> <name>bintray</name> <url>http://dl.bintray.com/trunkplatform/osw </repository> </repositories> <dependencies> <dependency> <groupId>com.trunkplatform.opensymphony</gro <artifactId>osworkflow</artifactId> <version>3.1.4</version> <scope>compile</scope> </dependency> </dependencies>
- 31. Postgres and MySqlPostgres and MySql Trnk.io - MySQL via Google CloudSQL Platmasphere - Postgres via Amazon RDS Postgres offers multi-tenant functionality
- 32. Dependency InjectionDependency Injection Inject dependencies as needed, rather than passing through different constructors. Swapping in stub implementations for tests Spring and Guice equally good. Right tool for right job
- 35. AngularJSAngularJS MVC Dependency Injection Static pages Made by Google (?)
- 36. GulpGulp http://markdalgleish.github.io/presentation-build- wars-gulp-vs-grunt/ Streaming Builds gulp.task('package', function() { return gulp.src([ 'app/**/*', 'gulp_tasks/*', 'newrelic.js', 'package.json' ], {"base": .pipe(tar('platmasphere-client.tar')) .pipe(gzip()) .pipe(gulp.dest('.')); });
- 37. HarpHarp Simple lightweight webserver Precompiles CSS and HTML templates No need to write any server app code var express = require('express') var app = express() app.get('/', function (req, res) { res.send('Hello World!') }) var server = app.listen(9000, function () { var host = server.address().address var port = server.address().port console.log('Example app listening at http://%s: }) bash$ harp server . ------------ Harp v0.14.0 – Chloi Inc. 2012–2014 Your server is listening at http://localhost:9000/ Press Ctl+C to stop the server ------------
- 38. Profit!Profit!