My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
2024-08-26-minutes-it-study-session
>
Meetings
>
2024
>
11. November
>
2024-11-05 10:00 AM - Commissioners' Agenda
>
2024-08-26-minutes-it-study-session
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/31/2024 12:03:58 PM
Creation date
10/31/2024 12:03:25 PM
Metadata
Fields
Template:
Meeting
Date
11/5/2024
Meeting title
Commissioners' Agenda
Location
Commissioners' Auditorium
Address
205 West 5th Room 109 - Ellensburg
Meeting type
Regular
Meeting document type
Supporting documentation
Supplemental fields
Item
Approve Minutes
Order
1
Placement
Consent Agenda
Row ID
123866
Type
Minutes
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
18
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Monolith to Individual Services & Microservices <br />CAMAS is currently built as a monolithic web applicatfon. Meaning all features and services interface through on single <br />applicatfon and are supported by one business class library. We desire to break this apart into individual applicatfons that <br />each serve a single purpose. Likewise, sole-purpose DLLs will be built for logic and business needs. <br />Advantages to the sole-purpose architecture <br />1. Decomposition: The applicatfon is decomposed into multfple services, each focusing on a specific business <br />capability. Features like purchasing, HR workflows, recruitment, etc., would be separate services. <br />2. Independence: Services are developed, deployed, and maintained independently. This allows for flexibility in <br />choosing different technologies and languages for each service, if they can communicate through APIs. <br />3. Scalability: You can scale individual services independently based on their specific resource needs, improving <br />efficiency and cost-effectfveness. <br />4. Isolation: Services are loosely coupled, which means changes or issues in one service are less likely to impact <br />others. This makes maintenance and troubleshootfng easier. <br />5. Deployment Flexibility: Updates or new features can be rolled out for specific services without affectfng the <br />entfre applicatfon. <br />6. Resilience: Failure in one service doesn't necessarily bring down the entfre applicatfon since other services can <br />contfnue to functfon. <br />Strategic Prioritfes <br />Our focus is on enhancing efficiency, scalability, and user experience. To achieve this, we have identffied three key <br />strategic prioritfes: <br />1. Replace Major Features with Commercial Off-the-Shelf (COTS) Software: <br />Our priority is to transitfon significant features of the intranet to reliable, industry standard COTS solutfons. This <br />approach will ensure cost-effectfve implementatfon, regular updates, robust security, and enhanced <br />functfonality. <br />2. Develop Features with Low-Code/No-Code Development Software: <br />For features that require customizatfon but do not necessitate full-scale development, we will leverage low-code <br />and no-code platiorms. This strategy will accelerate development, reduce costs, and empower our team to <br />quickly adapt and innovate. <br />3. Custom Applications Using Modern Coding Frameworks: <br />Where specific organizatfonal needs cannot be met by COTS or low-code/no-code solutfons, we will develop <br />custom applicatfons. Utflizing modern coding frameworks and robust platiorms, we aim to build scalable, secure, <br />and high-performance applicatfons tailored to our unique requirements. <br />4. Use RESTful Web APIs for Data Access: <br />Any custom applicatfons and integratfons will make use of Web APIs for data access, when appropriate. This <br />approach will allow us the flexibility to host the intranet outside of our network if we so desire while keeping <br />our data inside of our network.
The URL can be used to link to this page
Your browser does not support the video tag.