Best practice calls for AES and Applications to be on separate nodes with separate databases.
- If AES and applications shared resources consider the problem -- application has performance issues and sends data to AES. AES receives a lot of data and has to do a lot of processing using shared resources ... making performance worse ... causing application to send more alerts ... which triggers more work in AES ... making performance worse ..... etc
- if AES and application share resources, AES wont be able to help with application outage or impairment issues since it too will be out or impaired
Best practice for AES is completely separate stacks
Better best practice is use the PDC service -- you won't need to buy or operate a separate stack. PDC is FREE -- you don't pay for hardware; you don't pay for a database license; you don't need to pay for app servers and you dont need to assign staff to handle application operations. Plus PDC is normally "better software" as it is enhanced every week or two whilst AES is released every 18 months on average.