General Flashcards

1
Q

Some benefits of ERP-NAV web services

A
  1. very simple to publish
  2. provides managed access to ERP-NAV data while respecting and enforcing NAV rules, logic and design that already exists
  3. uses windows authn and respects NAV data constraints
  4. supports SOAP interface (cannot access query objects) and OData interface (cannot access codeunit objects)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Some disadvantages of ERP-NAV web services

A
  1. allowing access to system from the web requires more security
  2. ERP-NAV objects that re published need to be customized
  3. access from web complicates admin’s job of managing loads on the system
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Factors to be considered in judging ws integration

A
  1. What is degree to which functionality of standard ERP interface is needed? A web service application should be used for limited, focused functionality
  2. What is amount of data to be exchanged? A web service application should be used for low data volume applications
  3. How public is user set? Web services should be used in intranet
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Legoblok voorstelling service

A
  • biedt functionaliteit
  • gestandaardiseerde interface
  • autonoom
  • loosely coupled
  • reusable
  • composable
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
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)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

ESB

A

Enterprise service bus

  • bemiddeling
  • standaardisatie
  • transformatie
  • orchestratie
  • monitoring
  • logging
  • security
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
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
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Eigenschappen microservices

A
  • fine-grained -> loosely coupled + independent
  • indeling rond business capabilities
  • asynchroon
  • lightweight protocols
  • smart endpoints
  • dumb pipes
  • producten (geen projecten)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Waarom microservice architecture

A
  • scaling -> on demand + independent
  • decentralization (hoe 200 mensen samenwerken)
  • agility (lage time to market)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Voordelen microservice

A
  • modulariteit-> loosely coupled + onafhankelijke deployment
  • diverse technologiën (service kan kiezen)
  • scalability
  • agility
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Nadelen microservice

A
  • gedistribueerd systeem

- operationele complexiteit

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

3 standard page operations

A
  1. create: create single record
    - void Create(Entity entity)
  2. delete: delete single record
    - bool Delete(string key)
  3. read: read single record
    - Entity Read(string no)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

3 operations for exposing web services

A
  1. create: create single record (INSERT)
  2. update: update single record (MODIFY)
  3. delete: delete single record
How well did you know this?
1
Not at all
2
3
4
5
Perfectly