Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
2 replies
Subscribers
7 subscribers
Views
2297 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
Are there any known limitations in developing an application in Appian without a
padmanabhanv
over 11 years ago
Are there any known limitations in developing an application in Appian without a external data store(RDBMS)? There is no business need to perist data in an different data store and all the data would reside in Appian and would be purged based on the archival setting. Any known problems in proceeding with this architecture? Any suggestions would help....
OriginalPostID-90126
OriginalPostID-90126
Discussion posts and replies are publicly visible
0
Mike Cichy
Appian Employee
over 11 years ago
No "problems" per se, but NOT using an RDBMS in conjunction with Appian removes a very useful tool from your toolbox. You are limiting yourself to just using process data and making your app less flexible.
There is no need at this point, but what if there is one in the future? Are you going to migrate data out of Appian then? What if other applications, in Appian or external would like to use that data?
Every good Appian application design NEEDS to persist data in RDBMS.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
padmanabhanv
over 11 years ago
Thanks Mike. Concur with your observation - however a design pattern which will move process data to an external data store via a webservice - could be based on an event(eg Process completion) will also suffice right? It will cater to future reporting capabilities as well. Thoughts?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel