elastic.io
| Privately held company | |
| ISIN | 🆔 |
| Industry | Computer software |
| Founded 📆 | 2012 |
| Founders 👔 | Renat Zubairov, Igor Drobiazko |
| Headquarters 🏙️ | Bonn, Germany |
Area served 🗺️ | |
Key people |
|
| Products 📟 | elastic.io Integration Platform |
| Members | |
Number of employees | |
| 🌐 Website | www.elastic.io |
| 📇 Address | |
| 📞 telephone | |
elastic.io is a software vendor specializing in Data Integration. The company provides microservices-based integration software for connecting applications, databases, and APIs, cloud-to-cloud or cloud-to-ground.[1][2] elastic.io has their headquarters in Bonn, Germany.
History[edit]
Renat Zubairov [3] and Igor Drobiazko [4] founded elastic.io in 2012.[5]
On February 26, 2014, the company announced that it closed its first seed round of investments, amount undisclosed. At this time elastic.io has been venture-backed by two investors with background in IT, Ali Alghanim and Fabian von Kuenheim.
In May, 2015, elastic.io went into strategic partnership with T-Systems, German global IT services and consulting company headquartered in Frankfurt.[6]
In May, 2017 mVISE AG , German IT company headquartered in Düsseldorf and stocklisted at Scale standard of Frankfurt Stock Exchange purchased a 75% stake in elastic.io GmbH.
Products[edit]
elastic.io's main product is its microservices-based integration platform as a service (iPaaS), though in its recent report on platforms as a service, Gartner noticed that elastic.io is currently considered as both an iPaaS vendor and a pure-play iSaaS (Citizen Integrator Software as a Service) vendor.[7]
The company targets with its platform independent software vendors, system integrators and enterprise companies.[8]
The elastic.io Integration Platform is designed as a set of tools for data transformation and data integration both cloud-to-cloud and cloud-to-ground. It belongs to the hybrid integration platforms category, as it can be deployed in the cloud as well as on-premises. The set of elastic.io Integration Platform tools includes:
- Connector templates - open-sourced integration component templates for enterprise and SaaS applications, which can be modified and expanded by third-party developers
- Java and Node.js-based software development kits - open-sourced SDKs for building own integration components for third-party and in-house developed systems, databases, applications, and APIs
- Integration Management API - company's own JSON-based REST API for automating and scripting the elastic.io platform's functionality, embedding it into custom applications, or building new products on top of the platform
- Secure Integration Bridge (SIB) - designed to connect cloud-based applications, systems, databases and platforms to on-premises in cases when the elastic.io Integration Platform is deployed in the cloud
Technology[edit]
The elastic.io platform is microservices-based, with Apache Mesos and Docker underlying the software. This means that each integration flow, each integration components, and the platform itself are composed of Docker containers connected to each other via persistent messaging FIFO queue. Each container is limited with its own resources.
The platform supports both synchronous (aka Request/Response method) and asynchronous communication between applications and systems. Data is obtained either through polling APIs or via webhooks.
The elastic.io Integration Platform characteristics include:
- Multitenancy
- White-labeling option
- Horizontal scalability due to the microservices-based architecture
- Vertical scalability via individual container resource configuration (RAM + CPU)
- Low latency
- Hybrid deployment options
- Provided as managed service
- Support of API-first approach [9]
See also[edit]
- Data integration
- Enterprise service bus
- Extract, transform, and load (ETL)
- Software as a service (SaaS)
- Cloud computing
- iPaaS
- Enterprise application integration
- MuleSoft
- SnapLogic
- Talend
- Cloud-based integration
- Service-oriented architecture
References[edit]
- ↑ Büst, René. "API-Economy als Wettbewerbsfaktor: iPaaS im Zeitalter des Internet of Things (IoT) und Multi-Cloud-Umgebungen (German)". Crisp Research AG. Retrieved 13 October 2016.
- ↑ Büst, René. "API Economy as a competitive factor: iPaaS in the Age of the Internet of Things (IoT) and Multi-Cloud Environments (English)". Crisp Research AG. Retrieved 13 October 2016.
- ↑ "Why Your SaaS Ecosystem Isn't Delivering". DevOps.com. 2 May 2016. Retrieved 13 October 2016.
- ↑ "Bimodal IT and SaaS". CloudExpo Journal. 22 May 2016. Retrieved 13 October 2016.
- ↑ "Interview with elastic.io. Financial planning for SaaS Startups". 15 March 2012. Retrieved 13 October 2016.
- ↑ "Deutsche Cloud-Kooperation". Computerwoche. 5 May 2015. Retrieved 13 October 2016.
- ↑ "Platform as a Service: Definition, Taxonomy and Vendor Landscape, 2016". Gartner, Inc. 31 May 2016. Retrieved 13 October 2016.
- ↑ "German Startup elastic.io Launches New Product That Lets IT-Integration Experts Build Custom-Branded Integration Marketplaces". CloudWedge. 23 February 2016. Retrieved 13 October 2016.
- ↑ "Software development starts with an API-first approach". TechTarget. October 2014. Retrieved 13 October 2016.
Further reading[edit]
- Drobiazko, Igor (22 May 2016). "Bimodal IT and SaaS". CloudExpo Journal. Retrieved 13 October 2016.
...bimodal IT must include an integration platform to ensure a higher level of collaboration and visibility between the IT staff delivering the more centralized mode, and the ad hoc professionals seeking more agility and speed through SaaS...
- Zubairov, Renat (2 May 2016). "Why Your SaaS Ecosystem Isn't Delivering". DevOps.com. Retrieved 13 October 2016.
There is a point however, where SaaS and DevOps intersect—that point where an integration framework is superimposed over a SaaS catalog, and enterprise users now gain the advantage of each SaaS being part of a greater whole.
External links[edit]
This article "Elastic.io" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:Elastic.io. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.
