Connecting the clouds, A TrueLime Story
3 likes963 views
In this business case study, Jeroen shares his journey on how various microservices have been integrated, resulting in a rich and lightweight fresh new company blog.
More Related Content
What's hot (20)
Similar to Connecting the clouds, A TrueLime Story (20)
Recently uploaded (20)
Connecting the clouds, A TrueLime Story
- 1. Software om blij van te worden
- 3. HI, I AM JEROEN @jeroenfurst blogs.jeroenfurst.nl
- 4. To do: 1. Describe the project 2. Choose the right tech 3. Connect the dots 4. Quick demo 5. Inspect the outcome 6. Answer questions
- 6. Describe the project Create the company blog Target customers: Our employees Target audiences: Developers, Kenthusiasts Target architectures: Headless, Serverless Target technologies: Kentico Cloud, SPA Target platforms: Microsoft Azure, VSTS
- 7. Describe the project A couple of things to keep in mind This is an internal TrueLime project We apply the same approach to internal and external projects The goal is to create the MVP using new technology including Kentico Cloud
- 8. Describe the project Content first planning
- 9. Choose the right tech
- 10. Choose the right tech Kentico Cloud Is not the same as Kentico EMS, it’s a new product (SaaS) Provides “Content as a Service” via REST API’s (Kentico Deliver) Offers structured content and digital assets via global CDN’s Contains integrated analytics and visitor profiling (Kentico Engage) Does not require additional hosting
- 11. Choose the right tech ReactJS The project needs a head ReactJS is very suitable as the View part within the MVC pattern ReactJS is a JavaScript library (needs Flux or Redux to complete MVC pattern) ReactJS is a technology that is out of our comfort zone (serverless) Promotes fail fast strategy Developers love to work with the latest technologies
- 12. Choose the right tech DELIVER API RICH WEB APPLICATIONBLOG CONTENT REPOSITORY ReactJSAZURE https://blogs.truelime.nl Headless (microservice) architecture
- 13. Connect the dots
- 14. Connect the dots Implementing the microservice architecture We setup and configured the different components We developed the ReactJS web application We mapped content types from Kentico Cloud with stores in ReactJS We configured continuous deployment
- 15. Connect the dots Configure the different components
- 16. Connect the dots Developed the ReactJS web application
- 17. Connect the dots Mapping the models
- 18. Connect the dots Continuously deploy to Azure http://blogs.jeroenfurst.nl/blog/april-2017/how-to-deploy-reactjs-to-azure-using-vsts
- 19. Quick demo
- 21. Inspect the outcome Do you remember the planning?
- 22. Inspect the outcome Skip content modelling in spreadsheets
- 23. Inspect the outcome INSTALL BUILD TEST DEPLOY Traditional development lifecycle
- 24. Inspect the outcome INSTALL BUILD TEST DEPLOY less effort Headless development lifecycle
- 25. Inspect the outcome And regarding the technologies?
- 26. Inspect the outcome Still exploring (to be continued…) What is the impact on SEO? How to handle caching? Optimize the site with Kentico Engage Pick up development of new features (filtering, search) Integration with our corporate website
- 27. Inspect the outcome In retrospect Kentico Cloud offers a Vintage Kentico Experience We can shorten development time using Kentico Cloud We are learning new technologies We understand the difference between content centric and page centric We are ready to tap into new markets
- 29. Answer questions
- 32. Software om blij van te worden
Editor's Notes
- #4: Kentico MVP (veel ervaring) Kort over mijzelf TrueLime Breda Kentico Cloud Early Partner Program, sprint reviews Wat is onze ervaring
- #7: Inleiding Early adopter program Altijd al iets willen doen met rich web application
- #8: End client is TrueLime Explore new technologies, learn the tech by doing
- #9: One thing we directly noticed
- #11: Different product
- #12: We wanted to something different Line number Very lean
- #15: Backlog, VSTS, Azure, Visual Studio, Git
- #20: Keuze voor tool blijft wederom belangrijk
- #22: One thing we directly noticed
- #26: Kentico Cloud offers a trusted environment, ReactJS was really something completely different
- #27: Omni-channel
- #28: Vintage: We as long time Kentico partner felt right at home (tool, ems, support) Development: Content first approach, removes time for installation/hotfix/upgrades Technologies: Learned SPA, ReactJS, Headless/Microservice architectures Markets: Clients who are looking for rich web applications and seek omni-channel solutions
- #29: In other words… Thank Kentico for the opportunity as early adopter
- #30: Keuze voor tool blijft wederom belangrijk
- #31: In our journey