• Help Needed

  • Help please: Solution Overview Diagram & N-Tier Architecture

We have a large bank prospect that is being very annoying and asking a lot of questions about our tech. They have asked for:

Please describe how the solution is architected in the form of a solution overview diagram, and describe the various security, application and integration layers and protocols involved? Which product solutions does the architecture comprise? We at least need to know it is n-Tiered and how they separate application and business logic amongst the various layers, otherwise we will have problems confirming alignment to security protocols.

Has anyone jumped through these hoops before with an AwareIM based system and would be kind enough to share your docs/diagrams/answers with me? Feel free to PM me if you don't want to post here (understandably).

Thanks!

I've had similar with a large global company, not sure if it will be in the same arena but happy to chat.

Due to so many frauds and online security issues, security to be up to par with world's standards is the # 1 priority, especially in Banking, Insurance, Healthcare and government.
I had gone through that with an Insurance and healthcare prospects and they both denied AwareIM as the tool for their project.

As far as 3-tier goes, they want the back end and front end to be totally independent via REST services for immediate scale-ability and be able to connect to any type of client and other services. This also requires very tight security system. They're not being annoying. This is the reality & requirements of 99% of contracts today.

Many companies now even dictate what technologies must be used, i.e. Microsoft full stack, so they feel there is a large company behind the tooling system. When I tried to raise capital for my app, that was their first requirement to be based on the .Net 4.5 and above. AwareIM did not ring any bell on their list.

These are standard questions that any organization that has a basic level of IT competency is going to ask.

In general, it would be great to have a white paper that deep-dives into the AIM architecture. Maybe Vlad already has something he's used for other clients?

Regarding your immediate request ... these can be broken down further, but the basic n-tier layers are the:
-Presentation tier = Web Server (Tomcat)
-Business Logic tier = Application Server (AIM Server)
-Data tier = Database Server (MySQL, MS SQL Server, etc)

Generic description here ... https://en.wikipedia.org/wiki/Multitier_architecture

You can get the basic AIM description of each here: https://www.awareim.com/technical-architecture/

When it comes to the "technical aspects" of the solution, my suggestion is to focus less on AIM and more on the technology stack used by AIM. Some of which is called out here ... https://www.awareim.com/major-technical-features/