Downloaded 21 times
Uploaded byOutSystems
Neo in Wonderland: Essential Tools for an Outsystems Architect
The document outlines essential tools and strategies for becoming an effective OutSystems architect, emphasizing the importance of starting architecture before coding, utilizing live validation, and maintaining a comprehensive view of the project. It also discusses the significance of factory maintenance, database management, and team value creation through code contribution. The author, Fábio Fantato, shares insights on creating reports and configurations that enhance application development across various platforms.
More Related Content
Similar to Neo in Wonderland: Essential Tools for an Outsystems Architect
More from OutSystems
Neo in Wonderland: Essential Tools for an Outsystems Architect
- 1. | Neo inWonderland : essential tools for an OutSystems Architect Neo in Wonderland Essential Tools for an OutSystems Architect
- 2. | Neo inWonderland : essential tools for an OutSystems Architect| Neo in Wonderland : essential tools for an OutSystems Architect Fábio Fantato OutSystems MVP | Software Architect| Do iT Lean @ in [email protected] /fantato
- 3. | Create AmazingReports in OutSystems I want my perfect app tomorrow working in PC, android, IOS and in this language I’ve created yesterday source: Dilbert comic strip
- 4. | Neo inWonderland : essential tools for an OutSystems Architect
- 5. | Neo inWonderland : essential tools for an OutSystems Architect| Neo in Wonderland : essential tools for an OutSystems Architect
- 6. | Neo inWonderland : essential tools for an OutSystems Architect
- 7. | Neo inWonderland : essential tools for an OutSystems Architect
- 8. | Neo inWonderland : essential tools for an OutSystems Architect
- 9. | Neo inWonderland : essential tools for an OutSystems Architect
- 10. | Do AmazingReports in OutSystems ● Architecture ■ Starting before coding ■ Live Validation ■ Get a big picture ● Factory Maintenance ■ Database / Logs ■ Advanced Configurations ● Team Value Creation
- 11. | Neo inWonderland : essential tools for an OutSystems Architect| Neo in Wonderland : essential tools for an OutSystems Architect Architecture Starting before Coding
- 12. | Neo inWonderland : essential tools for an OutSystems Architect
- 13. | Neo inWonderland : essential tools for an OutSystems Architect
- 14. | Neo inWonderland : essential tools for an OutSystems Architect| Neo in Wonderland : essential tools for an OutSystems Architect Architecture Live Validation
- 15. | Neo inWonderland : essential tools for an OutSystems Architect
- 16. | Neo inWonderland : essential tools for an OutSystems Architect
- 17. | Neo inWonderland : essential tools for an OutSystems Architect
- 18. | Neo inWonderland : essential tools for an OutSystems Architect
- 19. | Neo inWonderland : essential tools for an OutSystems Architect
- 20. | Neo inWonderland : essential tools for an OutSystems Architect
- 21. | Neo inWonderland : essential tools for an OutSystems Architect| Neo in Wonderland : essential tools for an OutSystems Architect Architecture Get a big picture
- 22. | Neo inWonderland : essential tools for an OutSystems Architect
- 23. | Neo inWonderland : essential tools for an OutSystems Architect
- 24. | Neo inWonderland : essential tools for an OutSystems Architect
- 25. | Neo inWonderland : essential tools for an OutSystems Architect| Neo in Wonderland : essential tools for an OutSystems Architect Maintenance Database / Logs
- 26. | Neo inWonderland : essential tools for an OutSystems Architect
- 27. | Neo inWonderland : essential tools for an OutSystems Architect
- 28. | Neo inWonderland : essential tools for an OutSystems Architect
- 29. | Neo inWonderland : essential tools for an OutSystems Architect
- 30. | Neo inWonderland : essential tools for an OutSystems Architect
- 31. | Neo inWonderland : essential tools for an OutSystems Architect
- 32. | Neo inWonderland : essential tools for an OutSystems Architect
- 33. | Neo inWonderland : essential tools for an OutSystems Architect
- 34. | Neo inWonderland : essential tools for an OutSystems Architect
- 35. | Neo inWonderland : essential tools for an OutSystems Architect
- 36. | Neo inWonderland : essential tools for an OutSystems Architect| Neo in Wonderland : essential tools for an OutSystems Architect Maintenance Advanced Configurations
- 37. | Neo inWonderland : essential tools for an OutSystems Architect
- 38. | Neo inWonderland : essential tools for an OutSystems Architect
- 39. | Neo inWonderland : essential tools for an OutSystems Architect
- 40. | Neo inWonderland : essential tools for an OutSystems Architect
- 41. | Neo inWonderland : essential tools for an OutSystems Architect| Neo in Wonderland : essential tools for an OutSystems Architect Team Value Creation Code Contribution
- 42. | Neo inWonderland : essential tools for an OutSystems Architect
- 43. | Neo inWonderland : essential tools for an OutSystems Architect
- 44. | Neo inWonderland : essential tools for an OutSystems Architect
- 45. | Neo inWonderland : essential tools for an OutSystems Architect
- 46. | Neo inWonderland : essential tools for an OutSystems Architect
- 47. | Neo inWonderland : essential tools for an OutSystems Architect
- 48. | Neo inWonderland : essential tools for an OutSystems Architect Thank You! @ [email protected] m /fantato
Editor's Notes
- #4 Every day we are required to create amazing apps including the most modern practices and on top of the best architecture ever.
- #5 It is not an easy task to integrate different data sources, apis, legacy systems and technologies at the same solution.
- #6 And the most important on top a solid and robust architecture. Prepare to support evolution and heavy usage.
- #7 Usually we had this kind of issues. Almost in the end, we discover that our project doesn’t connect the things. But we need to remember that not always the architect’s fault.
- #8 Part of the problems underlies on the understanding of the problem. It is important to know what our customers want
- #9 Sorry guys. This is not the scope of this presentation, but you can find good books (this is one example) to help you in this mission.
- #10 In fact my purpose will be present you my Infinity Gauntlet of tools available on Forge to support an Architect life in OutSystems Infrastructures. Let's explore them
- #12 First we need to starting to create our architecture
- #13 We can use a conventional Canvas or use the Eletronic Canvas Tool
- #14 This tool will allow you to create your 4LC and assemble your ideas even before starting to code
- #15 After you create your projects and start to put your ideas off the paper. You need to validate your architecture
- #16 The best tool to do that it is the Discovery
- #17 Here you will be able to create snapshots of your environment and explore violations to 4LC framework directly based on your code.
- #18 You can see your Modules classified by the layers and have some information about consumers, producers, layer violations and many other information about your architecture
- #19 Also you can have the same kind of information for the Applications boundaries.
- #20 And map the dependencies table for your entire infrastructure.
- #21 Please go to the Learn area in the community to know more about 4LC and Discovery
- #22 Sometime the info we got form Discovery is too heavy and we need only a big picture to discuss with our customers.
- #23 A good tool to do that is the Clean Architecture
- #24 Here you can reuse the same classification you have done in Discovery , but get only a big picture and the boundaries and relationship among your applications and modules.
- #25 Also it is possible to see the Entity Diagram extracted directly from the metadata, but without the attributes.
- #26 As long as your project goes on. You need to think in your database maintanance
- #27 There is a new version of the DBCleaner.
- #28 This tool has the same features of the original one, but they were repaginated.
- #31 But it was added some features to create jobs to do the cleanup automatically and integrate this tool with the Service Account available in the lifetime.
- #32 Other important tool is the SQL Map.
- #33 Sometimes we need to know the physical names of our tables to create some maintenance scripts or do some actions directly in to the database. This tool will translate the queries to us. From the logical to physical names and vice versa
- #34 Another good tool related to SQL is the SQL Sandbox
- #35 Another good tool related to SQL is the SQL Sandbox
- #36 Here is possible to create your own queries to select and/or update data into the database without need to create timers and use some tricks inside the screen actions. This tool has some useful features that will help us to find the entities and create select and update statements for each one.
- #37 Other category we need to manage is our factory.
- #38 Facotry configurations is a tool that works on on premise installations . If you have a cloud environemnt this tool could be limited features.
- #39 The idea of this component is provide you some mechanism to amnipulate web.config to create custom handlers, change proxy to rest and soap calls, and increase the trace logs
- #40 Also it is possible to change some parameters related to security, brute force protection, runtime, compiler things
- #41 scheduler, reverse proxy and more
- #42 The last category I select to talk you is about the contributions of your team in your infrastructure
- #43 The OutGource project is very useful to do that
- #44 You can select the applications you want monitoring
- #45 And this toll will collect some logs to show you how your team are working on that application. Who are the guys working on each module, when they do the most part of the jobs, publishes and other things
- #46 Also you can see one specific developer and see what was his contributions to the project.
- #47 You can collect the log generated for this tool and run a viewer to display graphcally a timeline of your project and know when and how each developer act to evolute the application
- #48 Well guys these were my master tools I am always have in my infrastructures and I am sure that they can be valuable for any OS Architect.