General Flashcards
1
Q
Some benefits of ERP-NAV web services
A
- very simple to publish
- provides managed access to ERP-NAV data while respecting and enforcing NAV rules, logic and design that already exists
- uses windows authn and respects NAV data constraints
- supports SOAP interface (cannot access query objects) and OData interface (cannot access codeunit objects)
2
Q
Some disadvantages of ERP-NAV web services
A
- allowing access to system from the web requires more security
- ERP-NAV objects that re published need to be customized
- access from web complicates admin’s job of managing loads on the system
3
Q
Factors to be considered in judging ws integration
A
- What is degree to which functionality of standard ERP interface is needed? A web service application should be used for limited, focused functionality
- What is amount of data to be exchanged? A web service application should be used for low data volume applications
- How public is user set? Web services should be used in intranet
4
Q
Legoblok voorstelling service
A
- biedt functionaliteit
- gestandaardiseerde interface
- autonoom
- loosely coupled
- reusable
- composable
5
Q
Loose coupling van service
A
=> zo weinig mogelijk afhankelijkheden aan andere services
- flexibiliteit (aanpasbaar zonder andere services te beinvloeden)
- schaalbaarheid (vermijd bottle necks)
- fout tolerantie (risico op system failures is beperkt)
6
Q
ESB
A
Enterprise service bus
- bemiddeling
- standaardisatie
- transformatie
- orchestratie
- monitoring
- logging
- security
7
Q
Functionele voordelen ESB
A
- Validation van inkomende berichten op content/context
- Enrichment (extra data toevoegen aan bericht)
- Transformation (bericht type veranderen naar ander type of standaard type)
- Routing van berichten op basis van content/context
- Operate: oplossingen om connectiviteit te voorzien naar target systeem en ondersteuning van protocollen
8
Q
Niet-functionele voordelen ESB
A
- Security
- Monitoring voor errors
- Reliability: asynchrone communicatie tussen source en targets
- Message throttling: ESB kan load wegnemen van bepaalde targets
9
Q
Eigenschappen microservices
A
- fine-grained -> loosely coupled + independent
- indeling rond business capabilities
- asynchroon
- lightweight protocols
- smart endpoints
- dumb pipes
- producten (geen projecten)
10
Q
Waarom microservice architecture
A
- scaling -> on demand + independent
- decentralization (hoe 200 mensen samenwerken)
- agility (lage time to market)
11
Q
Voordelen microservice
A
- modulariteit-> loosely coupled + onafhankelijke deployment
- diverse technologiën (service kan kiezen)
- scalability
- agility
12
Q
Nadelen microservice
A
- gedistribueerd systeem
- operationele complexiteit
13
Q
3 standard page operations
A
- create: create single record
- void Create(Entity entity) - delete: delete single record
- bool Delete(string key) - read: read single record
- Entity Read(string no)
14
Q
3 operations for exposing web services
A
- create: create single record (INSERT)
- update: update single record (MODIFY)
- delete: delete single record