![]() ![]() How to overcome the constraint? Oracle databases aren’t so constrained, and SQLLoader can provide an easy means to ingest the data into a staging table. You may be working with a bulk data extract and only need a small subset of the data provided, it won’t help if the data is also represented using a verbose notation such as XML.Building an integration process so you have an event model developed, but in the interim, you need to take that bulk mechanism and convert it to a small stream of events. If an organization is transitioning to a more event-driven or at least micro-batch model, you have to start the transition somewhere, but trying to line up changes everywhere can be problematic, so we have to start somewhere.That said, there are cases where it does stand-up. Personally, I think there is a lot of validity in the argument, and anyone dealing with such bulky data activities should review and question if it is a better answer. There is a school of thought that points to the possibility when handling such large data volumes we should consider using Data Integration rather than a more event-centric integration tool. The question is how to handle such data with such constraints? Data Integration? But OIC is often used to support SaaS Financials and other cloud solutions which do have monthly process cycles which can generate significant data volumes, for example, payroll data. The file constraints (1GB for a file and 500GB for the FTP server) shouldn’t be an issue for day to day activities. But both have limits on the file size and capacity. OIC has for some time now provided an FTP adaptor and more recently included a full FTP server capability. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |